Domain Transfer Out Status Change
Sent when you have subscribed to the event on your account, and a domain transfer OUT from name.com to another registrar has completed. This webhook fires when a domain is removed from name.com, but in some edge cases (including near-expiration scenarios) the data may not be fully accurate. For example, registry sync delays or edge timing around expiration can cause temporary discrepancies between the payload and the registry’s eventual state.
Authorizations
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.
Headers
HMAC signature for the request payload. See HMAC signing documentation for example code and detailed explanation of signing.
"djasfgafgflgsdfgdsfkhfhjas,12334782,1123-3423-4dss4-354"
Body
The request sent to your server when a domain transfer out completes.
Payload sent when a domain transfer OUT from name.com to another registrar has completed. This webhook fires when a domain is removed from name.com, but in some edge cases (including near-expiration scenarios) the data may not be fully accurate.
The name of the subscription event.
domain.transfer_out.status_change The domain that has transferred out of name.com.
"example.com"
The status of the transfer out event. Currently, this webhook is emitted when the transfer out has completed and the domain has been removed from the account.
completed "completed"
The registry client ID associated with the domain at the time of transfer out, when available. This can help identify the gaining registrar at the registry.
"NAMECOM-123"
Response
The subscribed server accepted the request.