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 will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Rezdy, visit rezdy.com.

📒 NOTE

Looking to resell products from operators that use Rezdy instead? See Rezdy: Operator Backend.

📒 NOTE

This connection is available only to specific client accounts. If you're interested in using it, contact our Technical Support or your Ventrata Customer Success Manager.

Primary website	rezdy.com
Tags	Reseller System
Destination markets	🌎 Global
Source markets	🌎 Global
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Rezdy (using Ventrata's OCTO API)

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

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

Creating the Rezdy Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

Product Mapping	❌	You can't map products from Ventrata. Rezdy maps them on its side, through your account manager or Rezdy's portal. This works as follows: Get Products (`GET /products`) – when Rezdy 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}`) – Rezdy re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Rezdy's side – Rezdy links each Ventrata option and unit to its own listing and ticket types. Your Rezdy account manager does this for you, or you do it in Rezdy's own portal if Rezdy offers one. You only share the connection's API key. What this means for you: Rezdy can only sell what it has mapped. When you add a product, option or unit in Ventrata, Rezdy may see it on its next refresh, but it won't sell it until it's mapped. So tell your Rezdy account manager whenever you add one.
Content Sync	❌	Rezdy doesn't read your product content from Ventrata. Rezdy uses the descriptions, images and other content set up on its own side, so update your content with Rezdy directly.
Availability Sync	✅	Rezdy checks your live availability in Ventrata. Ventrata doesn't push availability changes to Rezdy. This works as follows: Availability Check (`POST /availability`) – Rezdy 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 Rezdy 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 Rezdy can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. What this means for you: when you close a date, change capacity or sell out in Ventrata, Rezdy shows it only after its next check, so there can be a short delay. Ventrata's check at booking still prevents overbooking.
Pricing Sync	✅	Your prices come back with every availability check, once Rezdy asks for them with the octo/pricing capability. This works as follows: `octo/pricing` capability – Rezdy 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 Rezdy, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Rezdy 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. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Rezdy to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Rezdy's portal. Otherwise it may be off, and Rezdy won't receive your Ventrata prices.
Promotions Sync	❌	Your Ventrata promotions don't apply on Rezdy. Prices on Rezdy don't include promotions you create in Ventrata. Set up any promotions with Rezdy directly.
Bookings Sync	✅	Bookings and cancellations made on Rezdy 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 Rezdy, Rezdy 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, Rezdy confirms the hold. 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. Rezdy gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Rezdy 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 Rezdy, Rezdy 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 Rezdy has to contact you. Change: Booking Update (`PATCH /bookings/{uuid}`) – lets Rezdy change a booking in place, for example a new date, time or number of people. Some resellers cancel and rebook instead. ‼️ IMPORTANT – Bookings sync one way, from Rezdy to Ventrata. If you cancel, change or rebook a booking from Rezdy in Ventrata, for example in the Dashboard, Rezdy isn't notified. Contact Rezdy so the booking is cancelled or changed on their side too, or ask the customer to cancel through Rezdy.
Pickups/Dropoff Sync	❌	Rezdy doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Rezdy how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Rezdy doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Rezdy how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Rezdy. Customers can only book your main products and options on Rezdy. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Rezdy. Ventrata doesn't notify Rezdy when a ticket is scanned or redeemed. Rezdy only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Rezdy pass holders can't be scanned at your entrance without a booking. Customers from Rezdy need a booking made through Rezdy before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Rezdy. Gift cards bought in Ventrata can't be used on Rezdy, and Rezdy can't sell Ventrata gift cards.

✅ supported · ❌ not supported

Good to know: limits and details of the Rezdy connection

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

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

Rezdy Pty Limited

Level 5, 320 Pitt Street, Sydney, NSW 2000

Australia

rezdy.com

Ventrata Partner ID: 0148316a-beef-4f9f-8ddc-9adc232012d7

Rezdy: Reseller Connection