Hero Travel is travel agency software for travel resellers, combining a marketplace of tours, activities, accommodation and transport with quoting, itinerary building, payments and instant ticketing in one back office, built in Australia and New Zealand and sold to travel agents in the United States. For operators, it brings agent-assisted demand: travel advisors packaging experiences into quoted itineraries for their clients, a longer-lead, higher-value booking than direct consumer search.

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

To learn more about partnering with Hero Travel, visit hero.travel.

Primary website	hero.travel
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Travel advisors building quoted itineraries
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Hero Travel (using Ventrata's OCTO API)

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

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

Creating the Hero Travel Connection

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

Before you begin:

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

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

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

📗 TIP

Hero Travel 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 Hero Travel Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Hero Travel connection

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

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

Hero Travel

hero.travel

Ventrata Partner ID: 6054d9e7-004f-444d-9104-2b573d41b517

Hero Travel: Reseller Connection