Volatour is a New York-headquartered tour operator with more than two decades in the market, selling sightseeing tours, excursions, attraction tickets, cruises and transfers in New York City, Los Angeles and Miami, with further US cities planned. For operators, it brings international visitors who book direct in their own languages, buying city sightseeing, attraction admissions and day excursions for US city breaks.

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

To learn more about partnering with Volatour, visit www.volatour.com.

Primary website	www.volatour.com
Tags	Receptive & Inbound Operator
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	City sightseeing and day excursions booked in visitors' own languages
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	Volatour (using Ventrata's OCTO API)

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

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

Creating the Volatour Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the Volatour connection

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

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

VOLATOUR, Inc.

33 West 46th Street

New York, NY 10036, United States

volatour.com

Ventrata Partner ID: 33abcbb5-ae66-427e-a3a3-880fee463456

Volatour: Reseller Connection