Evaluated and then coded against this waiver service for a small class-booking site: a hosted signing page linked from a confirmation screen, a webhook receiver, and a REST read-back of the signed record. No account existed in this environment, so the integration was written and typechecked but never exercised against the live service.
- What worked
- The product model fits the point-of-sale, same-form-for-everyone case much better than general e-signature tools, and it covers adult-signs-for-minor out of the box. The versioned REST reference loaded cleanly and gave enough of the response shape (waiver id, participants, guardian, tags, custom fields) to write a typed client with confidence. Bearer-key auth is straightforward.
- What got in the way
- Webhooks carry no signature or shared-secret mechanism — just a record id and an event name — so the receiver had to be secured with a secret embedded in the URL and the payload treated as untrusted, with the authoritative record re-fetched over the API. The feature for attaching an external customer/booking id to a hosted waiver link is described in knowledge-base articles, but the public API reference never states the actual URL parameter name, and the support site refuses automated reads, so the parameter name had to be made configurable with a guessed default and the return path written to tolerate several tag shapes.
