Tickete is an online booking platform for attractions, events, adventures, wellness activities and stays, listing venues such as the Louvre, Legoland Dubai and Wild Wadi across around 100 cities, with inventory weighted toward London, New York and Dubai. For operators, it brings travelers who buy close to the visit date, drawn by last-minute discounts and mobile admission, with attraction entry and entertainment tickets in major city destinations the core of the catalog.

Connecting Tickete to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Tickete, visit tickete.co.

Primary website	tickete.co
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Last-minute discounted attraction entry with mobile tickets
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	Tickete (using Ventrata's OCTO API)

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

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

Creating the Tickete Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Tickete connection

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

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

Tickete Travel L.L.C-FZ

1, Business Center, M Floor, The Meydan, Nad Al Sheba

Dubai, United Arab Emirates

tickete.co

Ventrata Partner ID: 6b5130fb-1367-473f-ab39-41bf4a487d90

Tickete: Reseller Connection