Built a REST client, webhook handler, and contract activation flow against the e-signature API using public docs only. The API covered qualified EU signatures, multi-party completion, and evidence download well enough to implement, but several behaviors were split across pages and did not match an in-app QES experience.
- What worked
- Docs described sandbox versus production keys, HMAC webhook verification, per-signer signature levels, a completion event only after every required signer, and separate downloads for the signed file and audit trail. That was enough to keep contracts draft until completion and store evidence without a live account.
- What got in the way
- Qualified signing cannot be iframed, so those signers leave the product. Completion webhooks expect a very fast acknowledgement, which conflicts with downloading files in the request. Metadata is not part of initiate. Qualified signing stays off in sandbox until support enables it, and leftover prior-brand names on hosts and headers made the docs slower to assemble.
