BookingReservations
Endpoint
Section titled “Endpoint”POST {base_url}/1.0/bookings/reservationsList the reservations created in a date range, with a summary of each one.
Headers
Section titled “Headers”| Header | Value |
|---|---|
Authorization |
Bearer <access_token> |
Content-Type |
application/json |
Accept |
application/json |
Request body
Section titled “Request body”{ "createdRange": { "from": "2026-04-13", "to": "2026-04-16" }}| Field | Type | Description |
|---|---|---|
createdRange |
object | Range of reservation creation dates |
createdRange.from |
string | Start of the range, YYYY-MM-DD |
createdRange.to |
string | End of the range, YYYY-MM-DD |
In one sample, the range was applied to the reservation’s creation date, not to the check-in date.
Response
Section titled “Response”{ "reservations": [ { "id": 21204517, "status": "CONFIRMED", "dateSale": "2026-04-14T09:12:45.317", "checkIn": "2027-05-15T00:00:00", "clientReference": "10045", "clientName": "John", "clientSurname": "Smith", "hotelId": 100652, "hotelName": "Ocean View Cancun Arenas" }, { "id": 21204688, "status": "CANCELLED", "dateSale": "2026-04-15T16:03:08.25", "checkIn": "2027-05-15T00:00:00", "clientReference": "10046", "clientName": "Maria", "clientSurname": "Lopez", "hotelId": 100652, "hotelName": "Ocean View Cancun Arenas" } ], "eventId": "5b8e2f41-9a7c-4d3e-b1f6-2c0d8a9e7f13"}This example is illustrative, not a capture: it follows the shape of an observed response, and its values are not real.
Response fields
Section titled “Response fields”| Field | Type | Notes |
|---|---|---|
reservations |
array | Reservations created in the range |
reservations[].id |
int | Reservation ID |
reservations[].status |
string | Reservation status. In one sample of six entries: CONFIRMED in four and CANCELLED in two. Do not assume these are the only values. |
reservations[].dateSale |
string | Sale date and time, without a time-zone designator. In one sample of six entries, the fractional seconds had three digits in four entries, two in one and one in one. Do not assume a fixed number of digits. |
reservations[].checkIn |
string | Check-in date and time, without fractional seconds or a time-zone designator, in the six entries of one sample |
reservations[].clientReference |
string | Partner reference |
reservations[].clientName |
string | Holder’s first name |
reservations[].clientSurname |
string | Holder’s last name |
reservations[].hotelId |
int | Hotel ID |
reservations[].hotelName |
string | Hotel name |
eventId |
string | Trace ID |
Each entry is a summary: it does not include check-out, amount, currency, rooms or cancellation policies. For those details, use BookingGet.
Errors
Section titled “Errors”| Code | HTTP | Message | Cause | What to do |
|---|---|---|---|---|
| 6102 | 400 | Invalid range, only 31 days are allowed |
The message states that the range is not valid and gives a number of allowed days; how the days are counted is not defined. | Reduce the range, or split the period into several requests. |
In one sample, a range in which to was 30 days after from was accepted, and one in which to was 31 days after from was rejected with 6102. How the days are counted is not defined.
The other error codes specific to this endpoint are not documented. For the codes common to all endpoints, see Error codes.
Use cases
Section titled “Use cases”- List the reservations created in a date range. The list can include cancelled reservations: check
statuson each entry. - Match the reservations against your own records using
clientReference, filtering the list on your side.
Recommendations
Section titled “Recommendations”- Request the narrowest range that covers what you need.
- Avoid wide ranges and polling this endpoint.

