Your domains.
Your workflow.

One key. All features.

Open Profile → API → Create key in the bot. Save the secret: it is displayed once. The same balance and domains are shared by the bot and the API.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

No key types, spending caps or request quotas. Your available balance pays for purchases. The key has no automatic expiry. Replace or disable it in the bot; the old key stops working immediately. Keep it out of URLs, public prompts, logs and source control.

From search to registration

1. GET /account

   Check balance and purchases_enabled.

2. POST /domains/search

   Find available names. Search prices are indicative.

3. POST /quotes

   Get the exact total, Prime discount and expiry. No purchase yet.

4. POST /orders/{id}/confirm

   Verify the amount before confirmation. This reserves funds and starts the purchase.

5. GET /orders/{id}

   Poll until completion. Inspect each item for partial orders. Check Cloudflare and TLS separately on the domain.

Retry safely

Every write except read-only search requires Idempotency-Key: 8–128 ASCII letters, digits or . _ : -. Use a new key for each distinct action; retry the same action with the same key and identical JSON. A changed payload returns 409.

DNS, NS & Cloudflare

GET DNS returns a saved provider snapshot. Queue dns.sync and await success to refresh it. Changes run asynchronously through domain operations. dns.rrset requires the expected signature from the snapshot. New Cloudflare connections require Prime; existing connections remain editable after expiry. SSL issuance and DNS propagation are asynchronous. Changing nameservers can affect website availability.

Errors & statuses

error.code · error.message · request_id