Tiqets is an online travel agency (OTA) for museums and attractions, part of Expedia Group, selling instant mobile tickets in 18 languages with 20 payment methods. For operators, it brings global and local visitors to cultural venues, with distribution through around 4,600 partners and Tiqets handling traveler customer service 24/7.

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

To learn more about partnering with Tiqets, visit tiqets.com.

Primary website	tiqets.com
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Cultural tickets and museums
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Custom Questions Sync
Ventrata Booked GMV (last 12 months)	US$10M+
Ventrata Booked Suppliers (last 12 months)	100+
Developed by	Expedia (using Ventrata's OCTO API)

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

Availability Sync – Tiqets checks your live availability in Ventrata.
Pricing Sync – Tiqets gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Tiqets are created in Ventrata instantly, and customers get Ventrata tickets.
Custom Questions Sync – custom booking questions are synced between Tiqets and Ventrata.

Creating the Tiqets Connection

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

Before you begin:

You must have a commercial agreement with Tiqets for them to sell your products. To inquire about partnering with them, contact them via tiqets.com. To start one, see tiqets.com/venues to get started.
You must have Tiqets 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 Tiqets (powered by Expedia) from the list of partners.
Select Tiqets 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 Tiqets 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 Tiqets

Make a note of the Connection ID (also called Supplier ID) shown on the Tiqets connection in Ventrata. Then choose one of these options:

Ask Tiqets to map your products. Email the Connection ID to your Tiqets contact or to [email protected] and ask them to map your products.
Map your products yourself in your Tiqets Supplier account, using the steps below for each of your Tiqets products.

Select Ventrata as your API booking platform.
Enter the Connection ID from the connection in the Supplier ID field.
Click Save & Continue. A validation check may run to make sure the ID is correct and that Tiqets has access to your products.
Continue by providing the rest of your product information in the following steps.
Add your desired ticket types.
Click the Map API button at the bottom of the ticket type. This lets you select the matching product and its tickets from Ventrata.
Once you have mapped all your tickets, click Save & Continue to finish onboarding the new product.
Repeat these steps for any other products or ticket types you want to offer.

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Tiqets connection

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

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.

Supplier ID is not correct.

Use the Connection ID from Ventrata as the Supplier ID in the Tiqets system.

Useful Resources

Become a Tiqets supplier

📚 More about Ventrata connections

Partner Information

Tiqets International B.V.

James Wattstraat 77

1097 DL Amsterdam, Netherlands

tiqets.com

Ventrata Partner ID: 87570ace-cff0-4b80-a782-d0f77f3a0c25

Tiqets Inc.

228 East 45th Street, Suite 9E

New York, NY 10017, USA

Expedia Group, Inc.

1111 Expedia Group Way W.

Seattle, WA 98119, United States

expedia.com/activities

Ventrata Partner ID: 31f14275-7784-4dde-9c05-3bc922061c56

Tiqets: Reseller Connection