What is a fallback message?
We send fallback messages any time your system fails to pick up a new reservation, modification or cancellation message. In each case, your system has a maximum of 30 minutes to pick up the new messages, and if it doesn’t, we’ll send you a fallback message via email.
Please note that we don’t push reservations to your interface or have a webhook actively ping you. Instead, in order to avoid fallbacks, overbookings and pricing mismatches, we recommend that you configure your system to pull messages every 30 seconds, if possible.
For more information about fallbacks, read our article about retrieving failed reservations.
What other factors can cause a reservation not to be received via XML?
Fallbacks aren’t the only reason you may not receive your reservations through XML. Here are some others:
- Non-XML rates: it’s possible to configure rates as non-XML, at the request of the property. We recommend you check if the rate in question has been configured as a non-XML rate.
- Mapping error: we recommend you check that the rooms and rates were correctly mapped before the reservation confirmation was retrieved.
- Connection not confirmed: errors can also arise when properties haven’t completed the auto sign-up process. Sometimes you may have confirmed the connection, but the property hasn’t yet done so from their side. We recommend you check the ‘Properties’ section of your Provider Portal. If the connection status says ‘XML Active’, it means both sides have confirmed and the connection is fully established.
- Enqueuing not enabled for modifications/cancellations: please check if modifications and cancellations were enqueued.