AlliedTPro is a North American receptive operator and destination management company (DMC) trading since 1955, operating under Horizon Travel Services. For operators, it brings trade demand only: more than 600 tour operators and travel companies in over 50 countries package US and Canada product into FIT, escorted tour, self-drive, VIP concierge and leisure and MICE group programs, bringing long-lead international bookings.

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

To learn more about partnering with AlliedTPro, visit alliedtpro.com.

Primary website	alliedtpro.com
Tags	Receptive & Inbound Operator · Multi-day & Packaged Tours
Destination markets	🇨🇦 Canada · 🇺🇸 US
Source markets	🌎 Global
Specialties	US and Canada product for international tour operators
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	AlliedTPro (using Ventrata's OCTO API)

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

Availability Sync – AlliedTPro checks your live availability in Ventrata.
Pricing Sync – AlliedTPro gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from AlliedTPro are created in Ventrata instantly, and customers get Ventrata tickets.
Pickups/Dropoff Sync – pickup and drop-off details from AlliedTPro bookings are passed to Ventrata.

Creating the AlliedTPro Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the AlliedTPro connection

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

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

Horizon Travel Services LLC

501 7th Avenue, Suite 1610, New York, NY 10018

United States

alliedtpro.com

Ventrata Partner ID: 81f85de2-ff44-41d2-af9c-bd59c336493c

AlliedTPro: Reseller Connection