Knowledge Base

Learn about top features of our solutions. Get help whenever you need.

English
Request limits and the list of errors in Exely Connect

Request limits and the list of errors in Exely Connect

Last update: Feb 13, 2025

Exely Connect 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:


Search API

Aggregation search: 3 requests per second, 20 requests per minute, 900 requests per hour.

Search by hotel: 50 requests per second, 200 requests per minute, 1000 requests per hour.

Search by extra services: 10 requests per second, 100 requests per minute, 1000 requests per hour.

Search by early check-in and late check-out rules: 10 requests per second, 100 requests per minute, 1000 requests per hour.


Reservation API

Verify: 10 requests per second, 15 requests per minute, 100 requests per hour.

Created: 10 requests per second, 15 requests per minute, 100 requests per hour.

Cancel: 5 requests per second, 10 requests per minute, 50 requests per hour.

CalculatePenalty: 10 requests per second, 15 requests per minute, 100 requests per hour.

Read: 50 requests per second, 500 requests per minute, 5000 requests per hour.


Content API

For all API: 50 requests per second, 200 requests per minute, 3000 requests per hour.


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

Incorrect request

Incorrect request. Check if the correct parameters were entered in the request on your side:

  • The value passed in the parameter is of an incorrect type.

  • A mandatory parameter is missing.

  • The number of items in the list exceeds the maximum allowed.

  • The specified parameters should not participate in the request.

Incorrect CreateBookingToken

Incorrect unique booking token. Check if the value is correct on your side.

Customer: firstName is required

The customer's first name must be entered.

Customer: lastName is required

The customer's last name must be entered.

Guest: firstName is required

The guest’s first name must be entered.

Guest: lastName is required

The guest's last name must be entered.

GuestCount: number of adults not specified

The number of adults is not specified.

ArivalDateTime {ARRIVAL_DATE} should be before departureDateTime {DEPARTURE_DATE}

Check-in time must be earlier than the check-out date.

Start date earlier than the end date

The start date of the stay must be earlier than the end date.

Booking is null

An empty request to create or verify a booking has been sent. Check if the request is correct on your side.

placement.code {PLACEMENT_CODE} incorrect

Invalid accommodation code.

BookingOrder: services not supported

Services are not supported.

BookingOrder: customer is required

Customer must be entered.

BookingOrder: roomStays not found

Stay option is not found.

RoomStay: incorrect guest count, can`t place

Incorrect number of quests is specified.

RoomStay: more guests than specified in GuestCount

More guests are specified than it is indicated in the “GuestСount” field.

Booking: roomStays is required

It is required to select a stay option.

RoomStay: stayDates is required

It is required to specify stay dates — date and time of check-in and check-out.

RoomStay: ratePlan is required

It is required to specify a rate plan.

RoomStay: roomType is required

It is required to specify room type details.

401

Authorization error

Check if the correct API-key was entered on your side.

403

The hotel did not provide access to its data

Try to call the method again not earlier than 5 minutes later.

404

Incorrect request path is specified

Probably, the property is deleted or incorrect ID was indicated.

429

Technical rules of the platform: large number of requests in a limited period of time

Exely Connect 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.


Need More Help? Contact Support

CONTACT SUPPORT