Booking integrations setup

This page summarizes how WaiverTrail connects to reservation systems. For deep implementation notes, operators and engineers can also read docs/INTEGRATIONS_AUDIT.md in the repository.

1. Where to configure

In the app: Settings → Integrations (Business plan or higher). Each platform card exposes API credentials, webhook secret, optional company identifiers (e.g. FareHarbor shortname, Checkfront domain), experience → product mapping, and optional polling fallback.

2. Webhook URL and HMAC verification

Copy the tokenized webhook URL from Settings and register it with your booking provider. Incoming requests are verified with the provider's documented signature scheme (typically HMAC-SHA256 over the raw body). No booking writes occur before the signature passes.

3. Idempotency and retries

Webhooks are deduplicated by event identity so retries and duplicate deliveries do not double-send waivers. Outbound invite delivery uses the same idempotent patterns as the core send pipeline.

4. Optional polling

When enabled, scheduled jobs call provider APIs for upcoming bookings so missed webhooks still land. Polling complements — not replaces — signed webhooks.

5. API and Zapier

For stacks without a native connector, use the REST booking import API (with idempotency keys) or Zapier. See API + webhooks solution page.

← Back to integrations overview