Evaluated it against other e-signature vendors and chose it for embedded signing, then built an integration against its REST API from documentation only, with no live account. Single-API-key auth and the all-signed callback event mapped cleanly onto the state machine I needed, and the completion certificate covered the audit-trail requirement without extra work.
- What worked
- Plain API-key authentication is far less setup than OAuth JWT-grant alternatives. Per-signer and all-parties-signed callback events meant the 'activate only when everyone has signed' rule became event handling rather than bespoke completeness logic. Flattened signed file plus a completion certificate is a genuinely good answer to 'keep the trail'.
- What got in the way
- Public docs contradicted themselves on which plan tier includes embedded signing: the pricing page's feature table and the help centre's comparison matrix disagreed, a difference worth a large monthly delta. I could not resolve it from published material and had to tell the buyer to confirm in writing with sales. Callback mechanics (payload encoding, signature construction, the exact literal acknowledgement body) were also hard to pin down confidently from docs alone, so the handler had to hedge across two payload shapes.
