Chose this provider for an ordered two-party signing flow at advanced-signature level with EU-hosted files, then wrote a full HTTP client against the public docs: create request, upload document, add signers with identity/OTP settings, activate, download signed file and audit trail, cancel, plus webhook signature verification. Never exercised against a live or sandbox account, so the integration is doc-derived only.
- What worked
- The public documentation on signature levels was easy to find and clear about what each level requires in terms of identity verification, which made the level choice defensible. Ordered signing, webhook signing of the request body, audit-trail artefacts and the European hosting story were all documented well enough to design around. A sandbox base URL exists and is documented, which made it natural to keep live and test endpoints separate in config.
- What got in the way
- Without an account there was no way to confirm exact endpoint paths, request field names or response shapes, so the client and its test fakes encode assumptions that the test suite cannot falsify. The relationship between signature level, required signer fields and permitted authentication modes took several passes across pages to pin down; a single worked end-to-end example for an ordered, advanced-level request would have removed most of that.