The response field deprecated of all endpoints that return "Images", "Server Types" and "Load Balancer Types" was removed, as announced on 8 September 2026. Please use the deprecation field instead: For "Images", use the deprecation field. For "Server Types", use the deprecation field of the respective entry in locations. For "Load Balancer Types", use the deprecation field.
The Volume endpoints for creating, attaching, listing, and retrieving details now support a new assignee property that generalises the attachment of Volumes to allow for resources other than server in the future. All assignments now show in the new assignee fields, in addition to the server field. The old server properties in the same endpoints are now deprecated and will be removed on 27 October…
The Network subnet type server is deprecated and will be removed on 15 April 2027. The Network subnet type server is functionally equivalent to the Network subnet type cloud, use cloud instead. After the removal, requests that create a Network subnet with type server, for example when creating a Network or adding a subnet to a Network, will fail. Existing Network subnets with type server are not a…
The HTTP Link header specified in the API documentation is considered deprecated from now on and will be removed on 1 April 2027. Paginated API responses contain multiple Link headers pointing to previous, next and last pages. Those headers are deprecated. Use the meta.pagination object in the response body instead.
As part of our work on supporting existing Primary IPs for Load Balancers, deleting a Load Balancer is now tracked with an Action. The endpoint DELETE /load_balancers/{id} now returns a 201 status code with an Action in the response body, instead of a 204 status code with an empty response body. You can use the returned delete_load_balancer Action to track the progress of the deletion.
Primary IPs, which were previously available exclusively for servers, are now also available for Load Balancers. When creating a Load Balancer, you can assign an existing Primary IP instead of having an IP address allocated automatically. Currently, you cannot change the Primary IP once the Load Balancer has been created. To support this change, we added the new public_net property to the request…
As announced on 2 June 2026, the endpoints for GET /v1/datacenters and GET /v1/datacenters/{id} are removed and now return HTTP 410 Gone.
As announced on 8 July 2026, 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.
As announced on 8 July 2026, when updating the TTL of an RRSet, the value of ttl is no longer optional and must be provided. For the endpoint below, the ttl value must be set to the desired TTL, or to null to use the Zone's default TTL. Leaving the value empty will cause the request to fail. POST /zones/{id_or_name}/rrsets/{rr_name}/{rr_type}/actions/change_ttl
Primary IP's assignee_type property now returns unassigned if the IP is not assigned (assignee_id is null). This change is required to eventually allow assigning Primary IPs to other resources. This change was previously scheduled to be released as of 1 Aug. 2026. assignee_type assignee_id Previously server null As of 23 Sept. 2026 unassigned null
We added a new endpoint to the API: GET /v1/networks/$ID/members The new endpoint lists the resources attached to a Network, so you no longer have to collect them from the individual Server and Load Balancer resources. Each entry in the members response field contains the following properties: Property Description type The type of the attached resource, either server or load_balancer. id The ID of…
You no longer need to completely empty a Bucket before deleting it. From now on, a Bucket can be deleted even if it contains up to 1,000 leftover parts from multipart uploads that are either still in progress or have been aborted. If the Bucket still contains other objects (no matter if locked or versioned), these must be removed beforehand as outlined in the documentation: How can I delete my Buc…
The response field deprecated of all endpoints that return "Images", "Server Types" and "Load Balancer Types" will be removed on 2 November 2026. Please use the deprecation field instead: For "Images", use the deprecation field. For "Server Types", use the deprecation field of the respective entry in locations, as announced on 24 September 2025. For "Load Balancer Types", use the deprecation field…
Primary IPs, which were previously available exclusively for servers, are now also available for Load Balancers. When creating a Load Balancer, you can assign an existing Primary IP instead of having an IP address allocated automatically. Currently, you cannot change the Primary IP once the Load Balancer has been created. To support this change, we added the new public_net property to the request…
The image debian-15 (IDs 45557056 (x86) & 103907373 (arm)) is deprecated and will no longer be available when creating new servers after 30 November 2026.
To provide more details about failed health checks, Load Balancer requests that return the target response field in a successful (200) response now include the following additional child attributes: targets.health_status.detail targets.health_status.http_status_code The detail property is only set while a target is unhealthy, and can have one of the following values: Value Description layer4_no_co…
Primary IP's assignee_type property now returns unassigned if the IP is not assigned (assignee_id is null). This change is required to eventually allow assigning Primary IPs to other resources. assignee_type assignee_id Previously server null As of 01 Aug. 2026 unassigned null
As announced on 30 Jun. 2026 the EC2 compatible routes were now removed from Server Metadata.
The image opensuse-15 (IDs 204457491 (x86) & 204457492 (arm)) is no longer available when creating new servers.
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. For the endpoints below, the dns_ptr value must be set to the desired domain name, or to null to reset it. Leaving the value empty will no longer reset the pointer. Instead, the request will fail. POST /se…
When updating the TTL of an RRSet, the value of ttl is no longer optional and must be provided starting on 30 September 2026. For the endpoint below, the ttl value must be set to the desired TTL, or to null to use the Zone's default TTL. Leaving the value empty will cause the request to fail. POST /zones/{id_or_name}/rrsets/{rr_name}/{rr_type}/actions/change_ttl
We removed the datacenter property in the request body and response of Servers and Primary IPs as announced on 16 December 2025.
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. This includes the following schemas: /2009-04-04/meta-data /2009-04-04/meta-data/{key} /2009-04-04/user-data /latest/meta-data /latest/meta-data/{key} /latest/user-data
The image fedora-42 (IDs 232895138 (x86) & 232895264 (arm)) is no longer available when creating new servers.
After making the Load Balancer idle timeout values for HTTP/HTTPS services configurable via the API in April, you can now also use the Console to change the previously fixed timeout of 50 seconds for each service separately.
To communicate deprecations more clearly to API users and align with server types, we have added the deprecation field to all endpoints that return "Load Balancer Types". The field describes if, when, and how the resource was deprecated. If this field is set to null, the resource is not deprecated. If it has a value, it is considered deprecated. Learn more about the field in our API docs. This new…
The response field deprecated of all endpoints that return "Load Balancer Types" is deprecated. Please use the new field deprecation instead.
The API endpoints GET /v1/datacenters and GET /v1/datacenters/{id} are now deprecated and will be removed after 1 Oct. 2026. After this date, requests to these endpoints will return HTTP 410 Gone.
Two new Rapid Deploy Images are now available. The Ubuntu 26.04 image can be used as ubuntu-26.04 (IDs 387894169 for x86 and 387894171 for arm). Also the latest Fedora 44 release can be deployed to all Cloud servers as fedora-44 (IDs 387893188 (x86) & 387893189 (arm)).
Images using cloud-init 25.3 or later support auto-configuration of Private Networks via cloud-init. Currently this is available in Ubuntu 22.04, 24.04 and 26.04 as well as Fedora 44. For these images, the configuration of Private Networks has been removed from hc-utils. If you are using an older version of hc-utils, you can find the latest hc-utils for these images in our documentation.