Rezdy is the dominant booking platform for tour operators in Australia, New Zealand, parts of Europe, and a growing share of the rest of the global market. If you run a tour operation on Rezdy, integrating it with a digital waiver platform is one of the highest-leverage operational changes you can make — and it’s faster than most operators expect.

This guide walks through the complete Rezdy + digital waiver integration: native API setup, the gotchas that catch first-time launches, how to handle Rezdy’s channel manager bookings (Viator, GetYourGuide, Expedia, and the rest of Rezdy Connect), and how to manage the multi-language and pickup-location complexity that’s more common on Rezdy than on North American booking platforms.

If you haven’t yet decided on a digital waiver platform, start with our complete digital waivers for tour operators guide. For a side-by-side platform comparison, see our best waiver software for tour operators post.

Why Integration Matters More on Rezdy

Rezdy operators tend to face two complications that make the integration even more valuable than on competing platforms:

Channel manager / OTA bookings. Rezdy Connect distributes bookings to Viator, GetYourGuide, Expedia, Airbnb Experiences, Klook, and dozens of regional OTAs. These bookings flow into Rezdy with varying levels of guest contact information. Without integration, you’re manually chasing waivers from guests whose contact details you may not even have cleanly.
Multi-language inbound traffic. Rezdy’s strongest markets (Europe, AU/NZ inbound) have heavy international guest traffic. International guests signing English-language waivers they don’t fully understand can argue they didn’t give informed consent — a real legal risk in restrictive jurisdictions.

A properly configured Rezdy + digital waiver integration handles both. Bookings from any channel automatically fire the appropriate language waiver to the right guest at the right time, with reminders and write-back.

What You’ll Need Before Starting

An active Rezdy account with admin/owner access
A digital waiver platform that integrates with Rezdy (native or via Zapier)
Your tour operator waiver template, finalized and attorney-reviewed (start with our free tour operator waiver template)
A list of your Rezdy products that need waivers
30–45 minutes for native integration; 60–90 minutes for Zapier setup

Path 1: Native Rezdy Integration (Recommended)

Native integrations handle channel manager bookings, group routing, multi-language detection, and write-back automatically. They’re worth the small additional setup effort.

Waiver World offers native Rezdy integration. The setup pattern below applies to most native integrations.

Step 1: Generate a Rezdy API Key

In your Rezdy dashboard:

Navigate to Integrations → API Access (under your account/settings menu)
Click Create New API Key
Name it descriptively (e.g., “Waiver World Integration”)
Copy the key immediately — Rezdy displays it only once
Set permissions: read access to bookings and products, write access to booking notes/extras if you want write-back

If your account doesn’t show API access, contact Rezdy support — some account tiers require API access to be enabled manually.

Step 2: Connect Rezdy to Your Waiver Platform

In your waiver platform’s integrations area:

Find the Rezdy integration and click Connect
Paste the API key
Confirm — your Rezdy products should populate automatically

If products don’t appear, the API key permissions are likely wrong, or the API access isn’t fully enabled on your Rezdy account.

Step 3: Map Rezdy Products to Waiver Templates

Each Rezdy product (your tours, rentals, lessons, packages) should map to the most appropriate waiver template:

Whitewater rafting product → rafting waiver with water/cold/rapids risk language
Sea kayak tour product → kayak waiver template with cold-water and marine traffic language
Wine tour product → walking tour waiver with traffic/alcohol consumption language
Bungee jump product → adventure waiver with height/equipment failure language

Generic waivers fail courts on activity-specific risks. Activity-specific templates with proper risk disclosure are what the law expects. Our tour operator waiver template includes activity-specific risk language for 10 common tour types.

For combo or package products that include multiple activities, map to a multi-activity template that discloses every activity’s specific risks.

Step 4: Configure Trigger Events

Rezdy supports several webhook events. The two that matter most:

BOOKING_CONFIRMED — fires after the booking is confirmed (typically post-payment)
BOOKING_CANCELLED — fires when a booking is cancelled

