Skip to content
Domains
/
Get Pricing For Domain

name.com Core API (1.3.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
namecom.api.json
namecom.api.yaml
Overview
Account Services

accountservices@name.com

Terms of Service

Languages
Servers
Mock server

https://docs.name.com/_mock/api-spec-cdn/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 Auth Code For Domain

Request

Retrieves the transfer authorization code (EPP code) for a domain.

Security
BasicAuth
Path
domainNamestringrequired

DomainName is the domain name to retrieve the authorization code for.

curl -i -X GET \
  -u <username>:<password> \
  'https://docs.name.com/_mock/api-spec-cdn/namecom.api/core/v1/domains/{domainName}:getAuthCode'

Responses

A successful response.

Bodyapplication/json
authCodestringrequired

AuthCode is the authorization code needed to transfer a domain to another registrar. If you are storing auth codes, be sure to store them in a secure manner.

Response
application/json
{
  "authCode": "string"
}

Get Pricing For Domain

Request

Retrieves the registration and renewal pricing for a given domain.

Security
BasicAuth
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/api-spec-cdn/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.

Security
BasicAuth
Path
domainNamestringrequired

DomainName is the domain to purchase Whois Privacy for.

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
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.

Default 1
curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/api-spec-cdn/namecom.api/core/v1/domains/{domainName}:purchasePrivacy' \
  -H 'Content-Type: application/json' \
  -H 'X-Idempotency-Key: 083910ef-04e4-4bd1-a0bf-3737fe005ca8' \
  -d '{
    "purchasePrice": 0.1,
    "years": 1
  }'

Responses

A successful response.

Headers
X-Idempotency-Keystring

If the initial request contained this header, echoes back with the initial value.

Example: "083910ef-04e4-4bd1-a0bf-3737fe005ca8"
X-Idempotent-Replaynumber

Indicates that the response is being replayed from an idempotent request. This header will only be returned if the API is responding with cached data. Caches are cleared after 12 hours.

Example: 1
Bodyapplication/json
domainobject(DomainResponsePayload)

The response format 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
}

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