Skip to main content
POST
domainTransferStatusChange
{}

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.

Payload sent when a domain transfer IN to name.com is processing. This schema represents transfer-in events where name.com is the gaining registrar.

​
eventName
enum<string>
required

The name of the subscription event

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

The domain that the transfer status has changed for

Example:

"example.com"

​
status
enum<string>
required

The updated status of the domain transfer. The transfer status will be one of the following values:

  • canceled: The transfer has been canceled by the user.
  • canceled_pending_refund: The transfer has been canceled by the user, and a refund for the price is being processed.
  • completed: The transfer has completed.
  • failed: The transfer has failed, and will not be retried.
  • pending: The transfer has been requested, and is pending.
  • pending_insert: The transfer has completed and the domain will soon be inserted into the account.
  • pending_new_auth_code: A new authcode is required to complete the transfer.
  • pending_transfer: The transfer has been requested, and is pending.
  • pending_unlock: The domain to be transferred is currently in a locked state at the losing registrar, and will begin processing once the lock has been removed.
  • rejected: The transfer has been rejected at the losing registrar and will not be retried.
  • submitting_transfer: The transfer has been initiated and will soon be submitted to the registry.
Available options:
canceled,
canceled_pending_refund,
completed,
failed,
pending,
pending_insert,
pending_new_auth_code,
pending_transfer,
pending_unlock,
rejected,
submitting_transfer

Response

The subscribed server accepted the request.