Skip to content

DNA Rest API

Register and manage domain names, contacts, DNS, SSL certificates and hosting from your own system. JSON over HTTPS — any HTTP client will do.

Everything in this guide, your AI agent can read too. See how

Claude CodeCursorCodexChatGPTClaude
  • 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.

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.

Your AI agent can build the integration

  1. Claude Code reads the whole guide before it writes a line

    /llms-full.txt
  2. Cursor writes your registration flow, extra registry fields included

    /domains/register.md
  3. Codex fills in the tldAttributes .com.tr asks for

    /tlds/com.tr.md
  4. ChatGPT explains an error code and what to do about it

    /reference/errors.md
  5. Claude checks your renewal logic against the rules

    /domains/renew.md

Every page of this guide is also plain Markdown, written so a coding agent can follow it as well as you can. Your agent reads the rules, then writes the code that calls the API with your key.

Add this line to CLAUDE.md in your project:

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.

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. 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.