TripWorks is a booking and reservation platform for tour, activity and attraction operators, used mostly in the United States across air and sea tours, sightseeing and city tours, adventure and outdoor activities, attractions and entertainment venues. It covers discovery, booking, payments, scheduling, check-in and analytics, with AI chat and call agents taking bookings around the clock and more than 50 distribution integrations.
Connecting TripWorks to Ventrata lets you resell products from operators that use TripWorks as their booking system. Ventrata reads their live availability and prices from TripWorks, and every booking you take is created directly in the operator's TripWorks account.
To learn more about TripWorks, visit tripworks.com.
📒 NOTE
Each API key connects you to one operator. If you resell more than one operator using TripWorks, create a separate operator in Ventrata for each one, with its own API key.
‼️ IMPORTANT
Mapping tells Ventrata which TripWorks product, option and units to request availability for and book. If backend-connected products are not properly mapped, bookings will fail. A red highlight across the product row indicates an incorrectly mapped product.
📗 TIP
Make a test booking after mapping and ask your operator to confirm it appears in TripWorks.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Pricing Sync · Bookings Sync |
Developed by | Ventrata (using TripWorks OCTO API) |
This operator connection (also called a backend) lets you resell products from operators that use TripWorks as their primary booking system, with every booking created directly in TripWorks. Features of this connection include:
Availability Sync – live availability comes from the operator's TripWorks account.
Pricing Sync – prices come from TripWorks, or you set prices in Ventrata.
Bookings Sync – bookings, updates and cancellations post from Ventrata to TripWorks, and TripWorks issues the tickets or vouchers.
Creating the TripWorks Connection
🔐 Required Role Permissions: See Operators, Modify Operators, See Products, Modify Products
Before you begin:
You must have a commercial agreement with the operator for their rates and terms.
You must have the OCTO API Key for the operator. See the steps below.
Each API key connects you to one operator only.
You must recreate the operator's products in Ventrata. See how to create products. The connection syncs availability, pricing and bookings, but doesn't create products in Ventrata.
Step 1: Configure the Operator in Ventrata
Your operator requests it from TripWorks for you. TripWorks issues a separate key for each reseller and operator relationship. Ask them to cc [email protected] so Ventrata can help if needed.
In the Ventrata Dashboard, go to Products → Operators and open the operator. If they don't exist yet, create them as an operator first.
In the Backend Partner section, select TripWorks and enter the OCTO API Key. Leave the endpoint as the default unless TripWorks or your operator tells you otherwise.
Keep the OCTO Endpoint pre-filled unless TripWorks or your operator instructs otherwise.
Enter the operator's name (for example HeliNY) when creating the operator.
Press Update Operator.
📒 NOTE – Each OCTO API Key connects you to one operator. Set up each TripWorks operator separately.
Step 2: Connect Each Product
Open the operator's product in Products → Products and edit it. Check that Operator is set to this operator.
Tick Backend Connected. Tick Backend Availability to use availability from TripWorks, and Backend Pricing to use prices from TripWorks.
Press Update Product.
📒 NOTE
TripWorks sends both retail and net prices. With Backend Pricing ticked, Ventrata records the retail price as your selling price and the net price as your cost price, whatever cost percentage is set on the operator.
In the Operator & Backend section of the product, assign the TripWorks operator, check Backend Connected and keep Backend Availability checked to pull live availability.
Optionally check Backend Pricing to pull pricing from TripWorks. If left unchecked, the product uses the pricing set in Ventrata but still posts bookings to TripWorks.
Repeat for each product you resell.
Mapping Products to TripWorks
‼️ IMPORTANT
Mapping tells Ventrata which TripWorks product, option and units to check availability for and book. If a backend-connected product isn't mapped correctly, its bookings fail. A red highlight across the product row shows an incorrectly mapped product.
In the Ventrata Dashboard, go to Products → Products and open the product.
Open the Mappings tab. It appears once the product is set to Backend Connected.
For each Ventrata option and unit, select the matching TripWorks product, option and units from the dropdowns, which Ventrata loads from TripWorks. Don't leave any field empty.
Press Save Changes.
📒 NOTE
Products appear under their TripWorks experience name. Map each Ventrata unit (for example Adult, Child) to the matching TripWorks unit.
📗 TIP
Make a test booking after mapping, and ask the operator to confirm it arrived in their TripWorks account.
Managing the TripWorks Connection
Update the mapping when the operator changes products, options or units in TripWorks.
Replace the key on the operator if TripWorks or the operator issues a new one.
Switch Backend Availability or Backend Pricing off on a product to use Ventrata's own availability or prices instead. Bookings still post to TripWorks.
Connection Features Detailed
This section is for anyone who wants to know exactly how the TripWorks connection works. Here the direction is the opposite of a reseller connection: Ventrata calls TripWorks, using TripWorks OCTO API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks TripWorks for availability and prices whenever someone looks at a backend-connected product, and creates every booking in the operator's TripWorks account. TripWorks doesn't send changes back to Ventrata.
Timings are typical for TripWorks and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's TripWorks product in the Ventrata Dashboard. This works as follows:
What this means for you: if something is missing from the dropdown, the operator hasn't made it available to you in TripWorks. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from TripWorks. Ventrata doesn't import product content from TripWorks. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in TripWorks. This works as follows:
What this means for you: customers book against the operator's live TripWorks availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ✅ |
With Backend Pricing on, Ventrata takes prices from TripWorks. This works as follows:
TripWorks sends both retail and net prices. With Backend Pricing ticked, Ventrata records the retail price as your selling price and the net price as your cost price, whatever cost percentage is set on the operator. |
Promotions Sync | ❌ |
Promotions aren't sent to TripWorks. Promotions aren't sent to TripWorks. Your Ventrata promotions still apply to the price your customer pays in Ventrata. |
Bookings Sync | ✅ |
Bookings made in Ventrata for a backend-connected product are created in the operator's TripWorks account. This works as follows:
Availability is reserved in TripWorks when a product is added to the cart and confirmed after payment, along with the customer's contact details. Booking updates (date, time, quantities) and cancellations made in Ventrata are sent to TripWorks automatically.
‼️ IMPORTANT – Bookings sync one way, from Ventrata to TripWorks. If the operator changes or cancels a booking in TripWorks, Ventrata isn't notified. Ask the operator to tell you about any changes they make. |
Pickups/Dropoff Sync | ❌ |
Pickup and drop-off details aren't passed to TripWorks. Pickup and drop-off details aren't passed to TripWorks. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to TripWorks. Answers to your booking questions aren't passed to TripWorks. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in TripWorks. Extras and add-ons aren't booked in TripWorks. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in TripWorks aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in TripWorks aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with TripWorks. Pass walk-up scanning isn't available with TripWorks. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to TripWorks. Ventrata gift cards aren't passed to TripWorks. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the TripWorks connection
Good to know: limits and details of the TripWorks connection
Live availability: availability comes from TripWorks as people browse.
One-way bookings: changes the operator makes in TripWorks don't reach Ventrata.
Vouchers/tickets: TripWorks returns a QR code for the booking and for each ticket, and Ventrata issues these to your customer. The QR code links to the operator's TripWorks customer portal and is what the operator scans on arrival.
FAQs
I get an error when I save the operator's backend configuration.
I get an error when I save the operator's backend configuration.
The OCTO API Key or endpoint is most likely incorrect. Check them with your operator. If the issue persists, contact our Technical Support.
There's no Backend Connected box in the product settings.
There's no Backend Connected box in the product settings.
The operator set on the product most likely doesn't have a backend configured. Check the operator's Backend Partner settings and try again. If the issue persists, contact our Technical Support.
The product, option or unit I want to map isn't in the dropdown.
The product, option or unit I want to map isn't in the dropdown.
The dropdowns list what the operator has made available to you in TripWorks. Ask the operator. If the issue persists, contact our Technical Support.
Bookings fail for a backend-connected product.
Bookings fail for a backend-connected product.
Check the product's mapping first: every option and unit must be mapped. Then check that the slot is still available in TripWorks. If the issue persists, contact our Technical Support.
Error when saving the operator's backend configuration.
Error when saving the operator's backend configuration.
The OCTO API Key is likely incorrect or not yet active. Double-check it with your operator. If the issue persists, contact [email protected].
The product/option/unit I want to map is not in the dropdown.
The product/option/unit I want to map is not in the dropdown.
The dropdown shows only the products, options and units the operator has made available to you in TripWorks. Ask your operator to check the allocation on their side.
Useful Resources
📚 More about Ventrata connections
Partner Information
TripWorks, Inc.
1 High Street Ct.
Morristown, NJ 07960, United States
Ventrata Partner ID: 01a159ec-f15a-73fd-96c5-917ef887269b