Scaleway API
replace query parameter removal on DELETE /k8s/v1/regions/{id}/nodes/{id}
Stopped workingSubscribe to Scaleway APIShare
On July 28, 2026, Scaleway API removed the replace query parameter from the DELETE /k8s/v1/regions/{id}/nodes/{id} endpoint. Calls to this endpoint that include the replace parameter fail since that date.
Calls it hits
DELETE /k8s/v1/regions/{id}/nodes/{id}query parameter replace
What to use instead of these calls
To replace a node, use POST /k8s/v1/regions/{region}/nodes/{node_id}/replace instead of sending a DELETE request with replace=true.
In Scaleway API's words
Removed parameter `replace` on `DeleteNode` route, the route `ReplaceNode` should be used instead.
Facts
- API
- Scaleway API
api.scaleway.com - Kind
- Parameter removal
- Takes effect
- July 28, 2026
- 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 DELETE /k8s/v1/regions/{id}/nodes/{id}, query parameter replace on Scaleway API stopped working on July 28, 2026.
What happens to calls after July 28, 2026?
They have failed since July 28, 2026.
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 -
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.