Name.com Core API (1.0.1)

RESTful API for managing domains, DNS records, and related services at Name.com. Access via HTTPS at api.name.com (production) or api.dev.name.com (testing). Supports standard authentication, rate-limited to 20 requests/second.

Download OpenAPI description
Languages
Servers
Mock server

https://docs.name.com/_mock/coreapi/namecom.api/

Testing

https://api.dev.name.com/

Hello

Use the Hello endpoint to verify that your API connection and credentials are working properly. This simple call returns a success message (along with server time and version info) to confirm the API is reachable and authenticated.

Operations

Account Info

Use Account Info endpoints to retrieve basic information about your Name.com account. For example, you can check your account’s current credit balance and other account details using these endpoints.

Operations

Accounts

Use Accounts endpoints (available upon request) to manage sub-accounts under your main account. For example, resellers can programmatically create new customer accounts with their own login credentials and permissions.

Operations

Domains

Use Domains endpoints to search for domain availability, register new domains, and manage existing domains.

Operations

Enable Whois PrivacyDeprecated

Request

Enables WHOIS privacy protection on a domain. DEPRECATED This endpoint is deprecated in favor of the new UpdateDomain API. This will be removed in a future release.

Path
domainNamestringrequired

DomainName is the domain name to enable whoisprivacy for.

Headers
Content-Typestringrequired

Required Content-Type Header for POST requests.

Value"application/json"
curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}:enableWhoisPrivacy' \
  -H 'Content-Type: application/json'

Responses

A successful response.

Bodyapplication/json
domainNamestring

The punycode-encoded value of the domain name.

Example: "example.com"
createDatestring(date-time)read-only

The date and time when the domain was created at the registry.

Example: "2023-01-15T14:30:00Z"
expireDatestring(date-time)read-only

The date and time when the domain will expire.

Example: "2025-01-15T14:30:00Z"
autorenewEnabledboolean

Indicates whether the domain is set to renew automatically before expiration.

Example: true
lockedboolean

Indicates if the domain is locked, preventing transfers to another registrar.

Example: true
privacyEnabledboolean

Indicates if Whois Privacy is enabled for this domain.

Example: true
contactsobject(Contacts)

Contacts stores the contact information for the roles related to domains.

nameserversArray of strings

The list of nameservers assigned to this domain. If unspecified, it defaults to the account's default nameservers.

Example: ["ns1.example.com","ns2.example.com"]
renewalPricenumber(double)read-only

The cost to renew the domain. This may be required for the RenewDomain operation.

Example: 12.99
Response
application/json
{ "domainName": "example.com", "createDate": "2023-01-15T14:30:00Z", "expireDate": "2025-01-15T14:30:00Z", "autorenewEnabled": true, "locked": true, "privacyEnabled": true, "contacts": { "admin": {}, "billing": {}, "registrant": {}, "tech": {} }, "nameservers": [ "ns1.example.com", "ns2.example.com" ], "renewalPrice": 12.99 }

Lock DomainDeprecated

Request

Locks a domain to prevent it from being transferred. DEPRECATED This endpoint is deprecated in favor of the new UpdateDomain API. This will be removed in a future release.

Path
domainNamestringrequired

DomainName is the domain name to lock.

Example: example.com
Headers
Content-Typestringrequired

Required Content-Type Header for POST requests.

Value"application/json"
curl -i -X POST \
  -u <username>:<password> \
  https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/example.com:lock \
  -H 'Content-Type: application/json'

Responses

A successful response.

Bodyapplication/json
domainNamestring

The punycode-encoded value of the domain name.

Example: "example.com"
createDatestring(date-time)read-only

The date and time when the domain was created at the registry.

Example: "2023-01-15T14:30:00Z"
expireDatestring(date-time)read-only

The date and time when the domain will expire.

Example: "2025-01-15T14:30:00Z"
autorenewEnabledboolean

Indicates whether the domain is set to renew automatically before expiration.

Example: true
lockedboolean

