Vienna E-Pass is a digital sightseeing pass for Vienna giving entry to dozens of palaces, museums, concerts and tours, including Schönbrunn Palace and the Upper Belvedere, sold in one- to four-day durations and delivered by email as a QR code. For operators, it brings short-break city visitors who commit to a bundle of attractions before arriving, buying online in ten languages including German, Italian, Spanish and French.

Connecting Vienna E-Pass to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Vienna E-Pass, visit viennaepass.com.

Primary website	viennaepass.com
Tags	Multi-Attraction Pass
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Bundled Vienna palaces, museums and concerts
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Vienna E-Pass (using Ventrata's OCTO API)

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

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

Creating the Vienna E-Pass Connection

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

Before you begin:

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

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

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

📗 TIP

Vienna E-Pass 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 Vienna E-Pass Connection

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

Connection Features Detailed

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

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

Timings are typical for Vienna E-Pass and rounded, and they can change if Vienna E-Pass changes how it syncs.

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Vienna E-Pass connection

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

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

GoVisit Digital GmbH

Seitenstettengasse 5/37, 1010 Vienna

Austria

viennaepass.com

Ventrata Partner ID: 83583970-a11b-4b6b-a663-64832cc9e00e

Vienna E-Pass: Reseller Connection