Tootbus is the sightseeing brand of RATP Dev, running hop-on hop-off routes on low-emission open-top buses in Paris, London, Brussels, Barcelona, Madrid, Rome and Tuscany. It packages partner attractions, river cruises and walking tours into Discovery bundles and attraction combos alongside its own one- to three-day passes. For operators, it brings first-time city visitors at the start of a stay, who buy a bus pass and add third-party products from the same basket, with French, British and Belgian city breaks the core markets.

Connecting Tootbus to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically. Tootbus uses Ventrata as their primary ticketing system.

To learn more about partnering with Tootbus, visit tootbus.com.

Primary website	tootbus.com
Tags	Operator Reselling Others · Sightseeing & Hop-On Hop-Off · Ventrata Client
Destination markets	🇧🇪 Belgium · 🇫🇷 France · 🇬🇧 UK
Source markets	🌎 Global
Specialties	Attraction bundles for first-time city visitors
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	Ventrata (using Ventrata's OCTO API)

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

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

Creating the Tootbus Connection

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

Before you begin:

You have a commercial agreement with Tootbus for them to sell your products.
Tootbus is created as a Reseller in Ventrata, with retail and wholesale/commission pricing set up.

Tootbus runs on Ventrata, so this is a Ventrata-to-Ventrata connection. You create a Ventrata Reseller Connection for Tootbus and securely share its API key. Tootbus then connects and maps your products in its own Ventrata account.

In the Ventrata Dashboard, go to Connections > Connections, press + New Connection and search for Ventrata Reseller Connection.
Select Tootbus as the reseller. If needed, allow or disallow destinations and products on the connection, then press Create Connection.
Press the eye icon to reveal the API key, copy it and securely share it with your contact at Tootbus.
Tootbus adds you as an operator with Ventrata (Operator Backend) as the backend, then connects and maps each product. Ask them to make a test booking, and check that it appears in your bookings table.

📗 TIP

For every step with screenshots, see Ventrata: Reseller Connection. Tootbus follows Ventrata: Operator Backend.

Managing the Tootbus Connection

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

Connection Features Detailed

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

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

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

Product Mapping	✅	Tootbus maps your products to its own in its Ventrata account. On each backend-connected product, Tootbus picks the matching product, option and units from your account on the product's Mappings tab. Products that aren't mapped correctly are highlighted in red, and bookings for them fail. See Ventrata: Operator Backend.
Content Sync	❌	Tootbus doesn't read your product content from Ventrata. Tootbus uses the descriptions, images and other content set up on its own side, so update your content with Tootbus directly.
Availability Sync	✅	Tootbus checks your live availability in Ventrata. Ventrata doesn't push availability changes to Tootbus. This works as follows: Availability Check (`POST /availability`) – Tootbus 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 Tootbus 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 Tootbus can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Tootbus: Availability Check: Tootbus checks your products throughout the day, usually starting 28 days ahead and covering 7 days per request, looks up to about a year ahead and re-checks the same product and dates about every 40 minutes. Availability Calendar: Tootbus checks your products throughout the day, usually starting today and covering a single day per request, looks up to about 6 months ahead and re-checks the same product and dates about every 2 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, Tootbus shows it after its next check. For dates it checks regularly, that's within about 40 minutes. Dates further ahead are usually checked less often.
Pricing Sync	✅	Your prices come back with every availability check, once Tootbus asks for them with the octo/pricing capability. This works as follows: Typically with Tootbus: 📗 TIP – If prices on Tootbus look wrong, check the Tootbus reseller's pricing in Ventrata first: that's what Tootbus reads. Tootbus can take your prices with Backend Pricing on its product, or set its own prices in its account.
Promotions Sync	❌	Your Ventrata promotions don't apply on Tootbus. Prices on Tootbus don't include promotions you create in Ventrata. Set up any promotions with Tootbus directly.
Bookings Sync	✅	Bookings and cancellations made on Tootbus 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 Tootbus, Tootbus 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, Tootbus confirms the hold, with its own booking reference and the customer's contact details. 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. Tootbus gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Tootbus 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 Tootbus, Tootbus 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 Tootbus has to contact you. Change: Tootbus doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Tootbus: Tootbus doesn't set a hold time, so the default hold time applies. A typical Tootbus 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. Tootbus also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) about every 30 minutes, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Tootbus to Ventrata. If you cancel, change or rebook a booking from Tootbus in Ventrata, for example in the Dashboard, Tootbus isn't notified. Contact Tootbus so the booking is cancelled or changed on their side too, or ask the customer to cancel through Tootbus.
Pickups/Dropoff Sync	❌	Tootbus doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Tootbus how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Tootbus doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Tootbus how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Tootbus. Customers can only book your main products and options on Tootbus. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Tootbus. Ventrata doesn't notify Tootbus when a ticket is scanned or redeemed. Tootbus only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Tootbus pass holders can't be scanned at your entrance without a booking. Customers from Tootbus need a booking made through Tootbus before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Tootbus. Gift cards bought in Ventrata can't be used on Tootbus, and Tootbus can't sell Ventrata gift cards.

✅ supported · ❌ not supported

Good to know: limits and details of the Tootbus connection

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

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

RATP Development SA

9 Rue Brahms

75012 Paris, France

tootbus.com

Ventrata Partner ID: b3f1d7b2-1cca-481a-af23-5c56d6103277

Ventrata Ltd

55 Baker Street

London, W1U 7EU, United Kingdom

ventrata.com

Ventrata Partner ID: a6a2a406-088a-4466-b87c-7fcc17770b71

Tootbus: Reseller Connection