public
GET /v1/public/domains/tld-requirements
What each extension's registry demands before it will register a name.
Authentication
This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/public/domains/tld-requirements?tlds=<tlds>Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Q10. For each named extension: whether it can be ordered online, which registrant countries and entity types the registry accepts, and every extra field it demands (registry_data on checkout and on a partner order) — identity, tax, company or VAT numbers on the owner, extension data such as the .us nexus, domain fields such as the .ca legal type, and registry acceptances. Read from the registrar's own per-extension API specification and documentation, with the source and its date on every row. No account, no registrar call; cacheable for an hour.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
tlds (query) | string | Yes | Comma-separated extensions without the dot (es,it,com.au), at most 50. |
op (query) | string<register, transfer> | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
tlds | TldRequirements[] | Yes | — |
sources | object | Yes | Where and when the registry data was read (API, knowledge base, curated rules). |
Errors this endpoint can return
422 · 429