Hetzner Cloud API
GET /v1/datacenters* endpoint removal
Stopped workingSubscribe to Hetzner Cloud APIShare
On October 1, 2026, Hetzner Cloud API removed the GET /v1/datacenters* endpoints. Calls to these routes fail since that date and now return HTTP 410 Gone.
Calls it hits
GET /v1/datacenters*
What to use instead of these calls
Read locations with GET /v1/locations instead, and retrieve per-location availability from the locations entries in GET /v1/server_types.
In Hetzner Cloud API's words
the endpoints for GET /v1/datacenters and GET /v1/datacenters/{id} are removed and now return HTTP 410 Gone.
Facts
- API
- Hetzner Cloud API
api.hetzner.cloud - Kind
- Endpoint removal
- Announced
- June 2, 2026
- Takes effect
- October 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Hetzner Cloud API's own pages
Questions
When does this change take effect?
Calls to GET /v1/datacenters* on Hetzner Cloud API stopped working on October 1, 2026.
What happens to calls after October 1, 2026?
They have failed since October 1, 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 Hetzner Cloud API 10
-
/2009-04-04/meta-dataEndpoint removal Stopped working -
/2009-04-04/user-dataEndpoint removal Stopped working -
/latest/meta-dataEndpoint removal Stopped working -
/latest/meta-data/{id}Endpoint removal Stopped working -
POST /floating_ips/{id}/actions/change_dns_ptrBehaviour change Stopped working -
POST /load_balancers/{id}/actions/change_dns_ptrBehaviour change Stopped working -
POST /primary_ips/{id}/actions/change_dns_ptrBehaviour change Stopped working -
POST /servers/{id}/actions/change_dns_ptrBehaviour change Stopped working -
POST /zones/{id}/rrsets/{id}/{id}/actions/change_ttlBehaviour change Stopped working -
debian-11Model retirement Stops workingin 24 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.