Tripper is a Dutch deals marketplace for days out, selling discounted tickets to amusement parks, zoos, museums, restaurants, wellness, workshops and short breaks, trading in Dutch, German and English. For operators, it brings domestic families, friend groups and colleagues booking price-led outings, with German- and English-speaking buyers added through the cross-border catalog.

Connecting Tripper to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Tripper, visit tripper.nl.

Primary website	tripper.nl
Tags	Family Experiences · Deals & Corporate Benefits
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Discounted days out for families and groups
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Tripper (using Ventrata's OCTO API)

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

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

Creating the Tripper Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Tripper connection

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

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

Tripper B.V.

Zijldijk 24B, 2352 AB Leiderdorp

Netherlands

tripper.nl

Ventrata Partner ID: aa147484-7816-4159-bc45-02938eb63119

Tripper: Reseller Connection