Rezdy is an Australian reservation system and channel manager for tour and activity operators whose marketplace connects supplier inventory with more than 25,000 resellers in over 100 countries and around 90 currencies. For operators, it brings trade demand from the agents and resellers booking through the Rezdy marketplace.
Connecting Rezdy to Ventrata lets you resell products from operators that use Rezdy as their booking system. Ventrata reads their live availability and prices from Rezdy, and every booking you take is created directly in the operator's Rezdy account.
To learn more about Rezdy, visit rezdy.com.
📒 NOTE
Looking for Rezdy to resell your products instead? See Rezdy: Reseller Connection.
📒 NOTE
This connection is coming soon. It's in development. If you'd like to use it, contact our Technical Support or your Ventrata Customer Success Manager.
📗 TIP
You can allow/disallow products or destinations on the connection level to limit which products Expedition Software can access.
Primary website | |
Tags | Booking / Ticketing System |
Connection features | Availability Sync · Pricing Sync · Bookings Sync |
Developed by | Ventrata (using Rezdy OCTO API) |
This operator connection (also called a backend) lets you resell products from operators that use Rezdy as their primary booking system, with every booking created directly in Rezdy. Features of this connection include:
Availability Sync – live availability comes from the operator's Rezdy account.
Pricing Sync – prices come from Rezdy, or you set prices in Ventrata.
Bookings Sync – bookings, updates and cancellations post from Ventrata to Rezdy, and Rezdy issues the tickets or vouchers.
Creating the Rezdy Connection
🔐 Required Role Permissions: See Operators, Modify Operators, See Products, Modify Products
Before you begin:
You must have a commercial agreement with the operator for their rates and terms.
You must have the OCTO API key (generated in Ventrata and shared with Expedition Software) for the operator. See the steps below.
An agreement with Expedition Software to use their services.
You must recreate the operator's products in Ventrata. See how to create products. The connection syncs availability, pricing and bookings, but doesn't create products in Ventrata.
Step 1: Configure the Operator in Ventrata
You create an OCTO connection in Ventrata (Connections > Connections > + New Connection > Expedition Software > Create Octo Connection), then securely share the OCTO API key shown on the connection to your Expedition Software contact.
In the Ventrata Dashboard, go to Products → Operators and open the operator. If they don't exist yet, create them as an operator first.
In the Backend Partner section, select Rezdy and enter the OCTO API key (generated in Ventrata and shared with Expedition Software).
Press Update Operator.
📒 NOTE – Each OCTO API key (generated in Ventrata and shared with Expedition Software) connects you to one operator. Set up each Rezdy operator separately.
Step 2: Connect Each Product
Open the operator's product in Products → Products and edit it. Check that Operator is set to this operator.
Tick Backend Connected. Tick Backend Availability to use availability from Rezdy, and Backend Pricing to use prices from Rezdy.
Press Update Product.
Mapping Products to Rezdy
‼️ IMPORTANT
Mapping tells Ventrata which Rezdy product, option and units to check availability for and book. If a backend-connected product isn't mapped correctly, its bookings fail. A red highlight across the product row shows an incorrectly mapped product.
In the Ventrata Dashboard, go to Products → Products and open the product.
Open the Mappings tab. It appears once the product is set to Backend Connected.
For each Ventrata option and unit, select the matching Rezdy product, option and units from the dropdowns, which Ventrata loads from Rezdy. Don't leave any field empty.
Press Save Changes.
📗 TIP
Make a test booking after mapping, and ask the operator to confirm it arrived in their Rezdy account.
Managing the Rezdy Connection
Update the mapping when the operator changes products, options or units in Rezdy.
Replace the key on the operator if Rezdy or the operator issues a new one.
Switch Backend Availability or Backend Pricing off on a product to use Ventrata's own availability or prices instead. Bookings still post to Rezdy.
Connection Features Detailed
This section is for anyone who wants to know exactly how the Rezdy connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Rezdy, using Rezdy OCTO API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.
In short: Ventrata asks Rezdy for availability and prices whenever someone looks at a backend-connected product, and creates every booking in the operator's Rezdy account. Rezdy doesn't send changes back to Ventrata.
Timings are typical for Rezdy and rounded, and they can change.
Product Mapping | ✅ |
You map each Ventrata product, option and unit to the operator's Rezdy product in the Ventrata Dashboard. This works as follows:
What this means for you: if something is missing from the dropdown, the operator hasn't made it available to you in Rezdy. Ask them to. |
Content Sync | ❌ |
Ventrata doesn't import product content from Rezdy. Ventrata doesn't import product content from Rezdy. You create and describe the products in Ventrata yourself. |
Availability Sync | ✅ |
With Backend Availability on, Ventrata checks the operator's live availability in Rezdy. This works as follows:
What this means for you: customers book against the operator's live Rezdy availability, so you can't oversell a slot the operator has already sold elsewhere. |
Pricing Sync | ✅ |
With Backend Pricing on, Ventrata takes prices from Rezdy. This works as follows:
|
Promotions Sync | ❌ |
Promotions aren't sent to Rezdy. Promotions aren't sent to Rezdy. Your Ventrata promotions still apply to the price your customer pays in Ventrata. |
Bookings Sync | ✅ |
Bookings made in Ventrata for a backend-connected product are created in the operator's Rezdy account. This works as follows:
Expedition Software can retrieve bookings, updates and cancellations for those products.
‼️ IMPORTANT – Bookings sync one way, from Ventrata to Rezdy. If the operator changes or cancels a booking in Rezdy, Ventrata isn't notified. Ask the operator to tell you about any changes they make. |
Pickups/Dropoff Sync | ❌ |
Pickup and drop-off details aren't passed to Rezdy. Pickup and drop-off details aren't passed to Rezdy. Share them with the operator another way if a product needs them. |
Custom Questions Sync | ❌ |
Answers to your booking questions aren't passed to Rezdy. Answers to your booking questions aren't passed to Rezdy. Share them with the operator another way if they need them. |
Extras Sync | ❌ |
Extras and add-ons aren't booked in Rezdy. Extras and add-ons aren't booked in Rezdy. Only the main product, option and units are. |
Redemption Sync | ❌ |
Redemptions and other status changes in Rezdy aren't sent back to Ventrata after a booking is confirmed. Redemptions and other status changes in Rezdy aren't sent back to Ventrata after a booking is confirmed. |
Pass Walkup Scanning Sync | ❌ |
Pass walk-up scanning isn't available with Rezdy. Pass walk-up scanning isn't available with Rezdy. |
Gift Card Sync | ❌ |
Ventrata gift cards aren't passed to Rezdy. Ventrata gift cards aren't passed to Rezdy. Gift card payments stay in Ventrata. |
✅ supported · ❌ not supported
Good to know: limits and details of the Rezdy connection
Good to know: limits and details of the Rezdy connection
Live availability: availability comes from Rezdy as people browse.
One-way bookings: changes the operator makes in Rezdy don't reach Ventrata.
You can revoke access at any time by setting the connection to inactive or archiving it.
FAQs
I get an error when I save the operator's backend configuration.
I get an error when I save the operator's backend configuration.
The OCTO API key (generated in Ventrata and shared with Expedition Software) or endpoint is most likely incorrect. Check them with your operator. If the issue persists, contact our Technical Support.
There's no Backend Connected box in the product settings.
There's no Backend Connected box in the product settings.
The operator set on the product most likely doesn't have a backend configured. Check the operator's Backend Partner settings and try again. If the issue persists, contact our Technical Support.
The product, option or unit I want to map isn't in the dropdown.
The product, option or unit I want to map isn't in the dropdown.
The dropdowns list what the operator has made available to you in Rezdy. Ask the operator. If the issue persists, contact our Technical Support.
Bookings fail for a backend-connected product.
Bookings fail for a backend-connected product.
Check the product's mapping first: every option and unit must be mapped. Then check that the slot is still available in Rezdy. If the issue persists, contact our Technical Support.
Expedition Software cannot see some of my products.
Expedition Software cannot see some of my products.
Check which destinations, products and options are allowed on the connection, and confirm your products and options are enabled for sale on the Direct API source. If the issue persists, contact Technical Support.
Useful Resources
📚 More about Ventrata connections
Partner Information
Expedition Software
Ventrata Partner ID: 01a199e1-e01b-7530-96b9-421c090113e1