August 17, 2026: The Domains API now supports batch domain availability checking via POST /v3/domains/check-availability
View as MarkdownWe've added POST /v3/domains/check-availability to the Domains API, so you can check the availability and indicative pricing of up to 25 domains in a single request instead of making one call per domain.
What changed
A new endpoint is available:
POST /v3/domains/check-availability— accepts a JSON body with adomainsarray (1–25 names) and returns oneAvailabilityresult per domain in request order inside{ "items": [...] }. Domains that cannot be checked carry anerrorobject on that item rather than failing the whole request.
One optional request field gives you control over the check behavior:
optimizeFor—SPEED(default) uses cached zone data for a fast response;ACCURACYperforms a live registry check for authoritative availability at higher latency.
Availability results are best-effort and indicative. The authoritative availability check always runs at quote time (POST /v3/domains/registration-quotes).
For single-domain checks without a request body, the existing GET /v3/domains/check-availability endpoint is unchanged.
Who is affected
Any developer building domain search or catalog experiences on the Domains API. The domains.domain:read OAuth scope is required — no new scope is needed if you already call the GET endpoint.
Existing integrations using GET /v3/domains/check-availability are unaffected.
Links
- Domains API reference —
POST /v3/domains/check-availabilityrequest and response schema - Registration quotes — authoritative availability is confirmed at quote time
Last updated on
How is this guide?