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

Get Pricing For Domain

Request

Retrieves the registration and renewal pricing for a given domain.

Path
domainNamestringrequired

DomainName is the domain to retrieve.

Query
yearsinteger(int32)

Years specifies the time period in years to get pricing for the domain. Years defaults to the minimum time period (typically 1 year) if not passed and cannot be more than 10. Some TLDs default to longer periods (e.g. .AI requires 2 year periods).

Example: years=2
curl -i -X GET \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}:getPricing?years=2'

Responses

A successful response.

Bodyapplication/json
premiumbooleanrequired

Premium indicates that this pricing is a premium result and the respective prices must be passed in create, renew or transfer commands.

purchasePricenumber(double)required

PurchasePrice is the price you will pay to register a domain. Can be passed in the CreateDomain request.

Example: 24.99
renewalPricenumber(double)required

RenewalPrice is the price you will pay to renew a domain. Can be passed in the RenewDomain request.

Example: 24.99
transferPricenumber(double)required

TransferPrice is the price you will pay to transfer a domain. Can be passed in the CreateTransfer request. The TransferPrice is always for 1 year regardless of the years input.

Example: 24.99
Response
application/json
{ "premium": true, "purchasePrice": 24.99, "renewalPrice": 24.99, "transferPrice": 24.99 }

Purchase Privacy

Request

Adds or renews WHOIS privacy protection for a domain. This is used to ensure personal contact details remain hidden from public WHOIS lookups. If WHOIS privacy is already enabled, this will extend the protection. If it’s not yet active, this will both purchase and enable the service. This is a billable action unless covered by a bundled privacy plan.

Path
domainNamestringrequired

DomainName is the domain to purchase Whois Privacy for.

Bodyapplication/jsonrequired
purchasePricenumber(double)

PurchasePrice is the (prorated) amount you expect to pay.

yearsinteger(int32)

Years is the number of years you wish to purchase Whois Privacy for. Years defaults to 1 and cannot be more then the domain expiration date.

curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}:purchasePrivacy' \
  -H 'Content-Type: application/json' \
  -d '{
    "purchasePrice": 0.1,
    "years": 0
  }'

Responses

A successful response.

Bodyapplication/json
domainobject(DomainResponsePayload)

Domain contains all relevant data for a domain.

orderinteger(int32)required

Order is an identifier for this purchase.

totalPaidnumber(double)required

TotalPaid is the total amount paid, including VAT.

Example: 4.99
Response
application/json
{ "domain": { "domainName": "example.com", "createDate": "2023-01-15T14:30:00Z", "expireDate": "2025-01-15T14:30:00Z", "autorenewEnabled": true, "locked": true, "privacyEnabled": true, "contacts": {}, "nameservers": [], "renewalPrice": 12.99 }, "order": 0, "totalPaid": 4.99 }

Renew Domain

Request

Renews an existing domain for an additional registration period. Include the domain name and renewal term. If the domain has non-standard pricing (e.g. premium), the purchasePrice must be passed. This is typically used to extend ownership before a domain’s expiration.

Path
domainNamestringrequired

DomainName is the domain to renew.

Bodyapplication/jsonrequired
purchasePricenumber(double)

PurchasePrice is the amount in USD to pay for the domain renewal at the minimum renewal period (typically 1 year). If VAT tax applies, it will also be added automatically. PurchasePrice is required if this is a premium domain.

Example: 10.99
yearsinteger(int32)

Years specifies how many years to renew the domain for. Years defaults to the minimum time period (typically 1 year) if not passed and cannot be more than 10. Some TLDs default to longer periods (e.g. .AI requires a 2 year renewal).

Example: 3
curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}:renew' \
  -H 'Content-Type: application/json' \
  -d '{
    "purchasePrice": 10.99,
    "years": 3
  }'

Responses

A successful response.

Bodyapplication/json
domainobject(Domain)

Domain contains all relevant data for a domain.

orderinteger(int32)(Order is an identifier for this purchase)
totalPaidnumber(double)

TotalPaid is the total amount paid, including VAT.

Example: 5.95
Response
application/json
{ "domain": { "domainName": "example.com", "createDate": "2023-01-15T14:30:00Z", "expireDate": "2025-01-15T14:30:00Z", "autorenewEnabled": true, "locked": true, "privacyEnabled": true, "contacts": {}, "nameservers": [], "renewalPrice": 12.99 }, "order": 0, "totalPaid": 5.95 }

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