Domain Transfers
Endpoints for managing incoming and outgoing domain transfers.
Show the auth-code
Retrieve the auth-code for a single domain for the authenticated team.
Some TLDs do not provide the auth-code to us but instead send it to the domain's registrant email address.
You can use the POST version of this endpoint to request the auth-code to be sent.
path Parameters
domainNameOrIdfull domain name or ID
Show the auth-code › Responses
Send the auth-code
Queue an auth-code delivery request for a single domain for the authenticated team.
Some TLDs do not provide the auth-code to us but instead send it to the domain's registrant email address.
To retrieve the auth-code directly, use the GET version of this endpoint.
path Parameters
domainNameOrIdfull domain name or ID
Send the auth-code › Responses
Initiate a push transfer
Initiate a push transfer for a single domain for the authenticated team.
A push transfer changes the registrar tag of the domain to transfer it to another registrar.
This is only available for certain TLDs (like .uk) that support tag-based transfers.
The transfer is processed asynchronously. Once a transfer is requested you are unable to update the request unless the transfer fails or the new regisrar rejects the request. If more than 5 days passes without any action the transfer expires and can be retried.
path Parameters
domainNameOrIdfull domain name or ID
Initiate a push transfer › Request Body
recipient^[a-zA-Z0-9-]{2,16}$ · requiredThe registrar tag of the receiving registrar. Must be 2-16 characters, alphanumeric and hyphens only.
Initiate a push transfer › Responses
DomainWithNotices
Retry a failed transfer
Retry a failed incoming transfer for a single domain for the authenticated team. No additional charge is created for a transfer retry. This endpoint is only available for failed transfers that require an auth-code.
path Parameters
domainNameOrIdfull domain name or ID
Retry a failed transfer › Request Body
auth_codeThe authorization code required to retry the transfer.
intended_useRequired when this historical transfer does not yet have its intended-use declaration.
Retry a failed transfer › Responses
The transfer retry was accepted. The returned domain and notices reflect the state after the retry was requested; the transfer itself may still be processing.
Decide whether to accept or reject an outgoing transfer
Submit an explicit decision for a pending outgoing transfer.
path Parameters
domainNameOrIdfull domain name or ID
Decide whether to accept or reject an outgoing transfer › Request Body
decisionAccept or reject the outgoing transfer.
accept Allow the domain to leave the current registrar account. |
reject Refuse the outgoing transfer request. |
Decide whether to accept or reject an outgoing transfer › Responses
DomainWithNotices
Move scheduled incoming transfer
Move a scheduled incoming transfer to a new future minute. The schedule can be moved until five minutes before execution.
path Parameters
domainNameOrIdfull domain name or ID
Move scheduled incoming transfer › Request Body
scheduled_transfer_atUse an RFC 3339 timestamp; if no timezone is provided, UTC is assumed. Seconds are discarded, and the resulting UTC minute must be at least 15 minutes and at most one year in the future.
auth_codeOptional replacement authorization code for the incoming transfer. Supply it only when the transfer uses an authorization code and that code has changed. When provided, it replaces the code that will be submitted when the scheduled transfer starts; when omitted, the current code is retained.
Move scheduled incoming transfer › Responses
DomainWithNotices