Skip to main content

TourPass: Reseller Connection

Connect TourPass to Ventrata to sync availability and prices and receive bookings instantly. A mobile pass for Charleston, Savannah and Saint Augustine.

TourPass logo

 

TourPass is a mobile multi-attraction pass for Charleston, Savannah and Saint Augustine, bundling hand-picked tours and attractions in three southeastern US heritage-tourism destinations into one digital pass. For operators, it brings prepaid American leisure travelers, more than 30,000 served, who stack several small operators into one trip across historic sites, tours and museums, with savings of up to 40 percent against retail as the draw.

 

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

 

To learn more about partnering with TourPass, visit tourpass.com.

 

Primary website

Tags

Multi-Attraction Pass

Destination markets

🇺🇸 US

Source markets

🇺🇸 US

Specialties

Multi-attraction pass for Southeastern US heritage destinations

Connection features

Availability Sync · Pricing Sync · Bookings Sync

Ventrata Booked GMV (last 12 months)

US$100k+

Developed by

TourPass (using Ventrata's OCTO API)

 

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

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

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

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

 

Creating the TourPass Connection

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

Before you begin:

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

  • You must have TourPass 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 TourPass from the list of partners.

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

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

 

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

 

 

📗 TIP

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

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

  • Rename the connection to tell several TourPass connections apart.

 

Connection Features Detailed

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

 

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

 

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

 

Product Mapping

❌

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

This works as follows:

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

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

 

Typically with TourPass:

  • It re-reads each product every few minutes.

 

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

Content Sync

✅ / ❌

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

This works as follows:

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

 

Typically with TourPass:

  • TourPass requests octo/content.

Availability Sync

✅

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

This works as follows:

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

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

 

Typically with TourPass:

  • Availability Check: TourPass checks your products throughout the day, usually starting today and covering a single day per request, looks up to about 3 months ahead and re-checks the same product and dates about every hour.

  • 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, TourPass shows it after its next check. For dates it checks regularly, that's within an hour. Dates further ahead are usually checked less often.

Pricing Sync

✅

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

This works as follows:

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

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

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

  • TourPass 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 TourPass to map your products, ask them to enable pricing (octo/pricing) as well, or switch it on yourself if you map in TourPass's portal. Otherwise it may be off, and TourPass won't receive your Ventrata prices.

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

Promotions Sync

✅ / ❌

Your Ventrata promotions can apply to TourPass prices and bookings.

This works as follows:

  • octo/offers capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and TourPass 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 TourPass:

  • TourPass requests octo/offers.

Bookings Sync

✅

Bookings and cancellations made on TourPass 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 TourPass, TourPass 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, TourPass 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. TourPass gives these to the customer, who shows them at your entrance like any Ventrata ticket.

  3. Expire: if the customer doesn't finish paying, TourPass 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 TourPass, TourPass 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 TourPass has to contact you.

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

 

Typically with TourPass:

  • TourPass doesn't set a hold time, so the default hold time applies.

  • A typical TourPass booking is for about 2 people.

  • TourPass also checks the bookings it has made, with Get Booking (GET /bookings/{uuid}) every few minutes, for example to reconcile its records.

 

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

Pickups/Dropoff Sync

❌

TourPass doesn't send pickup or drop-off details with its bookings.

If your products include pickups, check with TourPass how it collects pickup details, or arrange them with the customer.

Custom Questions Sync

❌

TourPass doesn't send answers to your booking questions.

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

Extras Sync

❌

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

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

Redemption Sync

❌

Redemptions aren't reported to TourPass.

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

Pass Walkup Scanning Sync

❌

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

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

Gift Card Sync

❌

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

 

Good to know: limits and details of the TourPass connection

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

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

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

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

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

Traveler Communications Group, LLC

557 East Bay Street, #22677

Charleston, SC 29401, United States

 

Ventrata Partner ID: 4ed1e23e-90c3-45ca-8357-73a71f3d0398

Did this answer your question?