See Tickets is a ticketing agency owned by CTS Eventim, selling music, festival, theater, comedy, sport and exhibition tickets for thousands of clients across the UK, Benelux, Iberia, Germany and Switzerland. For operators, it brings event-driven domestic audiences, ticket buyers who return for concerts and festivals, with attractions and exhibitions sold alongside live events in each of its home markets.

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

To learn more about partnering with See Tickets, visit seetickets.com.

Primary website	seetickets.com
Tags	Event & Festival Ticketing
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Live event audiences buying concerts, festivals and exhibitions
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	See Tickets (using Ventrata's OCTO API)

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

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

Creating the See Tickets Connection

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

Before you begin:

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

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

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

📗 TIP

See 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 See Tickets Connection

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

Connection Features Detailed

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

In short: See Tickets pulls everything it needs from Ventrata. It reads your products, checks your availability (and your prices, when it asks for them), and sends bookings and cancellations. Ventrata doesn't push changes to See Tickets, so anything you change in Ventrata reaches See Tickets the next time it checks.

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the See Tickets connection

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

The Way Ahead Group Limited

The Hockley Pod, Fletcher Gate, Nottingham, England, NG1 2FS

United Kingdom

seetickets.com

Ventrata Partner ID: 06e291a4-daf1-426a-899b-3144c3cf53d9

See Tickets: Reseller Connection