Search in this section
Page History
Instructions for the complete automation of the deletion of a domain.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Basics of the JSON and XML API
All important information for the use of the JSON and XML API you can find in the General API Basics and the XML API Basics and JSON API Basics.
Process overview
Flow chart
Task names, codes and routes
Task | Code | Route |
---|---|---|
DomainCancelationCreate | 0103101 | POST /domain/ {name} / cancelation |
PollConfirm | 0906 | PUT /poll/$id |
DomainInfo | 0105 | GET / domain/$name |
Process
Deleting domains is an asynchronous process because the registry is involved in the processing of the request. The system notifications are made available in the system upon receipt and can be retrieved by polling.
Info |
---|
For more details on system notifications, see page System Notifications |
Starting a domain cancelation create request
To delete a domain create a cancelation request (DomainCancelationCreate) with the cancelation type DELETE.
There are three options for the time of deletion (execution type):
- EXPIRE: Deletion at expiration date oof the domain
- NOW: immediate deletion
- DATE: Deletion on the specified date
For XML, the date is set in theexecdate
(=execution date) tag.
Format : yyyy-MM-dd or yyyy-MM-dd hh:mm:ss
Example : 2019-06-18 16:33:24
For JSON, it is specified as the value of theregistryWhen
field.
Format : yyyy-MM-dd'T'HH:mm:ssSSSZ
Example : 2019-06-18T16:33:24.000+02
Example: Deleting a domain at the expiration date - execution type EXPIRE
SP Tabs group | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Example: Deleting a domain immediately - cancelation type NOW
SP Tabs group | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Example: Deleting a domain at a specific date - execution type DATE
SP Tabs group | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Receive notifications
The DomainCancelationCreate task creates a cancelation request.
This triggers the creation of a second cancelation request, which is processed at the time defined in the cancelation (asynchronous processing).
Once this second request has been processed, a system notification is sent, indicating whether the deletion was successful or not.
The notification can be retrieved using the Polling and Push methods.
Info |
---|
Since the second cancelation request does not exist at the time the notice is created, the system can not inform you of the JobID in advance. To determine whether this is the request for the desired deletion, check whether these keywords contain the values specified here in the system response sent later:
These three lines indicate that it is the action "Delete", the object type that was deleted is a domain, and the name of the domain here is "example.com". |