Skip to main content

Ticmate: Reseller Connection

Connect Ticmate to Ventrata to sync availability and prices and receive bookings instantly. Nordic and European travelers booking in their own language.

Ticmate logo

 

Ticmate is a ticket agent founded in Stockholm in 2007, selling attraction admissions, theater, musicals, sports and events through localized country sites in more than a dozen languages, with offices in Stockholm, Copenhagen, Berlin and New York and direct contracts with venues. For operators, it brings Nordic and continental European travelers researching and booking in their own language before they travel, with theater, shows, sightseeing and attraction entry in major European and US cities the core of the catalog.

 

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

 

To learn more about partnering with Ticmate, visit ticmate.com.

 

Primary website

Tags

OTA · Tours & Activities OTA · Event & Festival Ticketing

Destination markets

🌎 Global

Source markets

🌎 Global

Specialties

Nordic and European travelers booking in their own language

Connection features

Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync

Ventrata Booked GMV (last 12 months)

US$100k+

Developed by

Ticmate (using Ventrata's OCTO API)

 

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

  • Availability Sync – Ticmate checks your live availability in Ventrata.

  • Pricing Sync – Ticmate gets your prices from your reseller pricing in Ventrata.

  • Bookings Sync – bookings, updates and cancellations from Ticmate are created in Ventrata instantly, and customers get Ventrata tickets.

  • Pickups/Dropoff Sync – Ticmate sends pickup and drop-off details with its bookings to Ventrata.

 

Creating the Ticmate Connection

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

Before you begin:

  • You must have a commercial agreement with Ticmate for them to sell your products. To inquire about partnering with them, contact them via ticmate.com.

  • You must have Ticmate 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.

 

  1. In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Ticmate from the list of partners.

  2. Select Ticmate 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.

  3. (Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Ticmate connections and would like to differentiate between them more easily in the future.

  4. 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 Ticmate

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

 

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

 

 

📗 TIP

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

  • Allow or disallow products: limit which destinations, products and options Ticmate can access. See how to allow or disallow products.

  • Rename the connection to tell several Ticmate connections apart.

 

Connection Features Detailed

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

 

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

 

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

 

Product Mapping

❌

You can't map products from Ventrata. Ticmate maps them on its side, through your account manager or Ticmate's portal.

This works as follows:

  • Get Products (GET /products) – when Ticmate 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}) – Ticmate re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

  • Mapping on Ticmate's side – Ticmate links each Ventrata option and unit to its own listing and ticket types. Your Ticmate account manager does this for you, or you do it in Ticmate's own portal if Ticmate offers one. You only share the connection's API key.

 

Typically with Ticmate:

  • Ticmate reads your full product list about every 4 hours.

 

What this means for you: Ticmate can only sell what it has mapped. When you add a product, option or unit in Ventrata, Ticmate may see it on its next refresh, but it won't sell it until it's mapped. So tell your Ticmate account manager whenever you add one.

Content Sync

✅ / ❌

Ticmate can read your product content, such as descriptions and images, from Ventrata.

This works as follows:

  • octo/content capability – when Ticmate 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 Ticmate on its next product refresh.

 

Typically with Ticmate:

  • Ticmate requests octo/content.

Availability Sync

✅

Ticmate checks your live availability in Ventrata. Ventrata doesn't push availability changes to Ticmate.

This works as follows:

  • Availability Check (POST /availability) – Ticmate 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 Ticmate needs to book that slot.

  • Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Ticmate can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

 

Typically with Ticmate:

  • Availability Check: Ticmate checks your products throughout the day, usually starting 23 days ahead and covering a single day per request, looks up to about 10 months ahead and re-checks the same product and dates about every 7 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, Ticmate shows it after its next check. For dates it checks regularly, that's within about 7 hours. Dates further ahead are usually checked less often.

Pricing Sync

✅

Your prices come back with every availability check, once Ticmate asks for them with the octo/pricing capability.

