Project Expedition is a global tours and activities marketplace selling to consumers and, in large part, through travel advisors, acting as a preferred supplier to Virtuoso and other advisor networks, with shore excursions, multiday trips, transfers, airport services and custom itineraries across six continents. For operators, it brings vetted North American advisor demand with the United States, Canada and the United Kingdom its main markets, long-lead bookings for cruise passengers and group requests alongside consumer orders.

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

To learn more about partnering with Project Expedition, visit projectexpedition.com.

Primary website	projectexpedition.com
Tags	OTA · Tours & Activities OTA · B2B Marketplace
Destination markets	🌎 Global
Source markets	🇨🇦 Canada · 🇬🇧 UK · 🇺🇸 US
Specialties	Sales through travel advisor networks such as Virtuoso
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync · Custom Questions Sync
Ventrata Booked GMV (last 12 months)	US$1M+
Ventrata Booked Suppliers (last 12 months)	25+
Developed by	Project Expedition (using Ventrata's OCTO API)

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

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

Creating the Project Expedition Connection

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

Before you begin:

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

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

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

📗 TIP

Project Expedition 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 Project Expedition Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Project Expedition connection

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

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

Project Expedition LLC

447 Broadway, Floor 2 #801

New York, NY 10013, United States

projectexpedition.com

Ventrata Partner ID: de3e7af3-4c50-4ee0-82f2-064e29bf061b

Project Expedition: Reseller Connection