Pulls a domain from another name.com account into your reseller (gaining) account using a valid authorization code. This is an internal name.com-to-name.com move; it is separate from Create Transfer, which brings domains in from external registrars. This API is only available to approved reseller accounts. Contact name.com support to request access. The following TLDs carry trade-costs and thus are ineligible for internal transfer in: ag, am, at, be, ca, ch, cl, cn, co.in, com.br, com.tw, cz, dk, ec, es, eu, in, it, jp, li, nl, no, pl, ru, se.
The party that holds the domain today must use the name.com dashboard on the losing account to unlock the domain (remove registrar transfer lock) and to copy the authorization code to provide to your integration. This endpoint does not unlock the domain or retrieve the auth code for the losing account.
Call this endpoint with domainName, authCode, and optional contacts using the gaining reseller’s API credentials.
If contacts is omitted, the gaining account’s default contacts are applied. If contacts is provided, the same completeness rules apply as for Set Contacts. The 60-day contact-change transfer lock is enforced based on the gaining account’s settings, consistent with Set Contacts.
Restricted to approved enterprise resellers; other callers receive 403 Forbidden.
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.
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.
Request body for transferring a domain from another name.com account into the authenticated reseller (gaining) account.
Fully qualified domain name to transfer in. The domain must be registered in another name.com account (the losing account).
1"example.com"
WHOIS contacts to apply after the transfer. If omitted, the gaining account's default contacts are applied. If provided, include all roles with complete fields (same rules as Set Contacts). A registrar contact-change transfer lock may apply according to the gaining account's settings, consistent with the Set Contacts endpoint.
The domain was accepted into the gaining account. The response body matches the domain resource representation used elsewhere in the API (same shape as Get Domain / Set Contacts).
The response format for a domain.
The punycode-encoded value of the domain name.
"example.com"
The date and time when the domain was created at the registry.
"2023-01-15T14:30:00Z"
The date and time when the domain will expire.
"2025-01-15T14:30:00Z"
Indicates whether the domain is set to renew automatically before expiration.
true
Indicates if the domain is transfer locked, preventing transfers to another registrar.
true
Indicates if Whois Privacy is enabled for this domain.
true
Contacts stores the contact information for the roles related to domains.
The list of nameservers assigned to this domain. If unspecified, it defaults to the account's default nameservers.
["ns1.example.com", "ns2.example.com"]List of all registry locking statuses currently applied to the domain. Use this to see which locks are active (e.g. clientTransferProhibited, clientHold). Empty when the domain has no locks applied.
["clientTransferProhibited", "clientHold"]The cost to renew the domain. This may be required for the RenewDomain operation.
12.99