Transfer Domains
View as MarkdownAuthorization
bearerAuth AuthorizationBearer <token>
Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
domain*string
Domain to transfer in
Header Parameters
X-Shopper-Id?string
Shopper ID which owns the domain. NOTE: This is only required if you are a Reseller managing a domain purchased outside the scope of your reseller account.
Details for domain transfer purchase
Response Body
curl -X POST "https://example.com/v1/domains/string/transfer" \ -H "Content-Type: application/json" \ -d '{ "authCode": "string", "consent": { "agreedAt": "string", "agreedBy": "string", "agreementKeys": [ "string" ] } }'{ "currency": "USD", "itemCount": 0, "orderId": 0, "total": 0}Agent & Automation Notes
Scopes
domains.domain:read, domains.domain:create, domains.domain:delete, domains.domain:update, domains.contact:update, domains.dns:update, domains.transfer:executeRate limit60 req/min per credential
On failureGET operations are safe to retry. PUT/PATCH DNS are idempotent by shape. POST purchase is NOT idempotent — verify state before retrying.
Related
Last updated on
How is this guide?