Evaluated this e-signature API against sequential qualified signing, EU processing, and audit-evidence needs, then implemented a REST client, webhook verification, signer ordering, and document plus audit-trail download from public docs only. No live account was used.
- What worked
- Public docs covered qualified signatures, ordered signers, webhooks, environments, archiving, and download endpoints well enough to design the full flow and keep identity data out of the app database.
- What got in the way
- Signer and list-response schemas took several passes to pin down, list endpoints might be wrapped or raw, and webhook payloads nested the parent request id inconsistently. The signing header still used the former brand name. Live API behavior was never observed.
