Zürich Tourism is the official destination marketing organization for Zürich, promoting the city and surrounding region to leisure, business and event travelers, and selling the Zürich Card, guided walks, excursions and event tickets through its website and a staffed visitor information desk at Zürich main station. For operators, it brings city visitors who buy before the trip as well as on arrival at the station desk, plus travel trade and congress business handled by its business section. Zürich Tourism uses Holidu Smart Destination as their connectivity provider.

Connecting Zürich Tourism to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically. Zürich Tourism runs on Holidu Smart Destination, and receives your products through its certified integration with Ventrata's OCTO API.

To learn more about partnering with Zürich Tourism, visit zuerich.com.

Primary website	zuerich.com
Tags	Destination Organization (DMO)
Destination markets	🇨🇭 Switzerland
Source markets	🌎 Global
Specialties	Official Zürich Card, walks and excursions at the station desk
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Holidu Smart Destination (TOMAS) (using Ventrata's OCTO API)

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

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

Creating the Zürich Tourism Connection

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

Before you begin:

You must have a commercial agreement with Zürich Tourism for them to sell your products. To inquire about partnering with them, contact them via zuerich.com.
You must have Zürich Tourism 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 Zürich Tourism (powered by Holidu Smart Destination) from the list of partners.
Select Zürich Tourism 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 Zürich Tourism 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 Zürich Tourism

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

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

📗 TIP

Zürich Tourism 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 Zürich Tourism Connection

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

Connection Features Detailed

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Zürich Tourism connection

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

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

Zürich Tourismus

Gessnerallee 3, 8001 Zürich

Switzerland

zuerich.com

Ventrata Partner ID: 6c400e45-18a2-4fcf-b311-87b6a77a86ad

Holidu Smart Destination GmbH

Riesstraße 24, 80992 München

Germany

holidu.de/hsd

Ventrata Partner ID: 73d55f64-f964-494c-ae18-5efa566220ac

Zürich Tourism: Reseller Connection