Skip to main content

name.com CORE API – FAQ

Use HTTP Basic Authentication with your name.com username and API token. You can use curl’s -u username:token shorthand or send an explicit Authorization: Basic <base64(username:token)> header. See the full Authentication guide for Linux/macOS and Windows PowerShell commands to generate the Base64 value.
❌ No. Accounts with 2FA enabled cannot authenticate. Disable 2FA and enable API Access in your account settings.
❌ No. The API is for server-side use only. Browser requests are blocked due to CORS restrictions.
✅ Yes. Any tool that can send HTTPS requests — including PowerShell, curl, Python, or Node.js — is supported. For a PowerShell example to generate the Basic Auth header, see Authentication.
All API requests must use HTTPS on port 443.
❌ No. Domains, DNS records, and user data are completely separate between environments.
❌ No. The sandbox uses registry test data, so domain availability and behavior may differ.
Use the sandbox environment (https://api.dev.name.com) with your -test username and sandbox API token. Sandbox domains are not live or publicly registered.
The API uses standard RESTful HTTP codes like 200 OK, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, and 429 Too Many Requests.
The domain must exist in the environment you’re querying. Check whether you’re using sandbox or production.
You can check up to 50 domains per checkAvailability call.
You’ll receive a 429 Too Many Requests error. Use backoff logic and retry after a delay.
✅ Yes. You can use saved credit card profiles and account credit for domain purchases via the API. Ensure your preferred payment method is set as the default payment method within your account.
🔔 Check the Changelog for the latest version releases, features, and any upcoming deprecations.

Next Steps

I