One transactional flow, every vertical.
Confirm an option, book it, then amend or cancel it. The same lifecycle applies to hotels today and to every vertical we add.
Lifecycle
Queries read. Transactions commit.
Eight documented steps, split cleanly so the shape of your integration is settled before you write the booking code.
03 Availability options
Fetch live options for the selected hotels and occupancy.
Concepts
Three things to decide up front.
These are the decisions that cause integrations to be rebuilt when they are made late.
Deltaprice
The price variation you accept between quote and book, as a percentage, an absolute tolerance, or both. Too tight rejects viable bookings; too loose erodes margin. It belongs in configuration, not code.
Client reference
An arbitrary string attached to a booking so it cross-references against your own systems. Set it to something meaningful — you will want it during your first incident, and it cannot be added afterwards.
Quote before book
You never book straight from a search result. Confirmation turns an availability option into a priced, committed quote, which is where price movement surfaces.
Testing
Build most of it before you go live.
Booking is disabled in the sandbox, but datasets, content, availability and confirmation all behave as they do in production.
Certification
Production access is issued with a separate key once your integration is certified. Plan for the booking path to be exercised first against production with a real transaction, and schedule that deliberately rather than discovering it on launch day.
Cancellation policies come from the supplier. Surface the policy attached to an option at the point the customer commits, not after.
Ship travel supply in days, not quarters.
Get a sandbox key and make your first availability call this week.