Coco-Moola is an online travel agency (OTA) for London, selling attraction tickets, sightseeing bus and boat tours, immersive exhibitions, afternoon tea and day trips to English theme parks, Bath and countryside sites. The site runs in ten languages including French, German, Spanish, Polish, Russian and Mandarin, with prices in pounds, euros and US dollars. For operators, it brings inbound European and Asian visitors to London ahead of domestic day-trippers, booking headline attractions and sightseeing in their own language for a city break.

Connecting Coco-Moola to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Coco-Moola, visit cocomoola.com.

Primary website	cocomoola.com
Tags	Sightseeing & Hop-On Hop-Off
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Multilingual London attractions and sightseeing for inbound visitors
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Coco-Moola (using Ventrata's OCTO API)

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

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

Creating the Coco-Moola Connection

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

Before you begin:

You must have a commercial agreement with Coco-Moola for them to sell your products. To inquire about partnering with them, contact them via cocomoola.com.
You must have Coco-Moola 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 Coco-Moola from the list of partners.
Select Coco-Moola 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 Coco-Moola 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 Coco-Moola

Securely share the OCTO API key shown on the connection you've created with your Coco-Moola 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 Coco-Moola team to complete this.

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

📗 TIP

Coco-Moola 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 Coco-Moola Connection

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

Connection Features Detailed

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

In short: Coco-Moola 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 Coco-Moola, so anything you change in Ventrata reaches Coco-Moola the next time it checks.

Timings are typical for Coco-Moola and rounded, and they can change if Coco-Moola changes how it syncs.

Product Mapping	❌	You can't map products from Ventrata. Coco-Moola maps them on its side, through your account manager or Coco-Moola's portal. This works as follows: Get Products (`GET /products`) – when Coco-Moola 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}`) – Coco-Moola re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Coco-Moola's side – Coco-Moola links each Ventrata option and unit to its own listing and ticket types. Your Coco-Moola account manager does this for you, or you do it in Coco-Moola's own portal if Coco-Moola offers one. You only share the connection's API key. What this means for you: Coco-Moola can only sell what it has mapped. When you add a product, option or unit in Ventrata, Coco-Moola may see it on its next refresh, but it won't sell it until it's mapped. So tell your Coco-Moola account manager whenever you add one.
Content Sync	✅ / ❌	Coco-Moola can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Coco-Moola 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 Coco-Moola on its next product refresh. Typically with Coco-Moola: Coco-Moola requests `octo/content`.
Availability Sync	✅	Coco-Moola checks your live availability in Ventrata. Ventrata doesn't push availability changes to Coco-Moola. This works as follows: Availability Check (`POST /availability`) – Coco-Moola 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 Coco-Moola 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 Coco-Moola can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Coco-Moola: Availability Check: Coco-Moola checks your products throughout the day, usually starting tomorrow and covering a single day per request, looks up to 10 days ahead and re-checks the same product and dates about every 16 hours. Availability Calendar: Coco-Moola checks your products throughout the day, usually starting today and covering 31 days per request, looks up to 28 days ahead and re-checks the same product and dates about every 13 hours. Checks are spread through the day with no strong peak, which suggests a mix of scheduled syncs and live customer searches. What this means for you: when you close a date, change capacity or sell out in Ventrata, Coco-Moola shows it after its next check. For dates it checks regularly, that's within about 13 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Coco-Moola asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Coco-Moola 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 Coco-Moola, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Coco-Moola 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 Coco-Moola: Coco-Moola requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Coco-Moola sends the number of people per unit type, so group prices are calculated for the actual booking. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Coco-Moola to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Coco-Moola's portal. Otherwise it may be off, and Coco-Moola won't receive your Ventrata prices. 📗 TIP – If prices on Coco-Moola look wrong, check the Coco-Moola reseller's pricing in Ventrata first: that's what Coco-Moola reads.
Promotions Sync	❌	Your Ventrata promotions don't apply on Coco-Moola. Prices on Coco-Moola don't include promotions you create in Ventrata. Set up any promotions with Coco-Moola directly.
Bookings Sync	✅	Bookings and cancellations made on Coco-Moola 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 Coco-Moola, Coco-Moola 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, Coco-Moola 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. Coco-Moola gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Coco-Moola 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 Coco-Moola, Coco-Moola 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 Coco-Moola has to contact you. Change: Coco-Moola doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Coco-Moola: Coco-Moola holds places for about 60 minutes while the customer pays (`expirationMinutes`). A typical Coco-Moola booking is for about 1 person. ‼️ IMPORTANT – Bookings sync one way, from Coco-Moola to Ventrata. If you cancel, change or rebook a booking from Coco-Moola in Ventrata, for example in the Dashboard, Coco-Moola isn't notified. Contact Coco-Moola so the booking is cancelled or changed on their side too, or ask the customer to cancel through Coco-Moola.
Pickups/Dropoff Sync	❌	Coco-Moola doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Coco-Moola how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Coco-Moola doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Coco-Moola how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Coco-Moola. Customers can only book your main products and options on Coco-Moola. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Coco-Moola. Ventrata doesn't notify Coco-Moola when a ticket is scanned or redeemed. Coco-Moola only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Coco-Moola pass holders can't be scanned at your entrance without a booking. Customers from Coco-Moola need a booking made through Coco-Moola before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Coco-Moola. Gift cards bought in Ventrata can't be used on Coco-Moola, and Coco-Moola can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Coco-Moola connection

Delays: availability and prices reach Coco-Moola only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Coco-Moola can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Coco-Moola 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: Coco-Moola issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Coco-Moola 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 Coco-Moola.

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

Coco-Moola Limited

cocomoola.com

Ventrata Partner ID: e81dc09c-f3f9-4bfc-9424-690aca408ca3

Coco-Moola: Reseller Connection