Scaleway API
/vpc-gw/v1/* version retirement
Stopped workingSubscribe to Scaleway APIShare
Calls to /vpc-gw/v1/* on Scaleway API stopped working on October 1, 2025.
Calls it hits
/vpc-gw/v1/*
What to use instead of these calls
Call the Public Gateways v2 API under /vpc-gw/v2/zones/{zone}/ instead. This transition requires more than changing an identifier, as DHCP settings move to the Private Network's built-in DHCP and IPAM.
In Scaleway API's words
The API v1 is now deprecated and will be definitively removed by October 1, 2025.
Facts
- API
- Scaleway API
api.scaleway.com - Kind
- Version retirement
- Announced
- April 8, 2025
- Takes effect
- October 1, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Scaleway API's own pages
Questions
When does this change take effect?
Calls to /vpc-gw/v1/* on Scaleway API stopped working on October 1, 2025.
What happens to calls after October 1, 2025?
They have failed since October 1, 2025.
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 -
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 -
No date
/containers/v1beta1/*Version retirement Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.