Get Products (GET /products) – when Klook sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child).

Get Product (GET /products/{productId}) – Klook re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

Mapping on Klook's side – Klook links each Ventrata option and unit to its own listing and ticket types. Your Klook account manager does this for you, or you do it in Klook's own portal if Klook offers one. You only share the connection's API key.

Klook reads your full product list about every 15 hours.

It re-reads each product about every 20 minutes.

Availability Check (POST /availability) – Klook sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (AVAILABLE, LIMITED, SOLD_OUT, CLOSED or FREESALE), the remaining vacancies, the booking cutoff and an availabilityId, which Klook needs to book that slot.

Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Klook can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

Availability Check: Klook checks your products throughout the day, usually starting about 2 months ahead and covering 20 days per request, looks up to about a year ahead and re-checks the same product and dates about every 8 hours.

Checks are spread through the day with no strong peak, which suggests a mix of scheduled syncs and live customer searches.

octo/pricing capability – Klook asks for prices by adding octo/pricing to the Octo-Capabilities header of its requests. Without it, Ventrata sends availability with no prices at all.

Availability Check (POST /availability) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Klook, both from the reseller's pricing in Ventrata (retail and wholesale/commission).

Group prices – when Klook also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing.

Booking Reservation (POST /bookings) and Booking Confirmation (POST /bookings/{uuid}/confirm) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at.

Klook requests octo/pricing on all of its availability checks, so it sells at your Ventrata prices.

Klook doesn't send the number of people per unit type, so prices come back per person, and group pricing such as Booking Size fares may not show correctly on Klook.

octo/offers capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and Klook can also send a promo code (offerCode).

Promotions work together with pricing, so they need octo/pricing as well.

This covers promotions you create in Ventrata (supplier-initiated promotions).

Klook doesn't usually request octo/offers, so check with Klook before relying on Ventrata promotions there.

Klook doesn't set a hold time, so the default hold time applies.

A typical Klook booking is for about 2 people.

It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire.

Klook also checks the bookings it has made, with Get Booking (GET /bookings/{uuid}) about once a day, for example to reconcile its records.

octo/pickups capability – Klook can see which options offer pickup and their pickup points, and send the customer's pickup point or hotel with the booking.

If a hotel doesn't match one of your pickup points, Ventrata saves it with the booking so you can arrange the pickup.

Klook requests the octo/pickups capability, but doesn't usually send a pickup point or hotel with its bookings. Check with Klook how it collects pickup details.