Tripster is a destination-specialist online travel agency (OTA) founded in 2001, selling discounted attraction and theme park tickets, shows, tours and lodging packages across 72 destinations in the United States, Canada and Hawaii. It also runs white-label booking services for destination marketing organizations, resellers and affiliate sites. For operators, it brings American and Canadian leisure families planning a destination trip in advance, who bundle attraction tickets with hotels or vacation homes, with theme parks, shows and aquariums the core of the catalog.

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

To learn more about partnering with Tripster, visit tripster.com.

Primary website	tripster.com
Tags	Multi-day & Packaged Tours
Destination markets	🇨🇦 Canada · 🇺🇸 US
Source markets	🇨🇦 Canada · 🇺🇸 US
Specialties	Theme park and attraction tickets bundled with lodging
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	Tripster (using Ventrata's OCTO API)

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

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

Creating the Tripster Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Tripster connection

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

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

Reserve Direct, Inc.

523 State Highway 248, Suite B

Branson, Missouri 65616, USA

tripster.com

Ventrata Partner ID: 3ffa2af0-4703-42c2-be21-cd6a431b3021

Tripster: Reseller Connection