Standard API Integration

When to choose Standard integration

Choose this approach when you maintain your own hotel catalogue and search/listing experience. Synchronize static content locally, then query availability and prices in real time only when the traveller needs them.

Mandatory interfaces

Static data: Query country list, Query city list, Get saleable hotel ID list, and Query hotel basic information.
Catalogue maintenance: Query hotel incremental information; update or unmap locally changed hotels and rooms.
Real-time booking: Query product in real time → Trial booking → Create order → Pay order.
Order lifecycle: receive order-status webhook; use Query order details for compensation; call Cancel order when needed.

Recommended synchronization

Data	Recommended handling
Countries and cities	Load during initial setup and refresh when mapping changes.
Saleable hotel IDs and details	Build the local catalogue from ID list, then fetch full hotel/room details.
Hotel increment	Run periodically; additions, changes and deletions must update local mapping.
Daily lowest price	Use for display/listing reference only; refresh daily after 05:00 where applicable and never treat it as a bookable price.

Booking path

At the hotel detail or booking step, call Query product in real time.
Call Trial booking when the traveller clicks Book, and repeat it immediately before order submission using the actual room count.
Call Create order only after the final trial succeeds; retain the unique partner coOrderCode.
After local payment succeeds, call Pay order.
Use the signed order-status webhook as the primary result; stop any compensation lookup as soon as the order becomes confirmed, rejected or cancelled.

Important: the legacy name hotelBooking in historical material is superseded by the current /booking/createOrder operation in this API Reference.