München Tourismus is the official tourism organization of the City of Munich, selling guided and themed city tours, brewery and market experiences, hop-on hop-off routes, hotel stays and day excursions to Bavarian castles, the Zugspitze and Salzburg through its official portal, and issuing the München Card and City Pass. For operators, it brings visitors planning a Munich trip who book tours and excursions on the destination's own site alongside accommodation.

Connecting München Tourismus to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically. München Tourismus runs on Holidu Smart Destination, and receives your products through its certified integration with Ventrata's OCTO API.

To learn more about partnering with München Tourismus, visit muenchen.travel.

📒 NOTE

This connection is available only to specific client accounts. If you're interested in using it, contact our Technical Support or your Ventrata Customer Success Manager.

Primary website	muenchen.travel
Tags	Destination Organization (DMO) · Multi-Attraction Pass
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Official Munich tours, Bavarian excursions and city cards
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 München Tourismus without managing availability, pricing and bookings by hand. Features of this connection include:

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

Creating the München Tourismus Connection

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

Before you begin:

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

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

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

📗 TIP

München Tourismus 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 München Tourismus Connection

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

Connection Features Detailed

This section is for anyone who wants to know exactly how the München Tourismus connection works: which Ventrata OCTO API calls München Tourismus 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: München Tourismus 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 München Tourismus, so anything you change in Ventrata reaches München Tourismus the next time it checks.

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

✅ supported · ❌ not supported

Good to know: limits and details of the München Tourismus connection

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

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

Landeshauptstadt München, Referat für Arbeit und Wirtschaft

80331 München, Germany

muenchen.travel

Ventrata Partner ID: 1c3df1eb-8abe-4b0e-9937-ed02ecb15750

Holidu Smart Destination GmbH

Riesstraße 24

80992 München, Germany

holidu.de/hsd

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

München Tourismus: Reseller Connection