Hetzner Cloud API
/2009-04-04/user-data endpoint removal
Stopped workingSubscribe to Hetzner Cloud APIShare
Calls to /2009-04-04/user-data on Hetzner Cloud API stopped working on August 1, 2026.
Calls it hits
/2009-04-04/user-data
In Hetzner Cloud API's words
Until now Server Metadata also responded to EC2-compatible routes besides the officially documented /hetzner/v1/* . This behaviour is now deprecated and will be removed after 1 Aug. 2026.
Facts
- API
- Hetzner Cloud API
api.hetzner.cloud - Kind
- Endpoint removal
- Takes effect
- August 1, 2026
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Hetzner Cloud API's own pages
Questions
When does this change take effect?
Calls to /2009-04-04/user-data on Hetzner Cloud API stopped working on August 1, 2026.
What happens to calls after August 1, 2026?
They have failed since August 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
-
POST /v1/primary_ipsParameter removal Stopped working -
POST /v1/serversParameter removal Stopped working -
/2009-04-04/meta-dataEndpoint removal Stopped working -
/latest/meta-dataEndpoint removal Stopped working -
/latest/meta-data/{id}Endpoint removal Stopped working -
/latest/user-dataEndpoint 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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.