Scaleway API
/containers/v1beta1/* version retirement
Deprecated, no dateSubscribe to Scaleway APIShare
Scaleway deprecated the Serverless Containers API v1beta1 without an announced shutdown date. This deprecation affects all endpoints matching /containers/v1beta1/*. Calls to these endpoints will eventually fail once the retirement takes effect.
Calls it hits
/containers/v1beta1/*
What to use instead of these calls
Call the Serverless Containers v1 API under /containers/v1/regions/{region}/ instead, following Scaleway's v1 migration guide.
In Scaleway API's words
Serverless Containers API `v1beta1` is now marked as **deprecated**, `v1` is the new reference version.
Facts
- API
- Scaleway API
api.scaleway.com - Kind
- Version retirement
- Announced
- July 13, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Scaleway API's own pages
Questions
When does this change take effect?
Scaleway API deprecated /containers/v1beta1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Scaleway API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Scaleway API 8
-
/mnq/v1alpha1/*Version retirement Stopped working -
GET /containers/v1beta1/regions/{id}/containers/{id}/logsEndpoint removal Stopped working -
GET /functions/v1beta1/regions/{id}/functions/{id}/logsEndpoint removal Stopped working -
/vpc-gw/v1/*Version retirement Stopped working -
GET /rdb/v1/regions/{id}/instances/{id}/metricsEndpoint removal Stopped working -
DELETE /k8s/v1/regions/{id}/nodes/{id}Parameter removal Stopped working -
No date
/edge-services/v1alpha1/*Version retirement Deprecated, no date -
No date
/lb/v1/regions/*Version retirement Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.