Check domain availability with the Domain Nexus v2 API

Use a credential with domains:availability and a valid idempotency key. Submit up to 50 full names in the documented domains array. Normalise names carefully and use the supported ASCII form for internationalised names.

POST /v2/domains/availability
Idempotency-Key: availability-search-1042
Content-Type: application/json

{
  "domains": ["example.com", "example.net"]
}

The examples are documentation names, not names you should attempt to purchase. In your application, preserve the link between each requested name and its individual result.

1. Read each result's domain and availability status.
2. Distinguish registered, reserved, unsupported and available outcomes where the provider returns them.
3. Review any premium information and whether its price is actually known.
4. Check the account's offered TLD and operation terms before presenting a purchasable option.

A name being unavailable is different from a failed query. Do not convert a timeout, unsupported TLD or provider error into an available result.

Availability can change before registration and does not reserve the domain. Obtain the applicable registry requirements and price quote, collect the customer's contact data and consents, then submit the registration through its dedicated workflow.

A premium flag by itself is not permission to charge an arbitrary amount. Use the actual offered premium pricing and customer acceptance process. A suggested name also needs an availability check; suggestions are not reservations.

Keep batches within the documented limit, respect rate guidance and avoid sending the same search repeatedly while a request is in progress. If you cache results, label them as recent search results and recheck before a paid order.

Use a new business reference for a genuinely new search; retain the original idempotency key for an unchanged transport retry. Record errors without logging account credentials. For unexpected results, provide support with the queried name, time and request reference.

• Get started with the current Nabtech Domain Nexus v2 API
• Register a domain using the current Domain Nexus v2 workflow
• Create a domain-operation quote and keep its currency and expiry attached to the order
• Build domain forms from current registry field and consent requirements