DNA Rest API
Everything in this guide, your AI agent can read too. See how
At a glance
Section titled “At a glance”- Base URL:
https://api.domainresellerapi.com/api/v1/ - Authentication: the
X-API-KEYand__resellerheaders on every request — see Authentication. - Format: JSON over HTTPS. There is no SDK to install.
- Test environment:
https://ote.domainresellerapi.comwith your separate test API key; registry operations are simulated and your balance is not charged.
Your first request
Section titled “Your first request”Check whether a domain is available. Replace the two header values with the API key and reseller ID from your reseller panel.
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.
Find what you need
Section titled “Find what you need”Your AI agent can build the integration
Claude Code reads the whole guide before it writes a line
/llms-full.txtCursor writes your registration flow, extra registry fields included
/domains/register.mdCodex fills in the
tldAttributes.com.tr asks for/tlds/com.tr.mdChatGPT explains an error code and what to do about it
/reference/errors.mdClaude 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.
Set up your agent →llms.txt →The whole guide →All endpoints →
Give the guide to your agent
Section titled “Give the guide to your agent”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.Add this line to AGENTS.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.Add this line 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.Every page has Open in ChatGPT and Open in Claude under its title. To give a chat the whole guide, paste this link:
https://www.domainnameapi.com/docs/llms-full.txtQuestions
Section titled “Questions”Can my agent call the API for me?
Section titled “Can my agent call the API for me?”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.
Which file should it read first?
Section titled “Which file should it read first?”/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.
How current is it?
Section titled “How current is it?”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.
Support
Section titled “Support”Open a ticket from your reseller panel. Include your X-Correlation-ID and, for paid operations, the traceId from your transaction list.