Hetzner Cloud API
POST /floating_ips/{id}/actions/change_dns_ptr now requires dns_ptr
Stopped workingSubscribe to Hetzner Cloud APIShare
Calls to POST /floating_ips/{id}/actions/change_dns_ptr, body parameter dns_ptr on Hetzner Cloud API stopped working on September 30, 2026.
Calls it hits
POST /floating_ips/{id}/actions/change_dns_ptrbody parameter dns_ptr
In Hetzner Cloud API's words
When updating the PTR record (reverse DNS) for a Primary IP, Floating IP, Server, or Load Balancer, the value of dns_ptr is no longer optional and must be provided starting on 30 September 2026.
Facts
- API
- Hetzner Cloud API
api.hetzner.cloud - Kind
- Behaviour change
- Takes effect
- September 30, 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 POST /floating_ips/{id}/actions/change_dns_ptr, body parameter dns_ptr on Hetzner Cloud API stopped working on September 30, 2026.
What happens to calls after September 30, 2026?
They have failed since September 30, 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 -
/latest/user-dataEndpoint removal 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 -
GET /v1/datacenters*Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.