Skip to content

name.com Core API (1.8.2)

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
namecom.api.json
namecom.api.yaml
Overview
Account Services

accountservices@name.com

Terms of Service

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

Contact Verification

Use Contact Verification endpoints to query a reseller’s unverified domains/emails and to programmatically mark an end user’s email as verified if the reseller has already completed the verification process. These endpoints help resellers meet ICANN requirements by ensuring end users confirm they can receive email at their listed address.

Operations

List Unverified Contacts

Request

Returns a list of contacts, related to domains within your account, that require verification as per ICANN procedures. When a new domain is created, unverified contacts are not immediately available in API responses. Records are added by a scheduled process that runs approximately every 10 minutes. As a result, there may be up to a 10-minute delay before unverified contacts appear in the API. This delay also applies to related events such as webhooks or other downstream systems that depend on contact verification data. This API is only available to approved reseller accounts. Contact name.com support to request access.

Security
BasicAuth
Query
perPageinteger(int32)>= 1

PerPage is the number of records to return per request. If not passed in the request, the default value is 100 records.

Default 100
Example: perPage=100
pageinteger(int32)>= 1

Page is which page to return. If not passed in the request, the default page is 1.

Default 1
Example: page=2
curl -i -X GET \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/contacts/unverified?perPage=100&page=2'

Responses

A successful response containing an array of unverified contacts. This array may be empty if there are no unverified contacts related to domains in your account.

Bodyapplication/json
unverifiedContactsArray of objects(UnverifiedContact)required
unverifiedContacts[].​verificationIdnumber(int64)required

The id of the verification record for the contact. Please note, this is different than the contact_id that may be returned in other API contexts. This id specifically relates to the verification and will be different than an contact_id for the same contact record in other contexts.

Example: 4897668
unverifiedContacts[].​createDatestring(date-time)read-onlyrequired

The date the record requiring verification was created.

Example: "2025-01-01T15:35:06Z"
unverifiedContacts[].​verifyBystring(date-time)read-onlyrequired

The date/time that the contact record must be verified by. If the contact record is not verified by this date, the domain may become locked by the registry. This is typically 15 days from the creation date of the verification record, but may vary by TLD and registry.

Example: "2025-01-16T15:35:06Z"
unverifiedContacts[].​emailstring(email)read-onlyrequired

The email address of the contact to be verified. This is the primary identifier used for verification.

Example: "admin@example.com"
unverifiedContacts[].​domainsArray of strings(hostname)non-emptyrequired

A list of the domains that the contact verification record is applied to.

frominteger(int32)required

From is the starting record for the current page.

Example: 1
tointeger(int32)required

To is the ending record for the current page.

Example: 25
lastPageinteger(int32)required

LastPage is the identifier for the final page of results. This value will be null if there is not a previous result page.

nextPageinteger or null(int32)required

NextPage is the identifier for the next page of results. This value will be null if there is not a next page of results.

totalCountinteger(int32)required

TotalCount is total number of domains returned for request.

Response
application/json
{
  "unverifiedContacts": [
    { … }
  ],
  "from": 1,
  "to": 25,
  "lastPage": 0,
  "nextPage": 0,
  "totalCount": 0
}

Verify Contact

Request

Use this API to verify a contact. This API is only available to approved reseller accounts. Contact name.com support to request access.

Security
BasicAuth
Path
verificationIdinteger(int32)required

The VerificationId required to verify a specific contact.

Example: 98752463
Headers
X-Idempotency-Keystring

A unique string (e.g., a UUID v4) to make the request idempotent. This key ensures that if the request is retried, the operation will not be performed multiple times. Subsequent requests with the same key will return the original result.

Example: 083910ef-04e4-4bd1-a0bf-3737fe005ca8
curl -i -X POST \
  -u <username>:<password> \
  https://docs.name.com/_mock/coreapi/namecom.api/core/v1/contacts/verify/98752463 \
  -H 'X-Idempotency-Key: 083910ef-04e4-4bd1-a0bf-3737fe005ca8'

Responses

Contact has been successfully verified.

Response
No content

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

Domain Info

Use Domain Info endpoints to retrieve information about TLD-specific requirements and registration rules. These endpoints help you understand what fields, documents, or constraints are needed to successfully register domains across different TLDs.

Operations

TLD Pricing

Use TLD Pricing endpoints to retrieve general pricing information for your account.

Operations

Premium Domains

APIs for working with Premium Domains.

Operations