Most operators should trigger waiver sends on BOOKING_CONFIRMED. Some platforms can also listen to BOOKING_UPDATED events (e.g., date changes), which keeps waiver expiration aligned with the actual tour date. If your platform supports it, enable it.

Step 5: Configure Reminder Cadence

A typical Rezdy operator reminder cadence:

Initial waiver email/SMS at booking confirmation
Reminder 48 hours before tour start (catches the multi-day-out international booker)
Reminder 24 hours before tour start
Reminder 4 hours before tour start
Final reminder 30 minutes before tour start

For inbound international guests booking weeks in advance, the 48-hour reminder is critical — guests often forget waivers signed at booking time and need a fresh prompt closer to the trip.

For same-day bookings, tighten this:

Immediate at booking
1-hour reminder
30-minute reminder

Most platforms let you configure reminders per product. Use this — your wine tour reminder cadence should differ from your bungee jump reminder cadence.

Step 6: Configure Multi-Language Detection

Rezdy’s strongest markets have heavy multi-language guest traffic. Configure your integration to detect the guest’s preferred language and serve the appropriate waiver version:

Booking-level language preference — Rezdy may include a language field in the booking data
Browser language detection — fallback when Rezdy doesn’t specify
Manual override — let the guest pick their preferred language at the start of the signing flow

Waiver World supports English, Spanish, and Thai out of the box. For European Rezdy operators, plan to also build out German, French, Italian, and Dutch versions of your waiver if those represent significant inbound markets.

Step 7: Configure Write-Back

Write-back puts the signed waiver URL onto the Rezdy booking record. Rezdy supports two common patterns:

Booking comments / notes — staff-visible note on the booking
Extras / custom fields — dedicated field, viewable on the booking detail page

Custom fields are cleaner because they show consistently in your booking dashboard. Talk to Rezdy support to set up a custom field for waiver URLs if you don’t already have one.

Step 8: Run Test Bookings

Before going live, create at least 5 test bookings covering:

A solo adult booking
A 2-adult booking
A family booking with minors
A 6+ person group booking
A booking from a channel manager partner (Viator, GetYourGuide)

For each, verify:

Each adult guest receives a unique waiver link within 60 seconds
Multi-language guests receive the correct language version
The signed waiver URL writes back to the Rezdy booking
Cancellation voids any unsent waivers
The mobile signing flow works on iOS and Android

If any case fails, fix it before launch.

Channel Manager Bookings: The Critical Edge Case

Bookings from Rezdy Connect distribution partners (Viator, GetYourGuide, Expedia, Klook, Airbnb Experiences, etc.) are where most Rezdy + waiver integrations have problems. The channel manager booking flow has unique characteristics:

Limited Guest Contact Information

Some OTAs only pass through the lead booker’s contact info, with no per-guest emails. Some pass through anonymized email addresses (e.g., viator-booking-12345@viator.com) that don’t reach the actual guest. Some pass through the OTA’s own email instead of the guest’s.

The implication: You may not be able to email or SMS individual waivers in advance for channel manager bookings.

Solutions for Channel Manager Bookings

1. QR-code-at-boarding fallback. For OTA bookings without reliable guest contact info, deploy a QR code at your boarding area. Guests scan and sign in 60 seconds before the activity starts. See our QR code waiver guide for setup.

2. Lead-booker-only mode for some channels. Configure your integration to send the waiver to the lead booker for OTA bookings, with a note that all participants must sign. Less ideal than per-guest routing but works.

3. Pre-arrival email to the lead booker. Send a clear email to the lead booker at booking confirmation explaining the waiver process and asking them to forward the signing link to other participants.

4. Post-booking outreach via the channel. Some channel managers let you send messages through their platform. Use this to send waiver links if the booking data doesn’t include direct guest contacts.

For tour operators with significant channel manager booking volume, the QR-code-at-boarding fallback is essential. Plan for it during initial integration setup, not after launch.

Pickup-Location Timing

Many Rezdy products use pickup locations rather than a single boarding point. This changes waiver reminder timing:

