Skip to main content
WEBHOOK
domainRegistryRejection
{
  "eventName": "domain.registry.rejection",
  "domainName": "example.com",
  "orderId": 123456,
  "orderItemId": 987654,
  "occurredAt": "2023-04-01T12:00:00Z",
  "reason": "Registry policy violation"
}

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

Payload sent when a domain create request fails after asynchronous registry processing. Most domain creates succeed immediately; this event covers the case where the registry initially accepts processing but later rejects or fails the registration.

​
eventName
enum<string>
required

The name of the subscription event.

Available options:
domain.registry.rejection
​
domainName
string
required

The domain name that failed to register.

Example:

"example.com"

​
orderId
integer<int32>
required

The unique identifier of the order for the failed domain create. Use the List Orders endpoint to retrieve order details.

Example:

123456

​
orderItemId
integer<int32>
required

The unique identifier of the order line item for the failed domain create. Use the List Orders endpoint to retrieve order item details.

Example:

987654

​
occurredAt
string<date-time>
required

When the asynchronous registration failure was recorded.

Example:

"2023-04-01T12:00:00Z"

​
reason
string

Optional human-readable or registry-provided detail about the failure, when available.

Example:

"Registry policy violation"

Response

The subscribed server accepted the request.