Skip to content

DNA Rest API · v1

Sell domains, DNS, SSL and hosting from your own system

One JSON API to register, renew and transfer domains, and to run their contacts, DNS, SSL certificates and hosting. Any HTTP client will do — there is no SDK to install.

  • 700+ TLDs
  • Test environment, nothing charged
  • Readable by AI agents

Give this guide to your AI agent

Pick yours and copy one line. It reads the rules before it writes the code that calls the API with your key.

Claude Code

Paste it into Claude Code, or add it to CLAUDE.md in your project so every session starts with it.

Before working on our DNA Rest API integration, read https://www.domainnameapi.com/docs/llms.txt and fetch the pages it lists that you need.

Codex

Paste it into Codex, or add it to AGENTS.md in your project so every task starts with it.

Before working on our DNA Rest API integration, read https://www.domainnameapi.com/docs/llms.txt and fetch the pages it lists that you need.

Cursor

Paste it into a Cursor chat, or add it to AGENTS.md in your project — Cursor reads it in every chat.

Before working on our DNA Rest API integration, read https://www.domainnameapi.com/docs/llms.txt and fetch the pages it lists that you need.

ChatGPT

Paste it into a new chat, or open ChatGPT with it already typed in.

Read https://www.domainnameapi.com/docs/llms-full.txt — the DNA Rest API reseller integration guide — and use it to answer my questions and write code for my integration.
Open in ChatGPT

Claude

Paste it into a new chat, or open Claude with it already typed in.

Read https://www.domainnameapi.com/docs/llms-full.txt — the DNA Rest API reseller integration guide — and use it to answer my questions and write code for my integration.
Open in Claude

Or point it at the files directly: /llms.txt lists every page,/llms-full.txt is the whole guide, and every page is Markdown at its own address plus .md — this one is /index.md.

  • Base URL: https://api.domainresellerapi.com/api/v1/
  • Authentication: the X-API-KEY and __reseller headers on every request — see Authentication.
  • Format: JSON over HTTPS. There is no SDK to install.
  • Test environment: https://ote.domainresellerapi.com with your separate test API key; registry operations are simulated and your balance is not charged. DNS records cannot be managed there — see Test environment.

Check whether a domain is available. Replace the two header values with the API key and reseller ID from your reseller panel.

Terminal window
curl -X POST https://api.domainresellerapi.com/api/v1/domains/search \
-H 'X-API-KEY: YOUR_API_KEY' \
-H '__reseller: YOUR_RESELLER_ID' \
-H 'Content-Type: application/json' \
-d '{"domainName":"apiname.com"}'

Then read Before you write any code: four decisions that prevent most integration bugs.

Not from this guide alone. It reads the rules and writes code that calls the API with your API key. Run that code against the test environment first: registry operations there are simulated and your balance is not charged.

Does my agent need an API key to read the guide?

Section titled “Does my agent need an API key to read the guide?”

No. Every page, /llms.txt and /llms-full.txt are public.

/llms.txt: one line per page, so the agent fetches only what it needs. Every page is also Markdown at its own address plus .md, for example /domains/register.md; All pages lists them all. If your agent can take a large file in one go, /llms-full.txt is the whole guide, about 300 KB.

The Markdown is built from the same source as these pages, so they never disagree. The TLD pages come from the catalogue on the date shown at the bottom of each one; in your code, read live values from GET /api/v1/products/tlds.

Open a ticket from your reseller panel. Include your X-Correlation-ID and, for paid operations, the traceId from your transaction list.