Configure a Smartwaiver webhook to deliver signed waivers to an FEC's POS system in near real time
domain: support.smartwaiver.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set the webhook endpoint URL at the waiver template level in the Smartwaiver dashboard
Decide whether email validation is required for that template's webhook
Have Smartwaiver POST the signed waiver payload to the endpoint after submission
Process the payload and store the waiver data and PDF reference against the guest record
Fall back to polling the API for any waivers missed due to endpoint downtime
Known gotchas
The webhook POST fires within about 10 seconds of a kiosk-signed waiver, so a slow or unavailable receiving endpoint will miss that near-real-time delivery window
Webhook configuration is per-template, not account-wide, so each waiver template used at the venue needs its own endpoint set up
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?