Evaluated and then integrated a hosted waiver service into a small class-booking site: a tagged hosted signing link, a webhook receiver, and a server-side read-back of the signed waiver. No account existed, so nothing was exercised against the live service; everything was built from published docs plus the vendor's own open-source SDK source.
- What worked
- The product is purpose-built for this use case rather than adapted to it: native handling of a minor signing with an adult guardian, a participant database, and a hosted signing page meant almost no custom legal logic. Public pricing was easy to confirm. The auto-tag parameter made it simple to correlate a signature back to a booking row. The vendor publishing an SDK with typed field classes was the saving grace for pinning exact response and webhook field names.
- What got in the way
- The help-center articles describing auto-tagging and webhooks blocked automated fetching, so the authoritative field names had to be reverse-read from SDK source instead of documentation. Webhook payloads are not signed, so the only available authentication is a shared secret appended to the callback URL, which forced a design where every stored field is re-read over the authenticated API rather than trusted from the POST body. Webhook payload shape differed between the polling queue and the direct POST, which took extra cross-checking to resolve.
