Client area

GET · DNS zones & records

List the account's DNS zones

List the account's DNS zones

GET /api/v1/dns/zones
R Read
Scope read:dns

This scope is inferred from the method and the endpoint's group — the OpenAPI document does not carry one per operation. The wire is authoritative; whoami reports what your token actually holds.

Description

Returns data[] of zones — {domain, isPrimary, daUsername, node, serviceId} — across every hosting account on the user. For one zone's health/record counts use get_dns_zone; for the records themselves use list_dns_records.

Parameters

This operation takes no parameters. Authentication is the bearer token in the Authorization header.

Responses

A 200 response returns the shape shown in the rail. Every non-2xx response is an RFC 7807 problem with a stable code.

Commonly returned errors

The codes this operation reaches on its own path: the auth stack, its own validation and ownership checks, and the transport. Not a closed set — a shared code from the full registry can still surface. Each links to the code’s own page, the same URL its type dereferences to.

401 No token was presented, or the token is revoked, expired or unknown.
403 The token lacks a required scope, or this account does not own the resource.
429 The rate limit for this token is exhausted. See `Retry-After`.
500 Something went wrong on our side. The failure is logged against `requestId`.
Esc
navigate open Esc close