This works as follows:

  • octo/pricing capability – Ticmate 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 Ticmate, both from the reseller's pricing in Ventrata (retail and wholesale/commission).

  • Group prices – when Ticmate 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 Ticmate:

  • Ticmate requests octo/pricing on all of its availability checks, so it sells at your Ventrata prices.

  • Ticmate 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 Ticmate.

 

‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Ticmate to map your products, ask them to enable pricing (octo/pricing) as well, or switch it on yourself if you map in Ticmate's portal. Otherwise it may be off, and Ticmate won't receive your Ventrata prices.

📗 TIP – If prices on Ticmate look wrong, check the Ticmate reseller's pricing in Ventrata first: that's what Ticmate reads.

Promotions Sync

❌

Your Ventrata promotions don't apply on Ticmate.

Prices on Ticmate don't include promotions you create in Ventrata. Set up any promotions with Ticmate directly.

Bookings Sync

✅

Bookings and cancellations made on Ticmate are created in Ventrata instantly, and customers get Ventrata tickets.

This works as follows:

  1. Hold: Booking Reservation (POST /bookings) – when a customer starts checkout on Ticmate, Ticmate 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.

  2. Confirm: Booking Confirmation (POST /bookings/{uuid}/confirm) – once payment goes through, Ticmate 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. Ticmate gives these to the customer, who shows them at your entrance like any Ventrata ticket.

  3. Expire: if the customer doesn't finish paying, Ticmate never confirms, and the hold expires on its own and frees the places.

  4. Cancel: Booking Cancellation (POST /bookings/{uuid}/cancel) – when a customer cancels on Ticmate, Ticmate 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 Ticmate has to contact you.

  5. Change: Ticmate doesn't use Booking Update (PATCH /bookings/{uuid}), so a change most likely reaches Ventrata as a cancellation plus a new booking.

 

Typically with Ticmate:

  • Ticmate holds places for about 5 minutes while the customer pays (expirationMinutes).

  • A typical Ticmate booking is for about 4 people.

 

‼️ IMPORTANT – Bookings sync one way, from Ticmate to Ventrata. If you cancel, change or rebook a booking from Ticmate in Ventrata, for example in the Dashboard, Ticmate isn't notified. Contact Ticmate so the booking is cancelled or changed on their side too, or ask the customer to cancel through Ticmate.

Pickups/Dropoff Sync

✅

Ticmate sends pickup details with its bookings.

This works as follows:

  • octo/pickups capability – Ticmate 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 Ticmate:

  • Ticmate sends pickup details with its bookings.

Custom Questions Sync

❌

Ticmate doesn't send answers to your booking questions.

If you rely on booking questions, for example names or dietary needs, check with Ticmate how it collects that information.

Extras Sync

❌

Extras and add-ons can't be booked through Ticmate.

Customers can only book your main products and options on Ticmate. Sell extras separately, for example on arrival.

Redemption Sync

❌

Redemptions aren't reported to Ticmate.

Ventrata doesn't notify Ticmate when a ticket is scanned or redeemed. Ticmate only sees a redemption if it reads the booking back from Ventrata.

Pass Walkup Scanning Sync

❌

Ticmate pass holders can't be scanned at your entrance without a booking.

Customers from Ticmate need a booking made through Ticmate before they visit.

Gift Card Sync

❌

Ventrata gift cards can't be sold or redeemed through Ticmate.

Gift cards bought in Ventrata can't be used on Ticmate, and Ticmate can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

 

Good to know: limits and details of the Ticmate connection

  • Delays: availability and prices reach Ticmate only when it checks, so there's always a short delay after you change something in Ventrata.

  • Cancellation cutoff: Ticmate can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.

  • What Ticmate 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: Ticmate issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.

  • Test bookings: Ticmate 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 Ticmate.

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.

 

 

Partner Information

Ticmate AB

Krukmakargatan 50 1tr

117 26 Stockholm, Sweden

 

Ventrata Partner ID: 82e1a77e-25c0-4b80-b173-5776243cfe73

Did this answer your question?