The following process flow diagrams show the steps to retrieve new, modified or cancelled reservations when all systems are functioning optimally.
Click on the diagram to see it in full screen. To return to the topic, click the browser's back button.
 |
1. Provider calls the reservations endpoint within the timeout period. 2. Provider integrates booking into their system and updates inventory. 3. Provider implements a short delay and begins the cycle again. We recommend a 20-seconds delay between reservations calls. |
The following process flow diagram shows the steps that lead to Booking.com systems triggering the fallback mechanism while retrieving reservations.
Click on the diagram to see it in full screen. To return to the topic, click the browser's back button.
 |
1. Provider calls the reservations endpoint within the timeout period. 2. Booking.com servers are temporarily unavailable. 3. Booking.com experiences extended system outage before pulling reservations. 4. Fallback mechanism is triggered and Booking.com sends reservations to property through email. |
→ To process reservations using the B.XML endpoint, see Retrieving reservations using B.XML