verify and process fareharbor booking and item webhook notifications
domain: developer.fareharbor.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
review the Webhooks section of the FareHarbor Integration Center covering the Booking Webhook, Item Webhook, and webhook best practices
share your webhook receiving url with fareharbor during integration setup — each account is issued its own unique webhook link
subscribe to Booking Webhook events to receive booking-group data (contact info, cancellation policy, created/updated/cancelled bookings)
subscribe to Item Webhook events to be notified when bookable items (activities/products) are added, updated, or removed
verify each incoming payload by computing an HMAC-SHA256 signature with your webhook secret and comparing it to the x-fareharbor-signature header before trusting the data
acknowledge receipt quickly with a 2xx response and process the payload asynchronously, handling retried deliveries idempotently
Known gotchas
webhook urls are unique per account and must be manually provided to fareharbor during setup — they are not self-configured in a dashboard
payloads must be signature-verified (x-fareharbor-signature, HMAC-SHA256) to avoid processing spoofed requests, since fareharbor does not otherwise authenticate the caller of your endpoint
webhook access sits behind the same partner/integration approval process as the rest of the external api, so it is not available to arbitrary unapproved developers
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?