How to Integrate Digital Waivers with FareHarbor, Rezdy, Bokun & Peek

For tour operators, the single biggest gain from digital waivers comes from integration with your booking platform. A standalone waiver tool saves time. A connected waiver tool transforms your operations — guests sign automatically the moment they book, your boarding line vanishes, and your staff stops chasing signatures.

This guide covers exactly how that integration works for the six booking platforms tour operators use most: FareHarbor, Rezdy, Bokun, Peek Pro, Checkfront, and TrekkSoft. Whether you’re evaluating a digital waiver platform or trying to wire up the one you already have, this is the practical setup guide.

If you’re earlier in the process and still deciding whether to switch from paper to digital, start with our complete digital waivers for tour operators guide — then come back here when you’re ready to wire it up.

Why Booking Platform Integration Matters

Without integration, your digital waiver is still a manual workflow:

• Booking comes in → staff manually copies guest details into the waiver tool
• Waiver tool sends guest a link → staff has to monitor inbox to know if they signed
• Guest arrives → staff has to manually look up whether the waiver is on file

With proper integration, the entire flow is automatic:

• Booking comes in → waiver tool receives a webhook with guest details
• Waiver tool emails or texts each guest a personalized signing link
• Guest signs → booking record updates with waiver URL and timestamp
• Guest arrives → staff sees a green check mark in the booking system, done

This is the difference between “we now use digital waivers” and “we eliminated 80% of our front-desk labor.”

What “Integration” Actually Means

When evaluating a waiver platform’s integration with your booking system, look for these specific capabilities:

If your waiver platform handles all six, integration is a 10–20 minute setup. If it handles only 1–2, you’ll be patching the gaps with Zapier and feeling it.

Platform-by-Platform Setup

FareHarbor

FareHarbor is the dominant booking platform for North American tour operators. Its API is well-documented and most modern waiver platforms have native integrations.

How it works:

1. In FareHarbor, generate an API key under Settings → API.
2. In your waiver platform, add a FareHarbor connection and paste the key.
3. Map your FareHarbor activities (called “items”) to specific waiver templates. A whitewater rafting trip should fire your rafting waiver; a city walking tour should fire your walking waiver.
4. Choose your trigger: most operators trigger waivers on BookingConfirmed (after payment) rather than BookingCreated (before payment). This avoids waiver spam to guests who abandon checkout.
5. Configure write-back: signed waiver URL writes to a custom field on the FareHarbor booking record.

Common gotchas:

• FareHarbor’s group bookings can list multiple “people” under one booking. Make sure your waiver tool routes to each guest, not just the lead booker.
• If you allow same-day bookings, set your reminder cadence aggressively (1 hour, 2 hours, 30 minutes before tour) — guests who book at 9am for an 11am tour need to sign fast.

Rezdy

Rezdy is the leading booking platform in Australia, New Zealand, and parts of Europe. Its REST API is straightforward and webhook-based.

How it works:

1. In Rezdy, navigate to Integrations → API Access and generate an API key.
2. In your waiver platform, add the Rezdy connection.
3. Map Rezdy product codes to waiver templates.
4. Subscribe to the BOOKING_CONFIRMED and BOOKING_CANCELLED events.
5. Configure write-back to an extra info field on the Rezdy booking.

Common gotchas:

• Rezdy supports “agent bookings” via channels like Viator and GetYourGuide. The contact info on agent bookings is sometimes the agent’s, not the guest’s. Verify your waiver tool handles this correctly — usually by pulling guest details from the participant list rather than the booking contact.
• Rezdy’s pickup-location feature can shift the timing of waiver sends. Make sure your reminder cadence accounts for pickup, not start time.

Bokun

Bokun (owned by Viator/TripAdvisor) is gaining ground in international tourism, particularly Iceland, Europe, and Latin America.

How it works:

1. In Bokun, generate an API key under Settings → Developer.
2. In your waiver platform, add the Bokun connection.
3. Map Bokun experiences to waiver templates.
4. Subscribe to BookingConfirmed webhook.
5. Configure write-back to Bokun’s booking notes or custom field.

Common gotchas:

• Bokun bookings frequently come from third-party OTAs (Viator, GetYourGuide, Expedia). The guest contact details may be limited or anonymized. Have a fallback flow for guests who don’t have an email on file — usually a QR code at boarding.
• Bokun’s multi-passenger bookings can have all participants under one record without per-guest emails. Test this case explicitly.

Peek Pro

Peek Pro is popular with smaller adventure operators in North America.

How it works:

1. Peek Pro’s integration is typically OAuth-based — you authorize your waiver platform from inside Peek’s settings.
2. Map Peek activities to waiver templates.
3. Webhook fires on Booking Created and Booking Updated.
4. Write-back appears as an attachment on the Peek booking.

Common gotchas:

• Peek’s “Add-ons” sometimes need their own waiver. A jet ski rental add-on attached to a sailing tour booking should probably fire the jet ski waiver in addition to the sailing waiver. Test your add-on logic.

