Lightweight Integration Flow

When to choose Lightweight integration

Choose this approach when you need a complete hotel search and display flow without first maintaining a full local hotel catalogue. Destination search, hotel list, filters and images are requested through G-Link as the traveller explores.

Required flow

Query destination by country, city or keyword and retain the destination ID.
Get hotel filters and Get hotel list for the destination.
Use Query hotel basic information and Query hotel images for the detail experience; synchronize changes with Query hotel incremental information if you cache data.
For a real booking, use the same protected path as Standard integration: real-time product → trial booking → create order → pay order → webhook.

What can be cached

Data	Guidance
Destination, filter and hotel-list results	Cache only according to your product freshness policy; refresh before quoting a bookable price.
Hotel details and image collections	May be cached; use the increment API to identify changes.
Products, stock, price and cancellation policy	Always request in real time for the selected stay dates and guests.
Booking result	Trust a successful trial/create/pay result plus the signed webhook, not stale search data.

Order safety rules

Repeat trial booking immediately before final submission with actual room and guest details.
Use a unique coOrderCode and idempotency key for write operations.
Call Pay order only after your local payment succeeds or confirmation is required.
Use the webhook as the primary confirmation mechanism; do not continuously poll order details.