Turbopass is a digital multi-attraction city pass bundling museum and landmark entry, local experiences and in some cities public transport into one QR-code ticket, sold for 14 destinations: Rome, Paris, London, Barcelona, Madrid, Venice, Florence, Naples, Athens, Munich, Hamburg, York, Stratford-upon-Avon and Dubai. For operators, it brings prepaid city-break travelers, more than 700,000 served, who plan multi-attraction itineraries before arrival, with savings of up to 45 percent against individual tickets as the draw. Turbopass uses Open Pass as their primary ticketing system.

Connecting Turbopass to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically. Turbopass runs on Open Pass, and receives your products through its certified integration with Ventrata's OCTO API.

To learn more about partnering with Turbopass, visit turbopass.com.

Primary website	turbopass.com
Tags	OTA · Tours & Activities OTA · Multi-Attraction Pass
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Digital multi-attraction city passes
Connection features	Availability Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	Open Pass (using Ventrata's OCTO API)

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

Availability Sync – Turbopass checks your live availability in Ventrata.
Bookings Sync – bookings, updates and cancellations from Turbopass are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Turbopass Connection

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

Before you begin:

You must have a commercial agreement with Turbopass for them to sell your products. To inquire about partnering with them, contact them via turbopass.com.
You must have Turbopass 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 Turbopass (powered by Open Pass) from the list of partners.
Select Turbopass 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 Turbopass 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 Turbopass

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

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

📗 TIP

Turbopass 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 Turbopass Connection

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

Connection Features Detailed

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

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

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

Product Mapping	❌	You can't map products from Ventrata. Turbopass maps them on its side, through your account manager or Turbopass's portal. This works as follows: Get Products (`GET /products`) – when Turbopass 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}`) – Turbopass re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Turbopass's side – Turbopass links each Ventrata option and unit to its own listing and ticket types. Your Turbopass account manager does this for you, or you do it in Turbopass's own portal if Turbopass offers one. You only share the connection's API key. Typically with Turbopass: Turbopass reads your full product list about every 5 hours. It re-reads each product about every 8 hours. What this means for you: Turbopass can only sell what it has mapped. When you add a product, option or unit in Ventrata, Turbopass may see it on its next refresh, but it won't sell it until it's mapped. So tell your Turbopass account manager whenever you add one.
Content Sync	❌	Turbopass doesn't read your product content from Ventrata. Turbopass uses the descriptions, images and other content set up on its own side, so update your content with Turbopass directly.
Availability Sync	✅	Turbopass checks your live availability in Ventrata. Ventrata doesn't push availability changes to Turbopass. This works as follows: Availability Check (`POST /availability`) – Turbopass 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 Turbopass 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 Turbopass can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Turbopass: Availability Check: Turbopass checks your products throughout the day, usually starting 2 days ahead and covering a single day per request, looks up to about 2 months ahead and re-checks the same product and dates about every 12 hours. Availability Calendar: Turbopass checks each product about once a day. Checks are busiest between 07:00 and 13:00 UTC, which suggests most checks are live, as customers browse Turbopass. What this means for you: when you close a date, change capacity or sell out in Ventrata, Turbopass shows it after its next check. For dates it checks regularly, that's within about 12 hours. Dates further ahead are usually checked less often.
Pricing Sync	❌	Turbopass doesn't get your prices from Ventrata. Prices on Turbopass are managed on Turbopass's side, so keep them up to date with Turbopass directly.
Promotions Sync	❌	Your Ventrata promotions don't apply on Turbopass. Prices on Turbopass don't include promotions you create in Ventrata. Set up any promotions with Turbopass directly.
Bookings Sync	✅	Bookings and cancellations made on Turbopass 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 Turbopass, Turbopass 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, Turbopass 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. Turbopass gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Turbopass 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 Turbopass, Turbopass 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 Turbopass has to contact you. Change: Turbopass doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Turbopass: Turbopass holds places for about 20 minutes while the customer pays (`expirationMinutes`). A typical Turbopass booking is for about 3 people. Turbopass also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) about once a day, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Turbopass to Ventrata. If you cancel, change or rebook a booking from Turbopass in Ventrata, for example in the Dashboard, Turbopass isn't notified. Contact Turbopass so the booking is cancelled or changed on their side too, or ask the customer to cancel through Turbopass.
Pickups/Dropoff Sync	❌	Turbopass doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Turbopass how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	✅ / ❌	Turbopass sends answers to your booking questions with its bookings. This works as follows: `octo/questions` capability – Turbopass reads the questions set on your products and sends the customer's answers with the booking, where you see them in Ventrata. Typically with Turbopass: Turbopass sends answers to your booking questions.
Extras Sync	❌	Extras and add-ons can't be booked through Turbopass. Customers can only book your main products and options on Turbopass. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Turbopass. Ventrata doesn't notify Turbopass when a ticket is scanned or redeemed. Turbopass only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Turbopass pass holders can't be scanned at your entrance without a booking. Customers from Turbopass need a booking made through Turbopass before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Turbopass. Gift cards bought in Ventrata can't be used on Turbopass, and Turbopass can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Turbopass connection

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

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

Turbopass GmbH

Niederwall 53, 33602 Bielefeld

Germany

turbopass.com

Ventrata Partner ID: c78de6f3-0617-4245-842d-df7ba331727c

TWG Systems Limited

Avon View House, Station Road, Fladbury, Pershore, England, WR10 2QW

United Kingdom

openpass.co.uk

Ventrata Partner ID: ad24532f-4770-428f-802c-9f7e6b17e038

Turbopass: Reseller Connection