My Hotel Tickets is a closed hotel distribution platform from Amsterdam Visitor Marketing through which hotels offer guests discounted admission to attractions, experiences, transport and activities, reached through hotel-issued QR codes that keep discounted rates off public sites. For operators, it brings in-destination visitors already staying at partner hotels, buying on arrival or during the stay, with the discount hidden from open channels.

Connecting My Hotel Tickets to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with My Hotel Tickets, visit amsterdamvisitormarketing.com/my-hotel-tickets-app.

Primary website	amsterdamvisitormarketing.com/my-hotel-tickets-app
Tags	Hotel & Concierge Channel · Offline & Retail Channel
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Hotel guests buying with closed, hotel-only discounts
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	My Hotel Tickets (using Ventrata's OCTO API)

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

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

Creating the My Hotel Tickets Connection

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

Before you begin:

You must have a commercial agreement with My Hotel Tickets for them to sell your products. To inquire about partnering with them, contact them via amsterdamvisitormarketing.com/my-hotel-tickets-app.
You must have My Hotel Tickets 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 My Hotel Tickets from the list of partners.
Select My Hotel Tickets 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 My Hotel Tickets 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 My Hotel Tickets

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

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

📗 TIP

My Hotel Tickets 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 My Hotel Tickets Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the My Hotel Tickets connection

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

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

My Hotel Tickets

Frans Halsstraat 39, 1072 BL Amsterdam

Netherlands

amsterdamvisitormarketing.com/my-hotel-tickets-app

Ventrata Partner ID: d7c0b35f-2c3f-4cf7-bd1a-ee0421ad4693

My Hotel Tickets: Reseller Connection