Developers » Go live
Go live
Before you sell to real guests, run through this list with a hotel you work with. Each item is something that has gone wrong for an agency before.
Before your first real booking
- Content loads in every language you sell in, and you store it per
locale. - You show the policies. Your client sees the cancellation policy and the payment policy of the rate plan before booking. They are part of what they agree to.
- Occupancy is right. Children are sent as ages, one per child, not as a count. Test a party with children and a party that does not fit the room, and check that the second one is refused, not "fixed".
- Every booking sends a
ref_id, and a retried booking does not create a second one. - You book within the search's thirty minutes, or you search again.
- You handle
REQUESTED. If a hotel confirms bookings itself, your system waits forAPPROVEDand tells your client only then. - Your webhook endpoint checks the signature and answers within ten seconds.
- You read errors by
code, not bymessage.
Make a test booking
Make one booking end to end with the hotel, on a date it agrees to: search, book, read it back, change a guest's name, cancel it. Ask the hotel to confirm that what it sees in Quendoo matches what you sent.
Tell us
When you are ready, or if something does not behave as described here, write to us through Get access with your agency name and the hotels you sell.
Already integrated?
The paths, the token and the shape of the answers are the same as they have always been. What behaves differently:
- Availability no longer counts rooms a hotel holds in a sales block for someone else.
- Deleted properties and rate plans are no longer listed or sold.
- Refusals name their cause. Error 10 says why a room cannot be booked (see Errors).
- Duplicate bookings are refused. A
ref_idthat already names a live booking of yours is refused with error 13 on every booking call. - Webhooks are sent as
application/json, carry asequencenumber, and an empty change is not sent (see Webhooks).