Domain Notifications
View as MarkdownManage notification opt-in preferences, retrieve notification schemas, and acknowledge domain lifecycle notifications.
Authorization
bearerAuth Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
The Customer identifier. Note: For API Resellers, performing actions on behalf of your customers, you need to specify the Subaccount customer identifier you're operating on behalf of.
Header Parameters
A client provided identifier for tracking this request.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v2/customers/string/domains/notifications"{ "notificationId": "", "type": "AUTH_CODE_REGENERATE", "resource": "", "resourceType": "CONTACT", "status": "AWAITING", "addedAt": "", "requestId": "string", "metadata": ""}Authorization
bearerAuth Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
The Customer identifier. Note: For API Resellers, performing actions on behalf of your customers, you need to specify the Subaccount customer identifier you're operating on behalf of.
Header Parameters
A client provided identifier for tracking this request.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v2/customers/string/domains/notifications/optIn"[ { "notificationId": "", "type": "AUTH_CODE_REGENERATE", "resource": "", "resourceType": "CONTACT", "status": "AWAITING", "addedAt": "", "requestId": "string", "metadata": "" }]Authorization
bearerAuth Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
The Customer identifier. Note: For API Resellers, performing actions on behalf of your customers, you need to specify the Subaccount customer identifier you're operating on behalf of.
Query Parameters
The notification types that should be opted in
Header Parameters
A client provided identifier for tracking this request.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PUT "https://example.com/v2/customers/string/domains/notifications/optIn?types=AUTH_CODE_REGENERATE"Authorization
bearerAuth Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
The Customer identifier. Note: For API Resellers, performing actions on behalf of your customers, you need to specify the Subaccount customer identifier you're operating on behalf of.
The notification type whose schema should be retrieved
Value in
- "AUTH_CODE_REGENERATE"
- "AUTO_RENEWAL"
- "CHANGE_OF_REGISTRANT_DELETE"
- "DOMAIN_DELETE"
- "DOMAIN_UPDATE"
- "DOMAIN_UPDATE_NAME_SERVERS"
- "PRIVACY_FORWARDING_UPDATE"
- "REGISTER"
- "TRANSFER"
- "TRANSFER_IN"
- "TRANSFER_IN_ACCEPT"
- "TRANSFER_IN_CANCEL"
- "TRANSFER_IN_RESTART"
- "TRANSFER_IN_RETRY"
- "TRANSFER_OUT"
- "TRANSFER_OUT_ACCEPT"
- "TRANSFER_OUT_REJECT"
Header Parameters
A client provided identifier for tracking this request.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v2/customers/string/domains/notifications/schemas/AUTH_CODE_REGENERATE"{ "id": "string", "models": [ {} ], "properties": [ { "defaultValue": "string", "format": "string", "items": [ { "format": "string", "pattern": "string", "type": "string" } ], "maxItems": 0, "maximum": 0, "minItems": 0, "minimum": 0, "pattern": "string", "required": true, "type": "string" } ], "required": [ "string" ], "type": "object"}Authorization
bearerAuth Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
The Customer identifier. Note: For API Resellers, performing actions on behalf of your customers, you need to specify the Subaccount customer identifier you're operating on behalf of.
The notification ID to acknowledge
Header Parameters
A client provided identifier for tracking this request.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v2/customers/string/domains/notifications/string/acknowledge"Agent & Automation Notes
domains.domain:read, domains.domain:create, domains.domain:update, domains.contact:update, domains.nameserver:update, domains.transfer:execute, domains.transfer:update, domains.forward:updateRelated
Last updated on
How is this guide?