Headout is a managed online marketplace (OTA) for tours, activities and attractions, selling around 10,000 experiences in 196+ countries through its app and website. For operators, it brings a fast-growing base of 57 million travelers, half acquired in the last four years, concentrated in major city destinations such as London, Paris, Rome, Dubai and New York.

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

To learn more about partnering with Headout, visit headout.com.

Primary website	headout.com
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Tours and attraction tickets in international destinations
Connection features	Availability Sync · Pricing Sync · Promotions Sync · Bookings Sync · Pickups/Dropoff Sync · Custom Questions Sync
Ventrata Booked GMV (last 12 months)	US$10M+
Ventrata Booked Suppliers (last 12 months)	25+
Developed by	Headout (using Ventrata's OCTO API)

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

Availability Sync – Headout checks your live availability in Ventrata.
Pricing Sync – Headout gets your prices from your reseller pricing in Ventrata.
Promotions Sync – your Ventrata promotions apply on Headout.
Bookings Sync – bookings, updates and cancellations from Headout are created in Ventrata instantly, and customers get Ventrata tickets.
Pickups/Dropoff Sync – pickup and drop-off details are synced between Headout and Ventrata.
Custom Questions Sync – custom booking questions are synced between Headout and Ventrata.

Creating the Headout Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Headout connection

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

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.

Useful Resources

Headout partner hub

📚 More about Ventrata connections

Partner Information

Headout Inc.

82 Nassau St #60351

New York, NY 10038, United States

headout.com

Ventrata Partner ID: 330e2bda-47c8-414d-ac8b-8f031cbaf085

Headout: Reseller Connection