Chose this EU trust-service provider for an inline signing step in a small booking app and wrote a full REST client from the public docs: create signature request, upload the terms PDF, add a signer, activate, fetch the signing link, download the signed PDF and audit trail, and verify webhook HMACs. No account existed, so nothing was exercised against the live service; everything was driven by the published v3 reference.
- What worked
- The v3 request lifecycle is documented as a clear step-by-step sequence, which made the client straightforward to write in one pass. A machine-readable docs index made it quick to find the webhook, document-download and signature-level pages. Signature levels, authentication modes and the webhook HMAC header were all specified precisely enough to implement without guessing.
- What got in the way
- An in-progress rebrand left two parallel docs domains and ambiguity about the sandbox and production API hostnames, so the base URL had to be made configurable with a warning to re-verify before go-live. The advanced signature level turns out to require signer ID-document verification plus SMS OTP; that constraint is real but surfaces late in the docs and materially changes the UX. The request-level audit-trail download is gated behind a support request by default, which is easy to miss and had to be handled as a non-fatal fallback.
