> ## Documentation Index > Fetch the complete documentation index at: https://docs.name.com/llms.txt > Use this file to discover all available pages before exploring further. # Create External Transfer In > 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](/api/v1/reference/transfers/get-transfer) endpoint. **Transfer pricing:** Omit `purchasePrice` for standard (non-premium) transfers. For premium transfers, pass `transferPrice` from [Get Pricing For Domain](/api/v1/reference/domains/get-pricing-for-domain) as `purchasePrice`. If sent, it must match Get Pricing `transferPrice` exactly or the request will fail. Premium transfers without `purchasePrice` will fail. See the [Domain pricing guide](/guides/domain-pricing) for how [Get Pricing](/api/v1/reference/domains/get-pricing-for-domain) `transferPrice` relates to the `years` query parameter. **Optional `contacts`** - Omit for account defaults; provided roles override; omitted roles use defaults. ## OpenAPI ````yaml post /core/v1/transfers openapi: 3.1.0 info: contact: email: reseller@name.com name: Reseller Account Services description: >- 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. title: name.com Core API version: 1.36.0 termsOfService: https://www.name.com/policies/api-access-agreement servers: - description: Testing url: https://api.dev.name.com security: - BasicAuth: [] tags: - name: Hello description: >- 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. - name: Account Info description: >- 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. - name: Accounts description: >- 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. - name: Domains description: >- Use Domains endpoints to search for domain availability, register new domains, and manage existing domains. - name: Contact Verification description: >- Use Contact Verification endpoints to query a reseller’s unverified domains/emails and to programmatically mark an end user’s email as verified if the reseller has already completed the verification process. These endpoints help resellers meet ICANN requirements by ensuring end users confirm they can receive email at their listed address. - name: DNS description: >- 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. - name: DNSSECs description: >- Use DNSSEC endpoints to configure DNS Security Extensions for your domains. These endpoints allow you to add, retrieve, or remove DNSSEC records. - name: Email Forwardings description: >- Use Email Forwardings endpoints to set up and manage email forwarding addresses on your domains. - name: URL Forwardings description: >- Use URL Forwardings endpoints to control URL redirection settings for your domains. - name: Vanity Nameservers description: >- Use Vanity Nameservers endpoints to configure custom nameserver hostnames (glue records) for your domains. - name: Transfers description: >- Use Transfers endpoints to move domains into your name.com account. Start by creating a transfer request for inbound transfers from **external** registrars, then monitor and manage the status of pending transfers. Use **internal transfer in** to pull a domain from another name.com account into your reseller account (enterprise allowlist; requires auth code from the losing account’s dashboard). You can cancel an incoming transfer if needed, or cancel an outbound transfer (domain leaving name.com) via the external transfer-out cancel endpoint. Use the **transfer eligibility** endpoint to check whether a domain is currently at name.com before initiating a transfer, so you can route to the correct flow (external vs internal transfer). - name: Orders description: Use Orders endpoints to review and track purchases made via the API. - name: Refunds description: > Use the Refunds endpoint to delete eligible domains and advanced security products during the Add Grace Period (AGP) and automatically issue refunds for the associated order items. You can use the List Orders endpoint to retrieve order IDs, then pass those IDs into the Refunds endpoint to process eligible deletions and refunds. This endpoint enforces AGP delete limits and supports only domain registrations and advanced security add-ons. Refunds are issued to the original payment method on file. If the original payment method is unavailable, the refund will be credited to the account balance. - name: Webhook Notifications description: > 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. Outbound webhook POSTs include an `X-NAMECOM-SIGNATURE` header. HMAC uses one API v4 token per account, chosen deterministically when multiple tokens exist (see HMAC Signature Verification in the developer docs). The signing input format is unchanged. - name: Domain Info description: >- 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. - name: TLD Pricing description: >- Use TLD Pricing endpoints to retrieve general pricing information for your account. - name: Premium Domains description: APIs for working with Premium Domains. paths: /core/v1/transfers: post: tags: - Transfers summary: Create Transfer description: >- 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](/api/v1/reference/transfers/get-transfer) endpoint. **Transfer pricing:** Omit `purchasePrice` for standard (non-premium) transfers. For premium transfers, pass `transferPrice` from [Get Pricing For Domain](/api/v1/reference/domains/get-pricing-for-domain) as `purchasePrice`. If sent, it must match Get Pricing `transferPrice` exactly or the request will fail. Premium transfers without `purchasePrice` will fail. See the [Domain pricing guide](/guides/domain-pricing) for how [Get Pricing](/api/v1/reference/domains/get-pricing-for-domain) `transferPrice` relates to the `years` query parameter. **Optional `contacts`** - Omit for account defaults; provided roles override; omitted roles use defaults. operationId: CreateTransfer requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateTransferRequest' description: >- CreateTransferRequest passes the required transfer info to the CreateTransfer function. required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/CreateTransferResponse' description: A successful response. '400': content: application/json: schema: $ref: '#/components/schemas/InvalidArgument400' examples: premiumPriceRequired: summary: Premium transfer requires purchasePrice value: message: >- PurchasePrice is required if the domain to transfer is a premium domain priceMismatch: summary: Transfer price does not match value: message: Invalid Price description: >- There was an invalid or missing argument in the request. The response messages will indicate which fields are invalid. '401': description: Unauthorized. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Unauthorized '402': description: >- The account placing the order has insufficient account credit to process this transfer order. content: application/json: schema: $ref: '#/components/schemas/GenericError500' example: message: Insufficient Funds '403': description: Forbidden - you do not have permission to perform this action. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Permission denied details: type: - string - 'null' description: Additional context or information about the error example: Failed authentication '405': description: Method not allowed. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Method Not Allowed '409': description: >- The status of the domain indicates that we are unable to process a transfer for it. content: application/json: schema: $ref: '#/components/schemas/GenericConflict409' '415': description: >- All POST, PUT, PATCH requests for this API must include the `Content-Type: application/json` header in the requests. content: application/json: schema: $ref: '#/components/schemas/UnsupportedMedia415' '422': description: Pricing information unavailable. content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntity422' examples: pricingUnavailable: summary: Pricing unavailable for domain value: message: Domain pricing unavailable details: >- The pricing information required to process this request is temporarily unavailable. This is an internal system error. Please try again in a few minutes or contact support if the issue persists. '429': description: Rate limit has been exceeded. content: application/json: schema: type: object required: - message - details properties: message: type: string description: >- ### Too Many Requests You have exceeded the rate limit. **Headers returned:** * 'X-RateLimit-Reset': An integer (UTC epoch) indicating when you can retry. example: Rate Limit Exceeded headers: x-ratelimit-reset: description: >- Unix timestamp for the time at which the current rate limit will reset. schema: type: number example: 1747668270 '500': description: Internal server error. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: Internal Server Error details: type: - string - 'null' description: Additional context or information about the error. example: Something went wrong. '502': description: Bad Gateway content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: >- The server received an invalid response from the upstream server. '503': description: >- Service Unavailable — returned during scheduled maintenance when the API is offline. See https://status.name.com for updates. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: Service Unavailable details: type: - string - 'null' description: Additional context or information about the error. example: >- The API is offline for scheduled maintenance. See https://status.name.com for updates. '504': description: Unable to retrieve domain status due to blocked-hostname. content: application/json: schema: $ref: '#/components/schemas/GatewayTimeout504' components: schemas: CreateTransferRequest: description: >- CreateTransferRequest passes the required transfer info to the CreateTransfer function. See the [Domain pricing guide](/guides/domain-pricing) for how `purchasePrice` relates to [Get Pricing](/api/v1/reference/domains/get-pricing-for-domain) `transferPrice`. properties: authCode: description: >- AuthCode is the authorization code for the transfer. Not all TLDs require authorization codes, but most do. type: string example: ABC123 minLength: 1 domainName: description: DomainName is the domain you want to transfer to name.com. type: string example: example.com minLength: 1 privacyEnabled: description: >- Whether to include Whois Privacy with the transfer. Whois Privacy is free. If omitted, the account default from account settings is used. Privacy is only added when the TLD supports it. type: boolean example: true purchasePrice: description: >- PurchasePrice is the USD inbound transfer fee, before VAT. VAT is applied when applicable and must not be included here. If sent, must match Get Pricing `transferPrice` exactly or the request will fail.. **Omit** for standard (non-premium) transfers. **Required** for premium transfers — use `transferPrice` from [Get Pricing](/api/v1/reference/domains/get-pricing-for-domain). format: double type: number example: 12.99 contacts: description: >- WHOIS contacts to apply when the domain lands in the account. If omitted, the gaining account's default contacts are applied. If provided, include any roles to override; omitted roles use the gaining account's default contacts. Each supplied role must include complete contact fields. A registrar contact-change transfer lock may apply according to the gaining account's settings. allOf: - $ref: '#/components/schemas/ContactsRequest' type: object required: - domainName - authCode CreateTransferResponse: description: >- CreateTransferResponse returns the newly created transfer resource as well as the order information. properties: order: description: Order is an identifier for this purchase. format: int32 type: integer example: 12345 totalPaid: description: >- TotalPaid is the total amount paid, including VAT when applicable. Whois Privacy is free and is not included in this amount. format: double type: number example: 12.99 transfer: $ref: '#/components/schemas/Transfer' warnings: description: >- Optional transfer warnings surfaced by the API when non-blocking registry statuses are detected. type: object properties: message: type: string description: 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. statuses: type: array description: Registry status values that triggered the warning. items: type: string example: - clientTransferProhibited - clientUpdateProhibited type: object required: - order - totalPaid - transfer InvalidArgument400: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: Bad Request details: type: - string - 'null' description: Additional context or information about the error example: '''domainName'' cannot be null' GenericError500: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error. example: Internal Server Error details: type: - string - 'null' description: Additional context or information about the error. example: Something went wrong. GenericConflict409: type: object description: A conflict error response. required: - message properties: message: type: string description: A human-readable error message describing the conflict example: Object already exists. details: type: - string - 'null' description: Additional context or information about the error example: Cannot create multiple objects under same key. UnsupportedMedia415: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: >- The 'Content-Type' header must be 'application/json' for this request. UnprocessableEntity422: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: Unprocessable Entity details: type: string description: Additional context or information about the pricing error example: >- The pricing information required to process this request is temporarily unavailable. This is an internal system error. Please try again in a few minutes or contact support if the issue persists. GatewayTimeout504: type: object properties: message: type: string description: A human-readable message providing more details about the error example: Unable to retrieve domain status ContactsRequest: description: >- Contacts stores the contact information for the roles related to domains. This schema is used for requests. properties: admin: $ref: '#/components/schemas/ContactRequest' billing: $ref: '#/components/schemas/ContactRequest' registrant: $ref: '#/components/schemas/RegistrantContactRequest' tech: $ref: '#/components/schemas/ContactRequest' type: object Transfer: description: Transfer contains all relevant data for a domain transfer to name.com. type: object properties: domainName: description: DomainName is the domain to be transfered to name.com. type: string example: example.com email: description: >- 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. type: string format: email example: admin@example.com status: $ref: '#/components/schemas/TransferStatus' required: - domainName - status ContactRequest: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for creating and updating contacts (POST/PUT requests) and includes all validation requirements. All fields listed in the `required` array must be provided and cannot be null or empty. allOf: - $ref: '#/components/schemas/Contact' - type: object properties: firstName: description: First name of the contact. type: string example: John minLength: 1 lastName: description: Last name of the contact. type: string example: Doe minLength: 1 address1: description: The first line of the contact's address. type: string example: 123 Main Street minLength: 1 city: description: City of the contact's address. type: string example: New York minLength: 1 state: description: State or Province of the contact's address. type: string example: NY minLength: 1 zip: description: >- ZIP or Postal Code of the contact's address. This field is required and must be a non-empty string. type: string example: '10001' minLength: 1 country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: string example: US pattern: ^[A-Z]{2}$ email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: string format: email example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: string pattern: ^\+[1-9]\d{7,14}$ example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' pattern: ^\+[1-9]\d{7,14}$ example: '+15557654321' required: - firstName - lastName - address1 - city - state - zip - country - email - phone RegistrantContactRequest: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for creating and updating contacts (POST/PUT requests) and includes all validation requirements. All fields listed in the `required` array must be provided and cannot be null or empty. allOf: - $ref: '#/components/schemas/RegistrantContact' - type: object properties: firstName: description: First name of the contact. type: string example: John minLength: 1 lastName: description: Last name of the contact. type: string example: Doe minLength: 1 address1: description: The first line of the contact's address. type: string example: 123 Main Street minLength: 1 city: description: City of the contact's address. type: string example: New York minLength: 1 state: description: State or Province of the contact's address. type: string example: NY minLength: 1 zip: description: >- ZIP or Postal Code of the contact's address. This field is required and must be a non-empty string. type: string example: '10001' minLength: 1 country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: string example: US pattern: ^[A-Z]{2}$ email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: string format: email example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: string pattern: ^\+[1-9]\d{7,14}$ example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' pattern: ^\+[1-9]\d{7,14}$ example: '+15557654321' required: - firstName - lastName - address1 - city - state - zip - country - email - phone TransferStatus: type: string description: > Terminal (finished; will not change): - **completed**: Completed. - **failed**: Failed. - **canceled**: Canceled by the user. - **canceled_pending_refund**: Canceled; refund processing. Non-terminal (in progress; may change): - **pending**: Requested. - **submitting_transfer**: Being submitted to the registry. - **pending_new_auth_code**: New auth code required. - **pending_unlock**: Waiting for losing registrar unlock. - **pending_registry_unlock**: Waiting for registry unlock. - **pending_transfer**: Pending at the registry. - **pending_insert**: Transfer complete; domain will be added to the account. - **rejected**: Rejected at the losing registrar. enum: - canceled - canceled_pending_refund - completed - failed - pending - pending_insert - pending_new_auth_code - pending_registry_unlock - pending_transfer - pending_unlock - rejected - submitting_transfer example: pending_transfer Contact: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for API responses and may contain null values for legacy data. For creating or updating contacts, use ContactRequest which enforces all validation requirements. type: object properties: firstName: description: First name of the contact. type: - string - 'null' example: John lastName: description: Last name of the contact. type: - string - 'null' example: Doe companyName: description: >- Company name of the contact. Leave blank if the contact is an individual, as some registries may assume it is a corporate entity otherwise. type: - string - 'null' example: Example Inc. address1: description: The first line of the contact's address. type: - string - 'null' example: 123 Main Street address2: description: The second line of the contact's address (optional). type: - string - 'null' example: Suite 400 city: description: City of the contact's address. type: - string - 'null' example: New York state: description: State or Province of the contact's address. type: - string - 'null' example: NY zip: description: ZIP or Postal Code of the contact's address. type: - string - 'null' example: '10001' country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: - string - 'null' example: US email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: - string - 'null' example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15557654321' isVerified: description: >- Indicates if the contact has been verified as per ICANN requirements. If the value is `false` it indicates that the contact has not completed the required verification process. This property is read-only and will be included in responses but should not be included in requests. type: boolean example: true readOnly: true verificationId: description: >- When the contact is unverified, this is the ID of the pending verification record. Use this ID with the resend verification email and verify contact endpoints. Omitted or null when the contact is verified. type: - integer - 'null' format: int64 example: 12345 readOnly: true RegistrantContact: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for API responses and may contain null values for legacy data. For creating or updating contacts, use RegistrantContactRequest which enforces all validation requirements. type: object properties: firstName: description: First name of the contact. type: - string - 'null' example: John lastName: description: Last name of the contact. type: - string - 'null' example: Doe companyName: description: >- Company name of the contact. Leave blank if the contact is an individual. Please be advised that ICANN policy links the "Company Name" field (Organization) in your domain's contact details to its legal ownership. If this field contains information, the listed organization is considered the legal "Registered Name Holder" (domain owner). type: - string - 'null' example: Example Inc. address1: description: The first line of the contact's address. type: - string - 'null' example: 123 Main Street address2: description: The second line of the contact's address (optional). type: - string - 'null' example: Suite 400 city: description: City of the contact's address. type: - string - 'null' example: New York state: description: State or Province of the contact's address. type: - string - 'null' example: NY zip: description: ZIP or Postal Code of the contact's address. type: - string - 'null' example: '10001' country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: - string - 'null' example: US email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: - string - 'null' example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15557654321' isVerified: description: >- Indicates if the contact has been verified as per ICANN requirements. If the value is `false` it indicates that the contact has not completed the required verification process. This property is read-only and will be included in responses but should not be included in requests. type: boolean example: true readOnly: true verificationId: description: >- When the contact is unverified, this is the ID of the pending verification record. Use this ID with the resend verification email and verify contact endpoints. Omitted or null when the contact is verified. type: - integer - 'null' format: int64 example: 12345 readOnly: true securitySchemes: BasicAuth: scheme: basic type: http description: >- Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic ' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.