Suche in diesem Bereich
Every user can use the JSON API without additional activation.
Only 3 requests per second and IP can be executed.
The system responses in the JSON interface always have the same structure:
- status: the Restcall status
- stid: the unique transaction ID assigned by the system
- object: the object in the request
- data: the data block containing the requested data. This is a list with 0 - n elements.
Structure of the Routes
The JSON API knows five request types:
CREATE = Creating an object
UPDATE = Changing an existing object
DELETE = Deleting an existing object
INFO = Single query of an object
LIST = List query for a group of identical objects
The URLs for the various Restcalls are structured according to the following schema:
CREATE = POST /object group
UPDATE = PUT /object group/$identifier
DELETE = DELETE /object group/$identifier
INFO = GET /object group/$identifier
LIST = POST /object group/_search
For many object groups, there are additional routes that address other order types in the system. These are described in the technical documentation.
For the JSON interface there is a technical documentation according to OpenAPI 2.0 standard. For further use of the OpenAPI documentation it is available in the InterNetX Github Repository.
A connection test is performed via the route GET /hello. The route does not perform an operation and is only used for the connection test.
Login and Authentication
The AutoDNS JSON API provides authentication via a SessionID and BasicAuth.
The use of a UserAgent is mandatory for the correct use of the JSON API.
System notifications are asynchronous notifications that inform you about the status of an order. They are sent with a time delay because other instances, such as a registry, are involved in the processing of the process.
Meaning of Status Types and Status Codes
The system responses contain information about the request status in the tag <status>. Documentation is here.
The API offers the possibility to perform complex list inquiries.
The API Processes section contains step-by-step instructions for various domain and certificate processes to help you implement the Domain-Robot API. Each of them describes how a process can be automated and includes corresponding XML and JSON examples.