Welcome to the RIPE Database REST API documentation.
For more information about the REST paradigm, see http://en.wikipedia.org/wiki/Representational_state_transfer.
If you used the old (beta) API, consider reading the migration guide for old API users.
All the services are accessible via HTTPS, and HTTP may only be used for lookups.
Use of the Whois REST API is governed by the RIPE Database terms and conditions.
Each object in the RIPE Database has a unique locator URI, in the following format:
All services support the standard HTTP/1.1 content negotiation method.
The client should specify the desired response format using the
Accept: header in the HTTP request. If unspecified, the response defaults to XML. The HTTP response will include a
Content-Type: header, and the response body will be encoded in the requested format.
The possible values that you can specify for the Accept header are:
Clients can also append an extension of
.json to the request URL instead of setting an
Accept: header. The server will return a response in the appropriate format for that given extension.
Client applications should use the HTTP status code to detect the result of an operation. Any error messages will be includes in the response body (see below).
Possible reasons for various HTTP status codes are as follows:
|HTTP Status Code||Cause|
|Bad Request (400)||The service is unable to understand and process the request.|
|Forbidden (403)||Query limit exceeded.|
|Not Found (404)||No results were found (on a search request), or object specified in URI does not exist.|
|Conflict (409)||Integrity constraint was violated (e.g. when creating, object already exists).|
|Internal Server Error (500)||The server encountered an unexpected condition which prevented it from fulfilling the request.|
If the request fails, any error messages will be returned in the response body, using the requested Accept format (XML or JSON). This element will not be included on a successful response.
For more details, see Whois Resources.
Please take into account the following points to avoid unexpected encoding behaviour:
The RIPE database is available via the URL:
The TEST database is available via the URL:
See Whois Resources.
It could take up to 10 seconds before an update becomes visible for lookup or search operations. For non-hierarchical object types (person, role, organisation, ....), the typical latency is less than 1 second. For hierarchical object types (inet(6)num, route(6), domain), it is about 3-5 seconds on average, up to 10 seconds maximum.
A way to work around this is limitation is to rely on the response of the the muting operation in REST API (PUT, POST, DELETE). These all return the object as it appears in the database in their response body after the successful update. This object is never filtered or altered in any way.