Choose an Integration Flow

Which flow should I choose?

Integration mode	Choose it when	Primary data strategy
Lightweight Integration	You want the fastest launch and do not need a full local hotel catalogue.	Discover destinations and hotels in real time.
Standard API Integration	You maintain your own hotel catalogue, room mapping, and list-page inventory.	Synchronize saleable hotel IDs and hotel static data locally.

Lightweight Integration

Recommended for new partners. The usual sequence is:

/search/destination — obtain a destination ID.
/search/hotelFilters — optionally retrieve filter options.
/search/hotelList — find hotels for the destination.
/hotel/detail and /hotel/images — load display data.
/booking/productDetails — retrieve real-time products when a traveller opens the booking path.
Continue with availability check, order creation, payment, and status notification.

Standard API Integration

Choose this flow when local hotel mapping is required:

/search/hotelIdList — obtain saleable hotel IDs.
/hotel/detail — synchronize hotel and room static data.
/hotel/increment — identify changed hotels and refresh local mappings.
/hotel/lowestPrice — optionally update list-page reference prices.
/booking/productDetails — always query sellable products in real time at the detail or booking step.

Do not query real-time products for hotels outside the local saleable-hotel cache.

Shared booking rule

Both flows must call /booking/availabilityCheck immediately before /booking/createOrder, and should call it again after the traveller enters the final room and guest information.