Hetzner

aid: hetzner
name: Hetzner
description: Hetzner Online is a German hosting provider offering cloud servers, dedicated servers, and domain services. Hetzner
  provides a Cloud API for programmatic management of cloud resources, as well as a DNS API for managing DNS zones and records.
type: Index
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hetzner.png
tags:
- Cloud Hosting
- DNS
- Infrastructure
- Servers
url: https://raw.githubusercontent.com/api-evangelist/hetzner/refs/heads/main/apis.yml
created: '2025-02-09'
modified: '2026-05-19'
specificationVersion: '0.19'
apis:
- aid: hetzner:hetzner-dns-api
  name: Hetzner DNS API
  description: The Hetzner DNS API provides programmatic access to manage DNS zones, records, and configurations for domains
    hosted with Hetzner's DNS service.
  humanURL: https://dns.hetzner.com/api-docs
  baseURL: https://dns.hetzner.com/api/v1
  tags:
  - DNS
  - Domain Management
  properties:
  - type: Documentation
    url: https://dns.hetzner.com/api-docs
  - type: Authentication
    url: https://dns.hetzner.com/api-docs#section/Authentication
- aid: hetzner:hetzner-actions-api
  name: Hetzner Actions API
  description: 'Actions represent asynchronous tasks within the API, targeting one or more resources.


    See [Actions](#description/actions) for more details.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-certificate-actions-api
  name: Hetzner Certificate Actions API
  description: The Certificate Actions API from Hetzner — 5 operation(s) for certificate actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Certificate Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-certificate-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-certificates-api
  name: Hetzner Certificates API
  description: TLS/SSL Certificates prove the identity of a Server and are used to encrypt client traffic.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Certificates
  properties:
  - type: OpenAPI
    url: openapi/hetzner-certificates-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-data-centers-api
  name: Hetzner Data Centers API
  description: 'Each Datacenter represents a _virtual_ Datacenter which may consist of possibly many physical Datacenters.
    A physical Datacenter is where [Servers](#tag/servers) are hosted.


    See the [Hetzner Locations Docs](https://docs.hetzner.com/cloud/general/locations/#what-datacenters-are-there) for more
    details about Datacenters.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Data Centers
  properties:
  - type: OpenAPI
    url: openapi/hetzner-data-centers-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-firewall-actions-api
  name: Hetzner Firewall Actions API
  description: The Firewall Actions API from Hetzner — 7 operation(s) for firewall actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Firewall Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-firewall-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-firewalls-api
  name: Hetzner Firewalls API
  description: 'Firewalls can limit the network access to or from your resources.


    - When applying a firewall with no `in` rule all inbound traffic will be dropped. The default for `in` is `DROP`.

    - When applying a firewall with no `out` rule all outbound traffic will be accepted. The default for `out` is `ACCEPT`.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Firewalls
  properties:
  - type: OpenAPI
    url: openapi/hetzner-firewalls-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-floating-ip-actions-api
  name: Hetzner Floating IP Actions API
  description: The Floating IP Actions API from Hetzner — 8 operation(s) for floating ip actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Floating IP Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-floating-ip-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-floating-ips-api
  name: Hetzner Floating IPs API
  description: 'Floating IPs help you to create highly available setups. You can assign a Floating IP to any Server. The Server
    can then use this IP. You can reassign it to a different Server at any time, or you can choose to unassign the IP from
    Servers all together.


    Floating IPs can be used globally. This means you can assign a Floating IP to a Server in one Location and later reassign
    it to a Server in a different Location. For optimal routing and latency Floating IPs should be used in the Location they
    were created in.


    For Floating IPs to work with your Server, you must configure them inside your operation system.


    Floating IPs of type `ipv4` use a single IPv4 address as their `ip` property. Floating IPs of type `ipv6` use a /64 network
    such as `fc00::/64` as their `ip` property. Any IP address within that network can be used on your host.


    Floating IPs are billed on a monthly basis.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Floating IPs
  properties:
  - type: OpenAPI
    url: openapi/hetzner-floating-ips-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-image-actions-api
  name: Hetzner Image Actions API
  description: The Image Actions API from Hetzner — 5 operation(s) for image actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Image Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-image-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-images-api
  name: Hetzner Images API
  description: 'Images are blueprints for your VM disks. They can be of different types:


    ### System Images


    Distribution Images maintained by us, e.g. “Ubuntu 20.04”


    ### Snapshot Images


    Maintained by you, for example “Ubuntu 20.04 with my own settings”. These are billed per GB per month.


    ### Backup Images


    Daily Backups of your Server. Will automatically be created for Servers which have backups enabled (`POST /servers/{id}/actions/enable_backup`)


    Bound to exactly one Server. If you delete the Server, you also delete all backups bound to it. You may convert backup
    Images to snapshot Images to keep them.


    These are billed at 20% of your server price for 7 backup slots.


    ### App Images


    Prebuild images with specific software configurations, e.g. “Wordpress”. All app images are created by us.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Images
  properties:
  - type: OpenAPI
    url: openapi/hetzner-images-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-isos-api
  name: Hetzner ISOs API
  description: 'ISOs are read-only Images of DVDs. While we recommend using our Image functionality to install your Servers
    we also provide some stock ISOs so you can install more exotic operating systems by yourself.


    On request our support uploads a private ISO just for you. These are marked with type `private` and only visible in your
    Project.


    To attach an ISO to your Server use `POST /servers/{id}/actions/attach_iso`.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - ISOs
  properties:
  - type: OpenAPI
    url: openapi/hetzner-isos-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-load-balancer-actions-api
  name: Hetzner Load Balancer Actions API
  description: The Load Balancer Actions API from Hetzner — 17 operation(s) for load balancer actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Load Balancer Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-load-balancer-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-load-balancer-types-api
  name: Hetzner Load Balancer Types API
  description: 'Load Balancer types define kinds of Load Balancers offered. Each type has an hourly and a monthly cost. You
    will pay whichever amount is lower for your usage of this specific Load Balancer. Costs may differ between Locations.


    All prices are displayed in the currency of the project owner''s account.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Load Balancer Types
  properties:
  - type: OpenAPI
    url: openapi/hetzner-load-balancer-types-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-load-balancers-api
  name: Hetzner Load Balancers API
  description: The Load Balancers API from Hetzner — 3 operation(s) for load balancers.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Load Balancers
  properties:
  - type: OpenAPI
    url: openapi/hetzner-load-balancers-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-locations-api
  name: Hetzner Locations API
  description: Datacenters are organized by Locations. Datacenters in the same Location are connected with very low latency
    links.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Locations
  properties:
  - type: OpenAPI
    url: openapi/hetzner-locations-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-network-actions-api
  name: Hetzner Network Actions API
  description: The Network Actions API from Hetzner — 10 operation(s) for network actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Network Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-network-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-networks-api
  name: Hetzner Networks API
  description: 'Networks is a private networks feature. These Networks are optional and they coexist with the public network
    that every Server has by default.


    They allow Servers to talk to each other over a dedicated network interface using private IP addresses not available publicly.


    The IP addresses are allocated and managed via the API, they must conform to [RFC1918](https://tools.ietf.org/html/rfc1918#section-3)
    standard. IPs and network interfaces defined under Networks do not provide public internet connectivity, you will need
    to use the already existing public network interface for that.


    Each network has a user selected `ip_range` which defines all available IP addresses which can be used for Subnets within
    the Network.


    To assign individual IPs to Servers you will need to create Network Subnets, described below.


    Currently Networks support IPv4 only.


    ### Subnets


    Subnets divide the `ip_range` from the parent Network object into multiple Subnetworks that you can use for different
    specific purposes.


    For each subnet you need to specify its own `ip_range` which must be contained within the parent Network’s `ip_range`.
    Additionally each subnet must belong to one of the available Network Zones described below. Subnets can not have overlapping
    IP ranges.


    Currently there are three types of subnet:


    - type `cloud` is used to connect cloud Resources into your Network.

    - type `server` was used to connect only cloud Servers into your Network. This type is deprecated and is replaced by type
    cloud.

    - type `vswitch` allows you to connect [Dedicated Server vSwitch](https://docs.hetzner.com/robot/dedicated-server/network/vswitch)
    - and all Dedicated Servers attached to it - into your Network


    Subnets of type `vswitch` must set a `vswitch_id` which is the ID of the existing vSwitch in Hetzner Robot that should
    be coupled.


    ### Network Zones


    Network Zones are groups of Locations which have special high-speed network connections between them. The [Location object](https://docs.hetzner.cloud/reference/cloud#locations-get-a-location)
    contains the `network_zone` property each Location belongs to. Currently these network zones exist:


    | Network Zone | Contains Locations |

    | ------------ | ------------------ |

    | eu-central   | nbg1, fsn1, hel1   |

    | us-east      | ash                |

    | us-west      | hil                |

    | ap-southeast | sin                |


    ### IP address management


    When a cloud Server is attached to a network without the user specifying an IP it automatically gets an IP address assigned
    from a subnet of type `server` in the same network zone. If you specify the optional `ip` parameter when attaching then
    we will try to assign that IP. Keep in mind that the Server’s location must be covered by the Subnet’s Network Zone if
    you specify an IP, or that at least one Subnet with the zone covering Server’s location must exist.


    A cloud Server can also have more than one IP address in a Network by specifying aliases. For details see the [attach
    to network action](https://docs.hetzner.cloud/reference/cloud#server-actions-attach-a-server-to-a-network).


    The following IP addresses are reserved in networks and can not be used:


    - the first IP of the network `ip_range` as it will be used as a default gateway for the private Network interface.

    - `172.31.1.1` as it is being used as default gateway for our public Network interfaces.


    ### Coupling Dedicated Servers


    By using subnets of type `vswitch` you can couple the Cloud Networks with an existing [Dedicated Server vSwitch](https://docs.hetzner.com/robot/dedicated-server/network/vswitch)
    and enable dedicated and cloud servers to

    talk to each other over the Network.

    In order for this to work the dedicated servers may only use IPs from the subnet and must have a special network configuration.
    Please refer to [FAQ](https://docs.hetzner.com/cloud/networks/connect-dedi-vswitch). vSwitch Layer 2 features are not
    supported.


    ### Routes


    Networks also support the notion of routes which are automatically applied to private traffic. A route makes sure that
    all packets for a given `destination` IP prefix will be sent to the address specified in its `gateway`.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Networks
  properties:
  - type: OpenAPI
    url: openapi/hetzner-networks-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-placement-groups-api
  name: Hetzner Placement Groups API
  description: 'Placement groups are used to influence the location of interdependent virtual servers in our data centers.
    The distribution of the different servers within a group is based on a pattern specified in the type. By enforcing certain
    rules on the placement of servers within our infrastructure, availability can be influenced in a way that fits your needs
    best.


    In `spread` placement groups, all virtual servers will run on different physical servers. This decreases the probability
    that some servers might fail together.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Placement Groups
  properties:
  - type: OpenAPI
    url: openapi/hetzner-placement-groups-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-pricing-api
  name: Hetzner Pricing API
  description: Returns prices for resources.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Pricing
  properties:
  - type: OpenAPI
    url: openapi/hetzner-pricing-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-primary-ip-actions-api
  name: Hetzner Primary IP Actions API
  description: The Primary IP Actions API from Hetzner — 8 operation(s) for primary ip actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Primary IP Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-primary-ip-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-primary-ips-api
  name: Hetzner Primary IPs API
  description: 'Primary IPs help you to create more flexible networking setups. You can assign at most one Primary IP of type
    `ipv4` and one of type `ipv6` per Server. This Server then uses these IPs.


    You can only unassign a Primary IP from a Server when it''s powered off. This Primary IP can then be assigned to a different
    powered off Server, or you can keep it around for later use.


    Primary IPs are bound to a specific Location. You can not assign a Primary IP from one Location to a Server in a different
    Location. If you need this capability use Floating IPs instead.


    If your Server''s operating system supports cloud-init there is no further configuration needed to make Primary IPs work.


    Primary IPs of type `ipv4` use a single IPv4 address as their `ip` property. Primary IPs of type `ipv6` use a /64 network
    such as `fc00::/64` as their `ip` property. Any IP address within that network can be used on your host.


    Primary IPs are billed on an hourly basis.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Primary IPs
  properties:
  - type: OpenAPI
    url: openapi/hetzner-primary-ips-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-server-actions-api
  name: Hetzner Server Actions API
  description: The Server Actions API from Hetzner — 27 operation(s) for server actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Server Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-server-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-server-types-api
  name: Hetzner Server Types API
  description: 'Server types define kinds of Servers offered. Each type has an hourly and a monthly cost. You will pay whichever
    cost is lower for your usage of this specific Server. Costs may differ between Locations.


    All prices are displayed in the currency of the project owner''s account.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Server Types
  properties:
  - type: OpenAPI
    url: openapi/hetzner-server-types-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-servers-api
  name: Hetzner Servers API
  description: Servers are virtual machines that can be provisioned.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Servers
  properties:
  - type: OpenAPI
    url: openapi/hetzner-servers-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-ssh-keys-api
  name: Hetzner SSH Keys API
  description: SSH keys are public keys you provide to the cloud system. They can be injected into Servers at creation time.
    We highly recommend that you use keys instead of passwords to manage your Servers.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - SSH Keys
  properties:
  - type: OpenAPI
    url: openapi/hetzner-ssh-keys-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-volume-actions-api
  name: Hetzner Volume Actions API
  description: The Volume Actions API from Hetzner — 8 operation(s) for volume actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Volume Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-volume-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-volumes-api
  name: Hetzner Volumes API
  description: 'A Volume is a highly-available, scalable, and SSD-based block storage for Servers.


    Pricing for Volumes depends on the Volume size and Location, not the actual used storage.


    Please see [Hetzner Docs](https://docs.hetzner.com/cloud/#Volumes) for more details about Volumes.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Volumes
  properties:
  - type: OpenAPI
    url: openapi/hetzner-volumes-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-zone-actions-api
  name: Hetzner Zone Actions API
  description: The Zone Actions API from Hetzner — 8 operation(s) for zone actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Zone Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-zone-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-zone-rrset-actions-api
  name: Hetzner Zone RRSet Actions API
  description: The Zone RRSet Actions API from Hetzner — 6 operation(s) for zone rrset actions.
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Zone RRSet Actions
  properties:
  - type: OpenAPI
    url: openapi/hetzner-zone-rrset-actions-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-zone-rrsets-api
  name: Hetzner Zone RRSets API
  description: 'This API operates on resource record sets (RRSets) instead of individual resource records (RRs).

    An RRSet is identified by a name and type. For example, the two RRs


    - (name: `@`, type: `MX`, value: `10 smtp.example.com.`) and

    - (name: `@`, type: `MX`, value: `20 smtp-backup.example.com.`)


    are part of the RRSet identified by (name: `@`, type: `MX`).


    Please see [Hetzner Docs](https://docs.hetzner.com/networking/dns/record-types/overview) for more information on types.'
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Zone RRSets
  properties:
  - type: OpenAPI
    url: openapi/hetzner-zone-rrsets-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
- aid: hetzner:hetzner-zones-api
  name: Hetzner Zones API
  description: "A Zone represents a [Domain Name System (DNS) zone](https://wikipedia.org/wiki/DNS_zone) managed by Hetzner\
    \ authoritative nameservers.\nPlease see [Hetzner Docs](https://docs.hetzner.com/dns-console/dns/general/dns-overview#the-difference-between-domain-and-zone)\
    \ for the difference between zones and domains.\n\nThis API supports all zone names with [well-known public suffixes](https://publicsuffix.org/)\
    \ (e.g. `.de`, `.com`, `.co.uk`).\nSubdomains are not supported.\n\n<h3 id=\"tag/zones/zone-modes\">Zone Modes</h3>\n\n\
    This API supports two types of zone modes.\n\n- In _primary_ mode, resource record sets ([RRSets](#tag/zone-rrsets)) and\
    \ resource records (RRs) are managed via the Cloud API or Hetzner Console.\n- In _secondary_ mode, Hetzner's nameservers\
    \ query [RRSets](#tag/zone-rrsets) and RRs from given primary nameservers via [AXFR](https://en.wikipedia.org/wiki/DNS_zone_transfer).\n\
    \nThe zone mode cannot be changed, the zone must be deleted and re-created with a new mode.\n\n### SOA Serial\n\nFor zones\
    \ in primary mode, Hetzner automatically increases the `SOA` record serial number.\nAs convention, a `YYYYMMDDnn` format\
    \ with incrementing `nn` is used.\n\n<h3 id=\"tag/zones/zone-file-import\">Zone file import</h3>\n\nThis API supports\
    \ importing a zone file in BIND (RFC [1034](https://datatracker.ietf.org/doc/html/rfc1034)/[1035](https://datatracker.ietf.org/doc/html/rfc1035))\
    \ format.\n\nImporting a zone file is only applicable for [Zones](#tag/zones) in primary mode.\n\nDuring an import:\n\n\
    - An `$ORIGIN` directive may be present, it must match the [Zone](#tag/zones)'s name with an ending dot\n- A `$TTL` directive\
    \ may be present, it is used as new default [Zone](#tag/zones) Time To Live (TTL)\n- Only `IN` (internet) class records\
    \ are allowed\n- The assigned authoritative Hetzner nameservers must be present as `NS` records\n- A `SOA` record must\
    \ be present\n- Comments for individual records are imported, comments on their own lines are discarded\n\nZone file example:\n\
    \n```dns\n$ORIGIN\texample.com.\n$TTL\t3600\n\n@\tIN\tSOA\thydrogen.ns.hetzner.com. dns.hetzner.com. 2024010100 86400\
    \ 10800 3600000 3600\n\n@\tIN\t10800\tNS\thydrogen.ns.hetzner.com. ; Some comment.\n@\tIN\t10800\tNS\toxygen.ns.hetzner.com.\n\
    @\tIN\t10800\tNS\thelium.ns.hetzner.de.\n```"
  humanURL: https://docs.hetzner.cloud/
  baseURL: https://api.hetzner.cloud/v1
  tags:
  - Zones
  properties:
  - type: OpenAPI
    url: openapi/hetzner-zones-api-openapi.yml
  - type: Documentation
    url: https://docs.hetzner.cloud/
  - type: GettingStarted
    url: https://docs.hetzner.cloud/#getting-started
common:
- type: AgenticAccess
  url: agentic-access/hetzner-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/hetzner-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/hetzner-domain-security.yml
- type: Authentication
  url: authentication/hetzner-authentication.yml
- type: GitHubOrganization
  url: https://github.com/hetzneronline
- type: LinkedIn
  url: https://www.linkedin.com/company/hetzner-online
- type: Website
  url: https://www.hetzner.com/
- type: Documentation
  url: https://docs.hetzner.com/
- type: Signup
  url: https://accounts.hetzner.com/signUp
- type: Login
  url: https://accounts.hetzner.com/login
- type: StatusPage
  url: https://status.hetzner.com/
- type: Support
  url: https://www.hetzner.com/support
- type: Pricing
  url: https://www.hetzner.com/cloud
- type: PrivacyPolicy
  url: https://www.hetzner.com/legal/privacy-policy
- type: TermsOfService
  url: https://www.hetzner.com/legal/terms-and-conditions
- url: https://www.hetzner.com/blog/
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com