For products with 8 AM start, 7:30 AM pickup, your “30-minute final reminder” should fire at 7:00 AM (30 minutes before pickup), not 7:30 AM
For products with multiple pickup windows, configure reminders against the earliest pickup time

Most native integrations handle this automatically by reading Rezdy’s pickup data. Zapier-based setups may require additional logic. Verify your reminder timing against pickup, not start time, during testing.

Path 2: Zapier Setup (Fallback)

If your waiver platform doesn’t offer native Rezdy integration, Zapier works for most use cases.

Zapier Setup Steps

Create a new Zap. Trigger: Rezdy → New Booking (filtered to confirmed status).
Set up authentication with your Rezdy API key.
Add a Filter step to skip cancelled bookings and bookings with channel manager guest data quality issues.
Add a Formatter step to extract guest details. Rezdy’s data structure can include multiple participants per booking — use a Looper step (Zapier Premium) to iterate through each adult.
Add the action step: Your Waiver Platform → Create Signing Link. Map guest details from Rezdy to the waiver platform’s required fields.
(Optional) Add a write-back step: Rezdy → Update Booking Comments with the signed waiver URL.
(Optional) Add a Cancellation Zap triggered on BOOKING_CANCELLED to void unsent waivers.

Zapier Limits with Rezdy

Channel manager bookings. Zapier-based setups have particular trouble with the variable contact-info quality from channel partners. Plan for QR-code-at-boarding fallback for OTA bookings.
Multi-language detection. Requires conditional Zapier branching that gets complex fast.
Pickup-location timing. Native integrations handle this; Zapier requires custom logic.
Rate limits. Rezdy API has rate limits that high-volume operators can hit during peak booking hours.

For high-volume operators (5,000+ bookings/year) or operators with significant channel manager traffic, native integration is a meaningful upgrade over Zapier.

Common Rezdy Integration Pitfalls

These are the failure modes we see most often during rollout:

1. Underestimating Channel Manager Booking Volume

Operators new to channel managers often assume channel bookings are a small percentage. They aren’t — for many tour operators, OTAs represent 30–60% of total volume. Plan your QR-code fallback before launch, not after the first peak weekend.

2. Generic Waiver for All Products

Rezdy operators often have many products (multi-day tours, single-day tours, rentals, lessons, packages, add-ons). A single generic waiver weakens your legal protection on activity-specific risks. Map each Rezdy product to an appropriate template.

3. Forgetting About Pickup Timing

If your reminders fire against tour start instead of pickup time, guests at distant pickup locations get the “30 minute” reminder after they’ve already been picked up. Configure against pickup time.

4. Not Handling Multi-Language Properly

Sending an English waiver to a French or Italian guest is a real legal risk in restrictive jurisdictions. Build out language versions for your major inbound markets and detect language at signing time.

5. Letting Channel Manager Bookings Skip the Audit Trail

If your fallback for OTA bookings is “let the guide manually verify the guest signed something on paper at boarding,” you’ve lost the audit trail benefit of digital waivers. Use QR codes that route to your digital waiver platform — even at boarding, the digital flow is more defensible than paper.

6. Not Testing Cancellations

A cancelled booking that still triggers a waiver send leads to confused guests. Test the cancellation flow explicitly during setup.

7. Skipping Write-Back

Without write-back, your check-in staff has to leave Rezdy and look up waiver status in a separate system. The whole operational benefit erodes. Set up write-back during initial configuration.

Migrating from a Manual or Third-Party Setup

If you’re currently using paper waivers or a non-integrated digital waiver tool with Rezdy, the migration path is:

Week 1

Pick a waiver platform with native Rezdy integration (Waiver World offers a 14-day free trial with native Rezdy support)
Customize your waiver template (or start from our free tour operator template)
Get attorney review for each state/country you operate in (see our state-by-state enforceability guide)

Week 2

Generate Rezdy API key
Connect the integration
Map products to waiver templates
Configure trigger events, reminder cadence, multi-language, and write-back
Run test bookings (5–10 covering all scenarios including channel manager)

Week 3

Soft-launch with new bookings only
Keep paper as backup
Train staff on the new check-in flow
Print QR-code signage for boarding-area fallback

