Introducing the Reservation Recovery API – your way to reduce fallbacks
06-Jul-2023
Key takeaways
- Reduce overbookings and improve your partners’ and their guests’ experiences by recovering reservation IDs
- Retrieve reservation IDs that have timed out due to outages and are at risk of fallback
- A fallback email will only be sent to properties if the reservation is not acknowledged after 24 hours
Looking for more transparency and control to reduce timed-out reservation fallbacks? With the new Reservation Recovery API, you’ll be able to act on reservations more quickly, improve your connection quality score and reduce the risk of overbookings caused by missed reservations.
Streamlined fallback management
Reservation fallbacks often happen when properties are unable to acknowledge a reservation within the 30-minute acknowledgement period (or 24 hours, if they have extended this period) – whether that’s due to technical problems, sync issues or other causes. You can manage these fallbacks with this API solution and reduce manual processes. Rather than relying on email notifications and fallback summary spreadsheets, they can get a regular overview of missed reservations via the API.
Reservation ID retrieval
The Reservation Recovery API works together with the Reservation API to back up unacknowledged reservation IDs. It’s recommended that properties call the Reservation Recovery API every 30 minutes to pull a list of all reservation IDs that haven't been acknowledged yet. This gives them a clearer picture of unacknowledged reservation IDs and a backup in case of any outages or technical issues.
Reservation fallback email holds
When the Reservation Recovery API is integrated, fallback emails will be held for 24 hours before being sent to properties. This allows them extra time to acknowledge reservations in case of outages or other delays.
We’re excited to reshape the way reservations are delivered. The Reservation Recovery API is your key to unlocking reliable and efficient reservations. Get started today and experience the difference.
For more information about this solution, check out the Reservation Recovery Handbook.