Chose this EU-based provider for a regulated signature requirement and wrote a full client against its documented v3 flow (create request, upload document, add signer with field coordinates, activate), plus a webhook receiver and an on-demand signed-document download. No account was available, so nothing was exercised against the live service.
- What worked
- The documented signing flow is explicit and maps cleanly onto a four-call sequence, with activation as a distinct step so nothing reaches a signer prematurely. Signature levels, signer authentication modes and a no-legal-value sandbox are all first-class, which made the compliance story easy to encode as configuration. Webhook docs covered the HMAC header and event names well enough to implement verification and dedup.
- What got in the way
- A recent rebrand left the developer portal redirecting to a new domain while the API host still carries the old brand, so I had to re-fetch docs and confirm the rename before trusting anything. Several specifics — the signed-document download endpoint, the exact webhook header name and event identifiers — needed extra searching rather than being obvious from the main guides.
