Chillout London is an independent London travel concierge and tour operator based at Westminster Pier, with over fifteen years in the market, packaging attraction tickets, guided walks, coach tours, Thames cruises, stadium tours and afternoon tea. It also sells day trips to Stonehenge, Edinburgh and Paris plus private hire and airport transfers. For operators, it brings UK and international visitors who want a curated London itinerary, booking several activities and tickets together through one concierge, priced in sterling.

Connecting Chillout London to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Chillout London, visit chilloutlondon.com.

Primary website	chilloutlondon.com
Tags	Operator Reselling Others
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Curated multi-activity London itineraries through one concierge
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Chillout London (using Ventrata's OCTO API)

This reseller connection lets you sell your products through Chillout London without managing availability, pricing and bookings by hand. Features of this connection include:

Availability Sync – Chillout London checks your live availability in Ventrata.
Pricing Sync – Chillout London gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Chillout London are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Chillout London Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

You must have a commercial agreement with Chillout London for them to sell your products. To inquire about partnering with them, contact them via chilloutlondon.com.
You must have Chillout London created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Chillout London from the list of partners.
Select Chillout London Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Chillout London connections and would like to differentiate between them more easily in the future.
Press the Create Octo Connection button.

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

Mapping Products to Chillout London

Securely share the OCTO API key shown on the connection you've created with your Chillout London contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Chillout London team to complete this.

Your Ventrata configuration is complete. You do not need to take any further steps.

📗 TIP

Chillout London can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

Managing the Chillout London Connection

Allow or disallow products: limit which destinations, products and options Chillout London can access. See how to allow or disallow products.
Rename the connection to tell several Chillout London connections apart.

Connection Features Detailed

This section is for anyone who wants to know exactly how the Chillout London connection works: which Ventrata OCTO API calls Chillout London makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

In short: Chillout London pulls everything it needs from Ventrata. It reads your products, checks your availability and prices, and sends bookings and cancellations. Ventrata doesn't push changes to Chillout London, so anything you change in Ventrata reaches Chillout London the next time it checks.

Timings are typical for Chillout London and rounded, and they can change if Chillout London changes how it syncs.

Product Mapping	❌	You can't map products from Ventrata. Chillout London maps them on its side, through your account manager or Chillout London's portal. This works as follows: Get Products (`GET /products`) – when Chillout London 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}`) – Chillout London re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Chillout London's side – Chillout London links each Ventrata option and unit to its own listing and ticket types. Your Chillout London account manager does this for you, or you do it in Chillout London's own portal if Chillout London offers one. You only share the connection's API key. Typically with Chillout London: Chillout London reads your full product list about every 2 hours. It re-reads each product about every 20 hours. What this means for you: Chillout London can only sell what it has mapped. When you add a product, option or unit in Ventrata, Chillout London may see it on its next refresh, but it won't sell it until it's mapped. So tell your Chillout London account manager whenever you add one.
Content Sync	✅ / ❌	Chillout London can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Chillout London adds it to the `Octo-Capabilities` header, Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content, such as descriptions, highlights, inclusions and images. Content changes in Ventrata reach Chillout London on its next product refresh. Typically with Chillout London: Chillout London requests `octo/content`.
Availability Sync	✅	Chillout London checks your live availability in Ventrata. Ventrata doesn't push availability changes to Chillout London. This works as follows: Availability Check (`POST /availability`) – Chillout London 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 Chillout London needs to book that slot. Availability Calendar (`POST /availability/calendar`) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Chillout London can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Chillout London: Availability Calendar: Chillout London checks each product about every 17 hours, usually starting today and covering 43 days per request and looks up to 41 days ahead. What this means for you: when you close a date, change capacity or sell out in Ventrata, Chillout London shows it after its next check. For dates it checks regularly, that's within about 17 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Chillout London asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Chillout London 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 Chillout London, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Chillout London 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. Typically with Chillout London: Chillout London requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Chillout London 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 Chillout London. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Chillout London to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Chillout London's portal. Otherwise it may be off, and Chillout London won't receive your Ventrata prices. 📗 TIP – If prices on Chillout London look wrong, check the Chillout London reseller's pricing in Ventrata first: that's what Chillout London reads.
Promotions Sync	✅ / ❌	Your Ventrata promotions can apply to Chillout London prices and bookings. This works as follows: `octo/offers` capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and Chillout London 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). Typically with Chillout London: Chillout London requests `octo/offers`.
Bookings Sync	✅	Bookings and cancellations made on Chillout London are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on Chillout London, Chillout London sends the product, option, chosen slot (`availabilityId`) and one unit item per person. Ventrata checks capacity again and creates an `ON_HOLD` booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, Chillout London confirms the hold. The booking becomes `CONFIRMED` in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Chillout London gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Chillout London never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on Chillout London, Chillout London cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Chillout London has to contact you. Change: Booking Update (`PATCH /bookings/{uuid}`) – lets Chillout London change a booking in place, for example a new date, time or number of people. Some resellers cancel and rebook instead. ‼️ IMPORTANT – Bookings sync one way, from Chillout London to Ventrata. If you cancel, change or rebook a booking from Chillout London in Ventrata, for example in the Dashboard, Chillout London isn't notified. Contact Chillout London so the booking is cancelled or changed on their side too, or ask the customer to cancel through Chillout London.
Pickups/Dropoff Sync	❌	Chillout London doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Chillout London how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Chillout London doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Chillout London how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Chillout London. Customers can only book your main products and options on Chillout London. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Chillout London. Ventrata doesn't notify Chillout London when a ticket is scanned or redeemed. Chillout London only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Chillout London pass holders can't be scanned at your entrance without a booking. Customers from Chillout London need a booking made through Chillout London before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Chillout London. Gift cards bought in Ventrata can't be used on Chillout London, and Chillout London can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Chillout London connection

Delays: availability and prices reach Chillout London only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Chillout London can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Chillout London can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.
Tickets: Chillout London issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Chillout London can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Chillout London.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

📚 More about Ventrata connections

Partner Information

Chillout London Limited

42 Jedburgh Street, London, England, SW11 5QB

United Kingdom

chilloutlondon.com

Ventrata Partner ID: d5cb9863-6faa-42f9-afb0-c69dc1e0e553

Chillout London: Reseller Connection