TripShock is a United States activities marketplace specializing in the Gulf Coast, listing more than 1,000 experiences across Destin, Fort Walton Beach, Pensacola Beach, Panama City Beach, Orange Beach, Gulf Shores, Myrtle Beach, New Orleans and Key West. For operators, it brings drive-market American families and couples on beach vacations, plus residents booking for visiting guests, who buy dolphin-watch and evening cruises, fishing charters, parasailing, pontoon rentals and other watersports.

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

To learn more about partnering with TripShock, visit tripshock.com.

Primary website	tripshock.com
Tags	Adventure & Outdoor
Destination markets	🇺🇸 US
Source markets	🇺🇸 US
Specialties	Gulf Coast beach cruises, fishing and watersports
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	TripShock (using Ventrata's OCTO API)

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

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

Creating the TripShock Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the TripShock connection

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

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

TS Tours, LLC

3999 Commons Dr. W., Unit N, Destin, FL 32541

United States

tripshock.com

Ventrata Partner ID: 9da04b1b-2141-4b79-b321-dd6db791618b

TripShock: Reseller Connection