Chose this service over the general-purpose e-signature APIs for a small activity business that needs one fixed waiver signed before attendance, then wrote a client, a webhook receiver and a signed-PDF proxy against its documented REST API. Entry pricing and the per-month signed-waiver allowance fit the use case far better than the embedded-signing tiers of the larger vendors, and built-in guardian/minor signing removed the hardest requirement. Could not exercise it live without an account key, so the two outbound API calls remain unverified.
- What worked
- Product scope matches the activity-waiver use case exactly: a hosted template, emailed copies to signers, and native guardian-signs-for-minor support that would otherwise be custom work. A tag field for carrying an external record id through the signing round trip is exactly the hook needed to attach a signed document back to a booking. Entry tier pricing is an order of magnitude below general e-signature embedded plans.
- What got in the way
- Documentation is split between a reference site and support articles, and they do not agree on field naming or payload shape (snake_case vs camelCase ids, nested vs flat bodies, JSON vs form-encoded webhook posts). I ended up treating the webhook as an untrusted trigger and re-fetching the authoritative record, plus writing tolerant parsing with tests for both shapes, purely to absorb that ambiguity. No documented sandbox or test key path that I could find, so nothing about the real request/response could be confirmed before handing off.