Indicates if the domain is locked, preventing transfers to another registrar.

Example: true
privacyEnabledboolean

Indicates if Whois Privacy is enabled for this domain.

Example: true
contactsobject(Contacts)

Contacts stores the contact information for the roles related to domains.

nameserversArray of strings

The list of nameservers assigned to this domain. If unspecified, it defaults to the account's default nameservers.

Example: ["ns1.example.com","ns2.example.com"]
renewalPricenumber(double)read-only

The cost to renew the domain. This may be required for the RenewDomain operation.

Example: 12.99
Response
application/json
{ "domainName": "example.com", "createDate": "2023-01-15T14:30:00Z", "expireDate": "2025-01-15T14:30:00Z", "autorenewEnabled": true, "locked": true, "privacyEnabled": true, "contacts": { "admin": {}, "billing": {}, "registrant": {}, "tech": {} }, "nameservers": [ "ns1.example.com", "ns2.example.com" ], "renewalPrice": 12.99 }

Unlock DomainDeprecated

Request

Unlocks a domain to allow it to be transferred. DEPRECATED This endpoint is deprecated in favor of the new UpdateDomain API. This will be removed in a future release.

Path
domainNamestringrequired

DomainName is the domain name to unlock.

Headers
Content-Typestringrequired

Required Content-Type Header for POST requests.

Value"application/json"
curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}:unlock' \
  -H 'Content-Type: application/json'

Responses

A successful response.

Bodyapplication/json
domainNamestring

The punycode-encoded value of the domain name.

Example: "example.com"
createDatestring(date-time)read-only

The date and time when the domain was created at the registry.

Example: "2023-01-15T14:30:00Z"
expireDatestring(date-time)read-only

The date and time when the domain will expire.

Example: "2025-01-15T14:30:00Z"
autorenewEnabledboolean

Indicates whether the domain is set to renew automatically before expiration.

Example: true
lockedboolean

Indicates if the domain is locked, preventing transfers to another registrar.

Example: true
privacyEnabledboolean

Indicates if Whois Privacy is enabled for this domain.

Example: true
contactsobject(Contacts)

Contacts stores the contact information for the roles related to domains.

nameserversArray of strings

The list of nameservers assigned to this domain. If unspecified, it defaults to the account's default nameservers.

Example: ["ns1.example.com","ns2.example.com"]
renewalPricenumber(double)read-only

The cost to renew the domain. This may be required for the RenewDomain operation.

Example: 12.99
Response
application/json
{ "domainName": "example.com", "createDate": "2023-01-15T14:30:00Z", "expireDate": "2025-01-15T14:30:00Z", "autorenewEnabled": true, "locked": true, "privacyEnabled": true, "contacts": { "admin": {}, "billing": {}, "registrant": {}, "tech": {} }, "nameservers": [ "ns1.example.com", "ns2.example.com" ], "renewalPrice": 12.99 }

DNS

Use DNS endpoints to manage DNS records for your domains. You can list all existing DNS records for a domain and create, update, or delete records as needed.

Operations

DNSSECs

Use DNSSEC endpoints to configure DNS Security Extensions for your domains. These endpoints allow you to add, retrieve, or remove DNSSEC records.

Operations

Email Forwardings

Use Email Forwardings endpoints to set up and manage email forwarding addresses on your domains.

Operations

URL Forwardings

Use URL Forwardings endpoints to control URL redirection settings for your domains.

Operations

Vanity Nameservers

Use Vanity Nameservers endpoints to configure custom nameserver hostnames (glue records) for your domains.

Operations

Transfers

Use Transfers endpoints to move domains into your Name.com account. Start by creating a transfer request, then monitor and manage the status of pending transfers. You can also cancel a transfer if needed.

Operations

Orders

Use Orders endpoints to review and track purchases made via the API.

Operations

Webhook Notifications

Use Webhook Notification endpoints to subscribe to real-time notifications for account and domain events. This keeps your application updated on important changes without polling the API.

OperationsWebhooks