Beta version

This API endpoint is currently in beta. Make sure to direct any questions during the beta phase to your Booking.com contact person via the appropriate channels.

Reservations Recovery API overview

Use the Reservations Recovery API to recover missed reservations.

You can use this API to recover missed reservations. Use this API along with the Reservations API (both OTA XML and B.XML endpoints). This topic helps you to identify situations in which you cannot process all reservations and provides process diagrams to help you implement the API.

Properties still receive emails even after implementing this API

When Booking.com determines that a reservation was missed, it triggers a fallback email and sends it to the property. This email is similar to the notification used with properties without a Connectivity implementation.

What are missed reservations?

Missed reservations are those messages (including confirmations, modifications, and cancellations) that were not:

  • Pulled within 30 minutes (using the B.XML endpoint). For example, you did not retrieve the reservations within the timeout period.
  • Pulled and acknowledged within the 30-minute timeout period (using the OTA XML endpoints). For example, you did not acknowledge a reservation by calling the POST OTA_HotelResNotifRS endpoint within the timeout period.

Active rejections are currently not supported

Reservations messages that were actively rejected using the POST OTA_HotelResNotifRS endpoint with an <Error> tag response are currently not returned using the missed-reservations endpoint.

Why use the Reservations Recovery API?

To manage missed reservations without implementing this API, you must either:

  • Go to the Connectivity Portal and select Reports > Email Fallbacks.
  • Read the fallback emails that Booking.com sends you.

Both of these options require manual effort and are not scalable. However, the Reservations Recovery API enables you to process the missed reservations data with better filtering, performance, and accessibility options:

Reservations Recovery API process

This section provides the process flow diagrams when using both OTA XML and B.XML Reservations API endpoints.

OTA reservations recovery process

The following 2 process flow diagrams show the steps to recover missed reservations that are new, modified, or cancelled.

Click on the diagram to see it in full screen. To return to the topic, click the browser's back button.

Retrieve missed reservations Retrieve missed reservations
1. Provider fails to acknowledge a new reservation within the 30-minute timeout period by calling the POST OTA_HotelResNotif endpoint. Booking.com sends the reservations directly to the property through an email.
2. Provider calls the GET /reservations-flow-control/missed-reservations endpoint after the 30-minute timeout period.
3. Booking.com returns reservation ID(s) of any missed reservations with reference_type=confirmation.
4. Provider calls the GET OTA_HotelResNotif endpoint with the specific reservation ID and property ID.
5. Provider integrates booking into their system and updates inventory.
6. Provider calls the POST OTA_HotelResNotif endpoint within the timeout period.
7. Booking.com returns a successful OTA_HotelResNotifRS message.
1. Provider fails to acknowledge a modified/cancelled reservation within the 30-minute timeout period by calling the POST OTA_HotelResModifyNotif endpoint. Booking.com sends the reservations directly to the property through an email.
2. Provider calls the GET /reservations-flow-control/missed-reservations endpoint after the 30-minute timeout period.
3. Booking.com returns reservation ID(s) of any missed reservations with reference_type=confirmation or cancellation.
4. Provider calls the GET OTA_HotelResModifyNotif endpoint with the specific reservation ID and property ID.
5. Provider integrates booking into their system and updates inventory.
6. Provider calls the POST OTA_HotelResModifyNotif endpoint within the timeout period.
7. Booking.com returns a successful OTA_HotelResModifyNotifRS message.

B.XML reservations recovery process

Retrieve missed reservations
1. Provider fails to retrieve a new reservation within the 30-minute timeout period by calling the POST reservations endpoint. Booking.com sends the reservations directly to the property through an email.
2. Provider calls the GET /reservations-flow-control/missed-reservations endpoint after the 30-minute timeout period.
3. Booking.com returns reservation ID(s) of any missed reservations with failure_type=missed deadline or missed reservation.
4. Provider calls the POST reservations endpoint with the specific reservation ID and property ID.
5. Booking.com returns the reservations details.
6. Provider integrates booking into their system and updates inventory.
7. After a delay, call the /reservations endpoint again.

Quick Actions

→ To retrieve missed reservations, see Retrieving missed reservations