Skip to main content
WEBHOOK
domainTransferOutStatusChange
{
  "eventName": "domain.transfer_out.status_change",
  "domainName": "example.com",
  "status": "initiated",
  "registryClientId": "NAMECOM-123"
}

Authorizations

​
Authorization
string
header
required

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

​
X-NAMECOM-SIGNATURE
string
required

HMAC signature for the request payload. See HMAC signing documentation for example code and detailed explanation of signing.

Example:

"djasfgafgflgsdfgdsfkhfhjas,12334782,1123-3423-4dss4-354"

Body

application/json

The request sent to your server when a domain transfer out status changes.

Payload sent when a domain transfer OUT from name.com to another registrar has a status change (initiated, completed, or canceled). When status is "completed", the domain has been removed from name.com. In some edge cases (including near-expiration scenarios) the data may not be fully accurate.

​
eventName
enum<string>
required

The name of the subscription event.

Available options:
domain.transfer_out.status_change
​
domainName
string
required

The domain that has transferred out of name.com.

Example:

"example.com"

​
status
enum<string>
required

The status of the transfer out event. May be "initiated" (transfer out was started), "completed" (domain has been removed from the account), or "canceled" (transfer out was canceled before completion).

Available options:
initiated,
completed,
canceled
Example:

"completed"

​
registryClientId
string | null

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.

Example:

"NAMECOM-123"

Response

The subscribed server accepted the request.