Hellotickets is an online travel agency (OTA) selling attraction admissions, guided tours and day trips alongside concerts, Broadway and West End theater and live sport, a catalog weighted to city-break entertainment, through localized sites in more than 25 countries. For operators, it brings demand concentrated in the United States and Europe, with volume centered on New York, Rome, Paris, London, Madrid and Barcelona, from travelers who pair show and event tickets with sightseeing on the same trip.

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

To learn more about partnering with Hellotickets, visit hellotickets.com.

📒 NOTE

Hellotickets connects to Ventrata through Globick, a channel manager that runs the integration on its behalf. As it isn't a direct connection, some functionality or content may be limited for reasons outside Ventrata's control.

Primary website	hellotickets.com
Tags	OTA · Tours & Activities OTA · Event & Festival Ticketing
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Shows and live events paired with city sightseeing
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	Globick (using Ventrata's OCTO API)

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

Availability Sync – Hellotickets checks your live availability in Ventrata.
Pricing Sync – Hellotickets gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Hellotickets are created in Ventrata instantly, and customers get Ventrata tickets.
Pickups/Dropoff Sync – pickup and drop-off details are synced between Ventrata and Hellotickets.

Creating the Hellotickets Connection

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

Before you begin:

You must have a commercial agreement with Hellotickets for them to sell your products. To inquire about partnering with them, contact them via hellotickets.com.
You must have Hellotickets 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 Hellotickets (powered by Globick) from the list of partners.
Select Hellotickets 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 Hellotickets 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 Hellotickets

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Hellotickets connection

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

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

HELLO TICKET, S.L.

Paseo de las Delicias 110, 7B

28045 Madrid, Spain

hellotickets.com

Ventrata Partner ID: bc9cf3de-714a-4d30-a84e-7e0439e683f8

Globick

Calle Numancia, 73, 5C

08029 Barcelona, Spain

globick.com

Ventrata Partner ID: 0ed2e173-4b56-4ab7-9050-2b8cbe55cab9

Hellotickets: Reseller Connection