Getting Started with the API

Developers often ask whether Domain India has an API for managing an account in code. There's no general REST API with API keys for your whole account. There are four supported ways to work with your services programmatically, and each one covers a different job. This guide explains which to use and how to make your first call safely.

1. What is and isn't available

Older versions of this page described an API address, token menu and endpoints that do not exist. If you have code written against them, it will not work. Use one of the routes above instead.

2. Connect an assistant or MCP client

Domain India runs a Model Context Protocol (MCP) server at https://domainindia.com/mcp. You connect with OAuth: you sign in to your Domain India account and approve permissions on our own page. There is no API key or client ID to copy. More about using AI assistants with your account: Domain India for AI assistants.

For developers. Claude Code:

claude mcp add --transport http domain-india https://domainindia.com/mcp

Then sign in from /mcp. Cursor (~/.cursor/mcp.json):

{"mcpServers": {"domain-india": {"url": "https://domainindia.com/mcp"}}}

VS Code (.vscode/mcp.json):

{"servers": {"domain-india": {"type": "http", "url": "https://domainindia.com/mcp"}}}

There is no auth field. The client opens your browser for sign-in the first time it connects.

What each permission allows

Some things are never possible through this connection, whatever you approve: making a payment or placing an order, cancelling a service, changing nameservers or domain contacts, getting a domain's transfer (EPP) code, and seeing a password. Access keys last one hour and renew in the background. A connection unused for 30 days lapses, and you can disconnect any app instantly on the Connected apps page.

In ChatGPT, publishing a website and getting order or renewal links are not available yet. You can build and edit a site there, then publish it from your client area (or from Claude).

The full walkthrough, with screens for each assistant, is Connecting your Domain India account to an AI assistant.

3. Deploy App Platform apps from CI

For the App Platform, the programmatic route is a deploy token. In your app's Deploy Tokens tab, click Create Token. The token is shown once, together with a ready-to-run command that already contains your token and your app's deploy address. Package your project with tar, then run that command from your terminal or CI job. A connected assistant with the Deploy apps permission can also create a deploy token for you.

• Each token works for one app only, and you can hold up to 5 per app.
• Uploads can be up to 512 MB.
• There is no automatic deploy on push. Your CI job runs the command.
• Copy the command from the tab. Don't type the deploy address from memory.

The full guide is Deploying with a deploy token.

4. Script your cPanel hosting with UAPI

On cPanel hosting, you can call your own account's cPanel API (UAPI) over HTTPS on port 2083. This is cPanel's own API, separate from the assistant connection.

curl -s -H "Authorization: cpanel yourusername:YOUR_API_TOKEN" \
  "https://your-panel-host:2083/execute/Email/list_pops"

A working call returns JSON with "status": 1 and a data array. A status of 0 comes with an errors array that explains what failed. Other modules follow the same pattern: /execute/Module/function.

Keep these limits in mind:

• WHM's API (port 2087) is not available to shared hosting accounts. UAPI covers your own account only.
• Scripts that run on the hosting itself have some PHP functions disabled on shared hosting, including proc_open and stream_socket_client. See PHP disabled functions on shared hosting.
• DirectAdmin hosting does not offer customer API login keys. Webuzo and Windows (Plesk) hosting have no API route documented here, so ask support if you need one.

To try calls interactively, see API testing with Postman.

5. Keep tokens and connections safe

• One token per purpose. Name each token after the script or pipeline that uses it, so you can revoke one without breaking the others.
• Least privilege. On the permission screen, tick only what the assistant needs. Leave the "change" permissions (DNS, email, websites, apps, support) off unless you want it to act on them.
• Check the return address, not the name. On the permission screen, an app's name is only a claim. If you did not just start a connection yourself, deny the request.
• Review regularly. Check Connected apps, and your cPanel token list, every few months and remove anything unused.

6. What to do when you need more

If your project needs something these routes don't cover, such as registering domains in bulk from your own software, open a ticket and describe the use case. Support will tell you what is possible. Until then, orders, payments, renewals and transfers are done in the client area.

If you are choosing where to build: the App Platform runs Node.js apps automatically and anything else with a Dockerfile, with deploy tokens for CI. cPanel hosting suits PHP sites that you script through UAPI. A VPS gives you full control of your own server.

Ready to automate? Connect an assistant from Connected apps, read Deploying with a deploy token for CI, or open a ticket if your use case isn't covered. Support is on 24/7 live chat, and tickets get a first response within 15 minutes.