GET · Meta & discovery
One TLD's pricing and registry requirements
One TLD's pricing and registry requirements
GET
/api/public/v1/products/domains/{tld}
Description
Returns register / renew / transfer price, the term bounds and the registry rules for the TLD. Use get_domain_pricing for a table across many TLDs.
Path parameters
| Name | Type | Description |
|---|---|---|
tld
required
|
string |
Query parameters
| Name | Type | Description |
|---|---|---|
tld
|
string | Up to 20 characters. |
currency
|
enum |
One of SEK, EUR, null.
|
locale
|
enum |
One of sv, en, null.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
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.
404
No such resource for this account.
422
Validation error
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`.