API

Manage domains from a program rather than a page at a time.

Wire registration, availability checks, DNS and management into your own systems: bulk ordering, renewal sweeps, a control panel for your customers.

The API is the machine entry point to the same operations the client area offers. What you can do on a page, you can script.

REST HTTPS with JSON responses
API keys Created and revoked in the client area
Full coverage The same operations as the client area
Auditable Calls are recorded on the account

What it is

  • Endpoints are grouped by resource - availability, domains, nameservers, contacts, orders and invoices - and return JSON.
  • Authentication uses an API key generated in the client area, which can be revoked and replaced at any time.
  • Typical uses: bulk registration, expiry sweeps, syncing domain state into your own system, a self-service panel for clients, and automated certificate workflows.
  • The same business rules apply as on the web: a domain cannot be registered out of thin air, and a transfer still needs an unlocked domain and 60 days.

How it works

01

Create a key

Generate an API key in the client area, scoped to what it needs to do.

02

Read the documentation

Endpoints, parameters and response shapes.

03

Test small

Try read-only endpoints, or a couple of domains, before automating.

04

Go live with logging

Add retries and logging before it touches production.

Availability and search

Check many names at once for monitoring and selection.

Registration and renewal

Order, renew and read order status.

DNS and nameservers

Push records and nameserver changes in bulk.

Contact management

Read and update registrant, admin, tech and billing.

Orders and invoices

Read orders, invoices and payment status.

Key rotation

Revoke and replace keys; keep each system on its own key.

What the API covers

By resource

ResourceWhat you can do
DomainsCheck availability, register, renew, read status and expiry
DNSRead and set nameservers, maintain DNS records
Privacy and contactsSet the privacy level, update all four contact roles
Orders and billingRead orders, invoices and payment status
AccountRead the balance and basic account details

What to have in place before you connect

Four small things that save most of the debugging

  • Balance or a working payment method: registration and renewal are real orders, and a call will fail at the ordering step without funds.
  • Retries and error handling: network blips, rate limits and upstream delays happen. Retry idempotent reads; for orders, send a unique reference and check before writing again.
  • Logging: record the reference, the domain and the response code. When something is disputed later, those logs are the only proof that the action happened.
  • Least privilege: do not use a writable key for a read-only job, and give each system its own key so one can be revoked without breaking the others.

An API key is equivalent to an account password. Keep it in a server-side environment variable or a secrets manager, never in front-end code, and never in a repository.

How people use it

Common patterns

  • Bulk registrar: submit a selection for registration and write the results back into your own backend.
  • Renewal sweeps: pull domains approaching expiry nightly and raise your own reminder or renewal tasks.
  • White-label panels: let your customers manage domains inside your product, without signing in here.
  • Reconciliation: pull domain and order data on a schedule and match it against your own ledger.

What every order includes

API key management

Create, revoke and separate keys by purpose.

Documentation

Endpoints, parameters and responses.

Domain and DNS endpoints

Search, register, renew, DNS and nameservers.

Order and billing endpoints

Orders, invoices and payment status.

Call history

Recorded against the account for troubleshooting.

Support

Open a ticket if an integration misbehaves.

Common questions

Is there an extra charge for the API?

The API itself is not charged separately; you pay for the business operations it performs. There is a sensible rate limit to prevent accidental or abusive use.

Is there an SDK?

The API is standard HTTPS and JSON, so any HTTP client works. The documentation includes request examples that can be adapted directly.

What if a key leaks?

Revoke it in the client area and generate a new one. Revocation takes effect immediately and requests using the old key are rejected.

Does testing cost anything?

Read-only calls cost nothing. Registration and renewal are real orders and do cost money, so validate the logic on a small number of domains first.

Can the API manage domains registered elsewhere?

No. It operates on the domains in this account, exactly as the client area does.

Please note

  • Keep API keys on the server. A key shipped in browser code or a mobile bundle is a published key.
  • For ordering endpoints, send a unique request reference and check before writing, so that a network retry does not register or charge twice.

Ready to start?

Open the page for this service and finish in a few steps. If you would rather ask first, a ticket reaches a person.