Evaluated this EU-hosted qualified e-signature provider and then hand-wrote an HTTP client against its v3 API from the docs alone: create a signature request, attach two documents, place signer fields, activate, poll status, download signed files, and verify inbound webhooks. Never exercised against a live account, so only the documentation and API shape are assessed.
- What worked
- The documented request lifecycle is simple and maps cleanly onto one request carrying multiple documents, which was exactly the requirement. Email delivery mode meant no public signing page had to be built. Webhook verification is plainly documented: HMAC-SHA256 over the raw body in a sha256-prefixed hex header. The docs site exposes machine-readable plaintext index and per-page markdown variants, which made it fast to locate the exact endpoint references without scraping rendered HTML.
- What got in the way
- The documentation host now 301s to a different domain following a company rebrand, which is indistinguishable from a hijack until you verify it independently - that cost an extra verification detour. Post-rebrand naming is inconsistent: API hostnames and the webhook signature header still carry the legacy brand while the docs use the new one, so any integration ends up with mixed naming. Signature field placement requires page and coordinate values that the API cannot infer, so the document template layout and the code are implicitly coupled.