Week 4

Full cutover — stop accepting paper waivers for new tours
Audit signing rates daily for the first week
Tune reminder cadence based on no-sign patterns

After this, the integration runs itself. Most operators check signing rates weekly thereafter.

What Boarding Looks Like After the Integration

Pre-integration, with paper waivers:

Guest arrives → staff greets → staff hands clipboard → guest fills out form (5–8 min) → staff verifies completion → guest is cleared → next guest in line

For a 12-person tour, total: 60–90 minutes of staff time, 18–25 minutes of boarding delay.

Post-integration, with Rezdy + digital waivers:

Guest arrives → staff scans booking → ”✓ waiver signed” badge appears → guest is cleared → next guest in line

For the same 12-person tour, total: 5–10 minutes of staff time, 2–3 minutes of boarding delay.

Frequently Asked Questions

Does Rezdy have its own waiver feature?

Rezdy supports basic waiver collection through configurable booking forms, but it lacks the depth of dedicated waiver platforms — limited audit trail, no advanced multi-language workflows, weaker template customization, no offline mode, and no QR-code check-in. Most serious tour operators use a dedicated waiver platform integrated with Rezdy.

How much does Rezdy + a waiver platform cost together?

Rezdy’s pricing is separate from the waiver platform pricing. Most digital waiver platforms charge $29–$199/month based on volume. Waiver World plans start at $29/month for 100 waivers and scale to unlimited usage on the Business plan. For most operators, labor savings cover the cost in the first month.

Can I integrate Rezdy with a free waiver tool?

Free waiver tools generally don’t offer native Rezdy integration. You’d need Zapier (often paid plan), and most free tools don’t have audit-trail depth required for legal defensibility. False economy.

What if my Rezdy bookings come from channel partners with no guest emails?

Use a QR-code-at-boarding fallback. The guest scans on arrival and signs in 60 seconds before the activity starts. See our QR code waiver guide.

Can the integration handle multiple languages automatically?

Yes, if your waiver platform supports it. Native integrations can read Rezdy’s language data (when present) and serve the appropriate waiver version. Waiver World supports English, Spanish, and Thai out of the box.

How do refunds and cancellations affect the waiver?

A signed waiver remains valid even if the booking is later cancelled — it documents that the guest acknowledged the risks at the time. For unsigned waivers on cancelled bookings, the integration should void the pending send.

Does the integration work for Rezdy multi-day or expedition products?

Yes. Configure waiver expiration to align with the tour end date. Multi-day expeditions should typically use a single waiver covering the full trip with extended risk language for cumulative exposure.

What happens if Rezdy’s API goes down?

Modern waiver platforms queue webhook events and retry automatically when the API recovers. Native integrations handle this gracefully. Zapier-based setups may drop events during extended outages.

Can I send waivers in advance for FIT (independent traveler) bookings?

Yes — direct bookings (where Rezdy has guest emails) work the same as any direct booking. The waiver fires at confirmation, with reminders leading up to the tour. For FIT bookings via OTAs without guest emails, the QR-code fallback is the right answer.

Your Next Step

A Rezdy + digital waiver integration is one of the highest-ROI changes a tour operator can make. The labor savings, legal defensibility, and guest experience improvements are dramatic — and the setup is faster than most operators expect.

Here’s the fastest path:

Pick a waiver platform with native Rezdy integration — Waiver World offers a 14-day free trial with native Rezdy support
Customize your tour operator waiver using our free template
Get attorney review in each operating jurisdiction (see our state-by-state enforceability guide)
Generate your Rezdy API key and connect the integration
Plan for channel manager bookings with a QR-code-at-boarding fallback
Configure multi-language for your inbound markets
Run test bookings covering direct, group, and channel manager scenarios
Soft-launch with new bookings, then cut over fully within 2 weeks

Visit our tourism industry page to see how Waiver World handles tour operator workflows end-to-end, or start your free trial — most operators are integrated and live within an afternoon.

Related guides:

Rezdy Waiver Integration: Complete Setup Guide for Tour Operators (2026)