Get booking
Read a whole trip, every service type included, by microsite and booking reference. This is the call to make after a webhook, and the source of truth for back-office and accounting syncs.
Which microsite to use
- Look the booking up with the microsite it was made on first. On a
404, try your other microsites. - A mismatched
micrositeIdin the path has resolved bookings in the past. Don't rely on it: that loophole is expected to close. - If one booking can be reached from more than one of your microsites, map them all to one canonical microsite before you use
(micrositeId, bookingReference)as a key. Otherwise the same booking becomes two records.
Reading the hotel
The short version. The full field guide is in Reading bookings.
- Two services at the same hotel and dates are not a duplicate. When an agent cancels and rebooks,
hotelservice[]holds oneCANCELEDservice at price 0 and oneBOOKEDservice, with different service references. Never deduplicate by hotel and dates. - The booking total can exceed the sum of the hotel services. Booking-level fees, taxes and non-hotel or manual services are included in the total on a meaningful share of bookings. Reconcile the difference explicitly.
- Supplier currencies appear in the cost legs.
providerNetPriceandnetProvider.micrositecan be in the supplier's currency even when the guest paid in yours. For single-currency accounting, the.operatorlegs are a good choice. - Values change after booking. A repricing updates
pricebreakdown, and a cancelled service can drop to 0. - Text fields can contain HTML. Treat
remarks[]and service names as untrusted: strip markup before display.
What is not here
- A field called
externalReference. Your order id comes back asagencyBookingReference. Booking detail returns it under its own name. - A list of bookings. Use List bookings. The old listing variant of
getBookingsis deprecated.
Errors
| Status | Meaning | What to do |
|---|---|---|
404 | The reference doesn't exist in this microsite. It is not an outage. | Try your other microsites, then treat it as not issued. |
401 / 403 | Token rejected. | Re-authenticate once, then alert. A deleted API user gives the same 401 as a wrong password. |
5xx, 429, timeout | Temporary failure. | Retry with backoff. This call changes nothing. |
The spec documents no error schema. Keep the raw body and the trace id for support.
Related
- Reading bookings: every
hotelservice[]field and the money model - Webhooks: when to call this endpoint
- List bookings: find references by date
- Booking detail: one hotel, with your
externalReference
Cancellation fee
Get the penalty a booked hotel would cost if you cancelled it today. It is a read-only quote. It cancels nothing and refunds nothing.
List bookings
List the bookings of one microsite by creation date, with optional filters on departure, update and cancellation dates, a reference and the user. Returns each booking's reference, status and creation date, so read the details with Get booking.