Create Transfer

curl --request POST \
  --url https://api.dev.name.com/core/v1/transfers \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "authCode": "ABC123",
  "domainName": "example.com",
  "privacyEnabled": true,
  "purchasePrice": 12.99
}
'

{
  "order": 12345,
  "totalPaid": 12.99,
  "transfer": {
    "domainName": "example.com",
    "status": "pending_transfer",
    "email": "[email protected]"
  },
  "warnings": {
    "message": "Domain has registry statuses that may prevent a successful transfer. Please ensure the domain is unlocked and eligible at the losing registrar.",
    "statuses": [
      "clientTransferProhibited",
      "clientUpdateProhibited"
    ]
  }
}

POST

core

transfers

Create Transfer

curl --request POST \
  --url https://api.dev.name.com/core/v1/transfers \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "authCode": "ABC123",
  "domainName": "example.com",
  "privacyEnabled": true,
  "purchasePrice": 12.99
}
'

{
  "order": 12345,
  "totalPaid": 12.99,
  "transfer": {
    "domainName": "example.com",
    "status": "pending_transfer",
    "email": "[email protected]"
  },
  "warnings": {
    "message": "Domain has registry statuses that may prevent a successful transfer. Please ensure the domain is unlocked and eligible at the losing registrar.",
    "statuses": [
      "clientTransferProhibited",
      "clientUpdateProhibited"
    ]
  }
}

Authorizations

Authorization

string

header

required

Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic <base64(username:token)>' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com.

Body

application/json

CreateTransferRequest passes the required transfer info to the CreateTransfer function.

authCode

string

required

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

Minimum string length: 1

Example:

"ABC123"

domainName

string

required

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

Minimum string length: 1

Example:

"example.com"

privacyEnabled

boolean

PrivacyEnabled is a flag on whether to purchase Whois Privacy with the transfer. If this flag is omitted from the request, the system will check the account's Whois Privacy auto-add settings. If auto-add is enabled in your account settings, Whois Privacy will be added by default, provided the TLD supports it.

Example:

true

purchasePrice

number<double>

PurchasePrice is the amount to pay for the transfer of the domain. If privacyEnabled 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

Response

A successful response.

CreateTransferResponse returns the newly created transfer resource as well as the order information.

order

integer<int32>

required

Order is an identifier for this purchase.

Example:

12345

totalPaid

number<double>

required

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

Example:

12.99

transfer

object

required

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

Show child attributes

transfer.domainName

string

required

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

Example:

"example.com"

transfer.status

enum<string>

required

The updated status of the domain transfer. The transfer status will be one of the following values:

canceled: The transfer has been canceled by the user.
canceled_pending_refund: The transfer has been canceled by the user, and a refund for the price is being processed.
completed: The transfer has completed.
failed: The transfer has failed, and will not be retried.
pending: The transfer has been requested, and is pending.
pending_insert: The transfer has completed and the domain will soon be inserted into the account.
pending_new_auth_code: A new authcode is required to complete the transfer.
pending_transfer: The transfer has been requested, and is pending.
pending_unlock: The domain to be transferred is currently in a locked state at the losing registrar, and will begin processing once the lock has been removed.
rejected: The transfer has been rejected at the losing registrar and will not be retried.
submitting_transfer: The transfer has been initiated and will soon be submitted to the registry.

Available options:

canceled,

canceled_pending_refund,

completed,

failed,

pending,

pending_insert,

pending_new_auth_code,

pending_transfer,

pending_unlock,

rejected,

submitting_transfer

Example:

"pending_transfer"

transfer.email

string<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:

"[email protected]"

warnings

object

Optional transfer warnings surfaced by the API when non-blocking registry statuses are detected.

Show child attributes

warnings.message

string

Brief guidance for resolving potential transfer issues.

Example:

"Domain has registry statuses that may prevent a successful transfer. Please ensure the domain is unlocked and eligible at the losing registrar."

warnings.statuses

string[]

Registry status values that triggered the warning.

Example:

[
  "clientTransferProhibited",
  "clientUpdateProhibited"
]

List Transfers Get Transfer

⌘I

API Home

Guides & Flows

Core API Overview

name.com Core API Reference

Resources

Create Transfer

Authorizations

Body

Response