Domains REST reference
View as MarkdownREST reference for the Domains API. v3 quote-execute registration, plus v1/v2 for DNS, contacts, transfers, and forwarding.
Machine-readable specs
The complete OpenAPI specs for this namespace are available as JSON — useful for code generation, SDK tooling, and LLM context: domains-v3.json (discovery + registration), domains-v1.json (account-scoped), and domains-v2.json (async operations).
The Domains REST API exposes domain availability search, registration, DNS and contact management, registry lock, WHOIS privacy, forwarding, and inbound and outbound transfers. Operations span three version namespaces: v3 (quote-execute registration model), v1 (account-scoped), and v2 (async operation tracking).
For a task-shaped guide written for DIY API users, see Use the API → Domains.
The core objects
The Domains namespace is built around a small set of resources. Each operation in the reference reads or writes one of these objects.
| Object | Description |
|---|---|
DomainDetail (v1) / DomainDetailV2 (v2) | A registered domain and its registry metadata: name, status, expiration, contacts, nameservers, lock state, and privacy state. |
DNSRecord | A single DNS record (A, AAAA, CNAME, MX, TXT, SRV, NS, SOA, or CAA) on a domain that uses GoDaddy's authoritative nameservers. |
Contact | A WHOIS contact record covering name, organization, address, email, and phone. The same shape is used for the registrant, admin, billing, and tech roles on a domain. |
Action | An asynchronous-operation tracker returned with 202 Accepted when the API queues a long-running write. Callers poll the action endpoint until the action's status reaches a terminal state. |
DomainAvailableResponse | The result of an availability check, including the available flag, current price in currency-micro-unit format, the registration period in years, and whether the answer is from a live registry call or cache. |
DomainForwarding | An HTTP forwarding rule on a domain, configurable as masked or unmasked and as a permanent (301) or temporary (302) redirect. |
DomainTransferIn | The request shape for an inbound transfer, carrying the domain name, authcode, and required contacts. |
Error / ErrorLimit | The standard error envelope returned on 4xx and 5xx responses across the namespace. ErrorLimit extends Error with retryAfterSec for 429 rate-limited responses. |
Version namespaces
v3 — quote-execute model
Discovery (check-availability, suggestions) and registration via a quote-execute flow. All writes are async with a poll URL. v3 does not yet cover DNS, renewals, transfers, contacts, forwarding, or privacy.
v1 — account-scoped
Operations under /v1/domains/... act on the domains owned by the authenticated account. Use for DNS, contacts, privacy, renewals, transfers, and anything not yet in v3.
v2 — async operations
v1 capabilities plus async operation tracking — action queues, status polling, notifications, and forwarding. Use when you need to track long-running writes like transfers and redemptions.
Conventions used across the namespace
| Concern | Where it's documented |
|---|---|
Authentication (PAT for v3; PAT or legacy sso-key for v1/v2) | Authentication |
| Error envelope and retry semantics | Errors |
| Rate limits (60 requests/minute per credential) | Rate limits |
| Cursor-based pagination on v1 list endpoints | Pagination |
Related references
Last updated on
How is this guide?