Checkfront

Checkfront is widely used in adventure tourism, equipment rentals, and accommodation-tour bundles.

How it works:

1. In Checkfront, create an API token under Manage → API.
2. In your waiver platform, add the Checkfront connection.
3. Map Checkfront items to waiver templates.
4. Subscribe to the booking.update event with status filters for confirmed bookings.
5. Configure write-back to a Checkfront custom field or staff note.

Common gotchas:

• Checkfront supports multi-day rentals. Make sure your waivers cover the full rental period and don’t expire mid-rental.

TrekkSoft

TrekkSoft is a European platform popular with Alpine and Mediterranean tour operators.

How it works:

1. In TrekkSoft, generate an API key under Settings → Integrations.
2. In your waiver platform, add the TrekkSoft connection.
3. Map TrekkSoft activities to waiver templates.
4. Subscribe to booking-confirmed webhooks.

Common gotchas:

• TrekkSoft is heavily multi-language (German, French, Italian, English). Make sure your waiver platform supports your guest’s preferred language at signing time, not just yours. See our tour operator waiver template for the structure.

What If My Booking Platform Isn’t Listed?

Plenty of operators use niche or regional booking platforms — Acuity, Resmark, Xola, Beyonk, Regiondo, TicketingHub, and dozens of others. If your platform isn’t in the native integration list of your waiver tool, you have three options:

Option 1: Zapier or Make.com

Both Zapier and Make have robust integrations with most booking platforms. The pattern is:

Booking platform (trigger: new booking) → Webhook → Your waiver platform’s “Create signing link” action → Email/SMS to guest

Setup takes 30–60 minutes. Reliability is good but not as bulletproof as native integration. Expect to revisit the Zap once or twice a year when one platform changes its API.

Option 2: REST API + a Small Webhook Server

If your booking platform has webhooks but your waiver platform doesn’t natively integrate, you can stand up a tiny webhook receiver (Cloudflare Worker, AWS Lambda, or a hosted alternative) that translates between the two. Two hours of developer time, then it runs forever.

Option 3: Email Parsing (Last Resort)

Some waiver platforms can parse incoming booking confirmation emails and extract guest details. Lower fidelity, but works when no API exists. Use this only if Options 1 and 2 are blocked.

What to Verify Before Going Live

After you’ve wired up the integration, run this checklist with real test bookings:

• Adult guest receives waiver link within 60 seconds of booking confirmation
• Group booking (3+ guests) routes individual links to each adult
• Cancellation voids the waiver send if it hasn’t been signed yet
• Booking modification (date change, guest count change) updates the waiver flow correctly
• Signed waiver URL appears on the booking record in your booking platform
• Signing-status badge is visible to your check-in staff at boarding
• Reminder emails/SMS fire at the cadence you configured
• Multi-language waiver renders correctly in each supported language
• Mobile signing flow works on both iOS and Android
• Offline boarding fallback (QR code or staff override) works if a guest didn’t sign in advance

If any of these fail, fix it before launch. Each is the kind of edge case that turns into a real-world problem at the worst time.

Common Integration Pitfalls

A few patterns we see tour operators hit during rollout:

1. Overly aggressive reminders. Sending an SMS every hour is annoying. A reasonable cadence is: at booking, 24 hours before, 4 hours before, 30 minutes before.

2. Forgetting third-party booking channels. If 40% of your bookings come through Viator, Expedia, GetYourGuide, or Airbnb Experiences, those bookings flow into your booking platform but may not have full guest contact info. Plan a QR-code-at-boarding fallback for those guests.

3. Not testing cancellations. A cancelled booking that still triggers a waiver send leads to confused, annoyed guests. Test this case explicitly.

4. Skipping the activity-to-template mapping. Tour operators with multiple activity types need different waivers for each. Sending a generic waiver weakens your legal protection.

5. Letting waivers expire mid-season for repeat guests. Multi-pass holders need automatic renewal at 12 months. Set this up before your peak season starts, not during.

Your Next Step

Once your waiver platform is wired up to your booking system, the boarding-time savings show up almost immediately. Most operators see boarding times drop 60–80% within the first month, with the bulk of waivers signed in advance from the guest’s hotel or home.

Here’s the fastest way to ship:

1. Pick a digital waiver platform that has native integration with your booking tool. Waiver World supports FareHarbor, Rezdy, Bokun, Peek Pro, Checkfront, and TrekkSoft natively, plus Zapier for everything else.
2. Customize a tour operator waiver template — start from our free tour operator waiver template.
3. Wire up the integration using the platform-specific steps above.
4. Run the verification checklist with real test bookings.
5. Soft-launch with new bookings, then cut over fully within two weeks.

Want a digital waiver platform with tour operator templates and booking integrations already built? Start a 14-day free trial — most operators are live and integrated within an afternoon.