Get Transfer

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

namecom.api.json

namecom.api.yaml

Overview

Account Services

accountservices@name.com

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

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

List Transfers

Request

Returns all domain transfer requests for the account, including in-progress and recent transfers.

Query

perPageinteger(int32)

Per Page is the number of records to return per request. Per Page defaults to 1,000.

pageinteger(int32)

Page is which page to return.

curl -i -X GET \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/transfers?page=0&perPage=0'

Responses

A successful response.

Headers

Linkstring

String of comma delimited links for pagination of the response

Example: "<https:\\\\api.dev.name.com?page=3; rel=\"next\">,<https:\\\\api.dev.name.com?page=1; rel=\"prev\">,<https:\\\\api.dev.name.com?page=10; rel=\"last\">"

Bodyapplication/json

lastPageinteger(int32)

LastPage is the identifier for the final page of results. It is only populated if there is another page of results after the current page.

nextPageinteger(int32)

NextPage is the identifier for the next page of results. It is only populated if there is another page of results after the current page.

totalCountinteger(int32)required

TotalCount is total number of results.

frominteger(int32)required

From specifies starting record number on current page.

tointeger(int32)required

To specifies ending record number on current page.

transfersArray of objects(Transfer)required

Transfers is a list of pending transfers

transfers[].domainNamestringrequired

DomainName is the domain to be transfered to Name.com.

Example: "example.com"

transfers[].emailstring(email)

Email is the email address that the approval email was sent to. Not every TLD requries an approval email. This is usually pulled from Whois.

Example: "admin@example.com"

transfers[].statusstringrequired

The current status of the transfer. Details about statuses can be found in the following Knowledge Base article: https://www.name.com/support/articles/115012519688-transfer-status-faq.

Example: "pending_transfer"

Response

application/json

{
  "lastPage": 0,
  "nextPage": 0,
  "totalCount": 0,
  "from": 0,
  "to": 0,
  "transfers": [
    { … }
  ]
}

Create Transfer

Request

Initiates a domain transfer into your Name.com account from another registrar. You must provide the domain name and its valid transfer authorization code (EPP code). The domain must not be locked or under any transfer restrictions (e.g. clientTransferProhibited). If successful, the transfer is submitted and tracked through the ICANN transfer process. Once a transfer has been created, you can track its progress via the GetTransfer endpoint.

Bodyapplication/jsonrequired

CreateTransferRequest passes the required transfer info to the CreateTransfer function.

authCodestringrequired

AuthCode is the authorization code for the transfer. Not all TLDs require authorization codes, but most do.

Example: "ABC123"

domainNamestringrequired

DomainName is the domain you want to transfer to Name.com.

Example: "example.com"

privacyEnabledboolean

PrivacyEnabled is a flag on whether to purchase Whois Privacy with the transfer.

Example: true

purchasePricenumber(double)

PurchasePrice is the amount to pay for the transfer of the domain. If privacy_enabled is set, the regular price for Whois Privacy will be added automatically. If VAT tax applies, it will also be added automatically. PurchasePrice is required if the domain to transfer is a premium domain.

Example: 12.99

curl -i -X POST \
  -u <username>:<password> \
  https://docs.name.com/_mock/coreapi/namecom.api/core/v1/transfers \
  -H 'Content-Type: application/json' \
  -d '{
    "authCode": "ABC123",
    "domainName": "example.com",
    "privacyEnabled": true,
    "purchasePrice": 12.99
  }'

Responses

A successful response.

Bodyapplication/json

orderinteger(int32)required

Order is an identifier for this purchase.

Example: 12345

totalPaidnumber(double)required

TotalPaid is the total amount paid, including VAT and Whois Privacy.

Example: 12.99

transferobject(Transfer)required

Transfer contains all relevant data for a domain transfer to Name.com.

transfer.domainNamestringrequired

DomainName is the domain to be transfered to Name.com.

Example: "example.com"

transfer.emailstring(email)

Email is the email address that the approval email was sent to. Not every TLD requries an approval email. This is usually pulled from Whois.

Example: "admin@example.com"

transfer.statusstringrequired

The current status of the transfer. Details about statuses can be found in the following Knowledge Base article: https://www.name.com/support/articles/115012519688-transfer-status-faq.

Example: "pending_transfer"

Response

application/json

{
  "order": 12345,
  "totalPaid": 12.99,
  "transfer": {
    "domainName": "example.com",
    "email": "admin@example.com",
    "status": "pending_transfer"
  }
}

Get Transfer

Request

Retrieves details of a specific domain transfer request.

Path

domainNamestringrequired

DomainName is the domain you want to get the transfer information for.

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

Responses

A successful response.

Bodyapplication/json

domainNamestringrequired

DomainName is the domain to be transfered to Name.com.

Example: "example.com"

emailstring(email)

Email is the email address that the approval email was sent to. Not every TLD requries an approval email. This is usually pulled from Whois.

Example: "admin@example.com"

statusstringrequired

The current status of the transfer. Details about statuses can be found in the following Knowledge Base article: https://www.name.com/support/articles/115012519688-transfer-status-faq.

Example: "pending_transfer"

Response

application/json

{
  "domainName": "example.com",
  "email": "admin@example.com",
  "status": "pending_transfer"
}

Cancel Transfer

Request

Cancels a pending transfer request. This can be used if the transfer was initiated in error or if the authorization code provided was incorrect. The price of the transfer will refund the amount to account credit.

Path

domainNamestringrequired

DomainName is the domain to cancel the transfer for.

curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/transfers/{domainName}:cancel'

Responses

A successful response.

Bodyapplication/json

domainNamestringrequired

DomainName is the domain to be transfered to Name.com.

Example: "example.com"

emailstring(email)

Email is the email address that the approval email was sent to. Not every TLD requries an approval email. This is usually pulled from Whois.

Example: "admin@example.com"

statusstringrequired

The current status of the transfer. Details about statuses can be found in the following Knowledge Base article: https://www.name.com/support/articles/115012519688-transfer-status-faq.

Example: "pending_transfer"

Response

application/json

{
  "domainName": "example.com",
  "email": "admin@example.com",
  "status": "pending_transfer"
}

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

Name.com Core API (1.0.1)

Hello

Account Info

Accounts

Domains

DNS

DNSSECs

Email Forwardings

URL Forwardings

Vanity Nameservers

Transfers

List Transfers

Request

Responses

Was this helpful?

Create Transfer

Request

Responses

Was this helpful?

Get Transfer

Request

Responses

Was this helpful?

Cancel Transfer

Request

Responses

Was this helpful?

Orders

Webhook Notifications