# Create Transfer

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.

Endpoint: POST /core/v1/transfers
Version: 1.3.1
Security: BasicAuth

## Request fields (application/json):

  - `authCode` (string, required)
    AuthCode is the authorization code for the transfer. Not all TLDs require authorization codes, but most do.
    Example: "ABC123"

  - `domainName` (string, required)
    DomainName is the domain you want to transfer to name.com.
    Example: "example.com"

  - `privacyEnabled` (boolean)
    PrivacyEnabled is a flag on whether to purchase Whois Privacy with the transfer.
    Example: true

  - `purchasePrice` (number)
    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

## Response 200 fields (application/json):

  - `order` (integer, required)
    Order is an identifier for this purchase.
    Example: 12345

  - `totalPaid` (number, 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.

  - `transfer.domainName` (string, required)
    DomainName is the domain to be transfered to name.com.
    Example: "example.com"

  - `transfer.email` (string)
    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.status` (string, required)
    The current status of the transfer. Details about statuses can be found in the following Knowledge Base article: .
    Example: "pending_transfer"

## Response 400 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Bad Request"

  - `details` (string,null)
    Additional context or information about the error
    Example: "'domainName' cannot be null"

## Response 402 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error.
    Example: "Internal Server Error"

  - `details` (string,null)
    Additional context or information about the error.
    Example: "Something went wrong."

## Response 409 fields (application/json):

  - `message` (string, required)
    A human-readable error message describing the conflict
    Example: "Object already exists."

  - `details` (string,null)
    Additional context or information about the error
    Example: "Cannot create multiple objects under same key."

## Response 415 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "The 'Content-Type' header must be 'application/json' for this request."

## Response 429 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Bad Request"

  - `details` (string,null)
    Additional context or information about the error
    Example: "'domainName' cannot be null"

## Response 500 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error.
    Example: "Internal Server Error"

  - `details` (string,null)
    Additional context or information about the error.
    Example: "Something went wrong."