Any API has limits on the number of requests. If the limit is exceeded, API will show error code 429 and json in the following format:
{
"message": "%description%"
}
Below are the base limits, which can be revised on a case-by-case basis — it all depends on the growth in the number of bookings:
Read Reservation API
/v1/properties/{propertyId}/bookings method: 3 requests per second, 60 requests per minute, 1200 requests per hour.
/v1/properties/{propertyId}/bookings/{number} method: 10 requests per second, 200 requests per minute, 4000 requests per hour.
Content API
For all API: 50 requests per second, 200 requests per minute, 3000 requests per hour.
For example, there is a limit on hotel search in the Content API — 50 requests per second. If the 51st request comes during one second, all other requests will be returned with an error till the second ends.
The list of codes with error description
HTTP-code | Brief error description | Detailed error description |
200 | The request was successful | Standard response to the operation, no errors occurred. |
400 | Invalid request | |
401 | Authorization error | Check that the authentication data is correct |
403 | The property did not provide access to its data | Try to call the method again no earlier than 5 minutes later. or contact the property. |
404 | Incorrect request path is specified | Probably, the object is deleted or an incorrect ID was indicated. |
429 | Technical rules of the platform: large number of requests in a limited period of time | API has limits on the number of requests per second, minute, hour. Information about which limit is exceeded is passed in the “warning” parameter in the response to the request. In this case, it is necessary to wait until the hour, minute, second is over. |
500 | Internal server error | Try calling the method again not earlier than 5 minutes later. The issue might be on our side. If the error reoccurs, contact Exely Customer Support team. |
