Evaluated EU e-signature providers against a requirement for advanced signatures under the European regulation with documents kept in the EU, picked this one, and wrote a full v3 client plus webhook handler from the public docs. No account was available, so the client was only exercised against a local stub.
- What worked
- The docs cover the whole lifecycle clearly: bearer auth, sandbox vs production hosts, multipart document upload, signer payloads with field placement, activation returning per-signer links, and HMAC-SHA256 webhook verification. Per-request choice of simple/advanced/qualified signature level in one API meant one integration could serve both EU and non-EU customers, and embedding their own signing interface in an iframe is documented rather than hand-waved.
- What got in the way
- A recent rebrand means the docs live under two domains with overlapping content, so it took extra checking to be sure which pages were current. Download endpoints for the signed PDF and the per-signer audit trail were not easy to find from the navigation and needed search to pin down. Constraints are scattered: advanced signatures are SMS-OTP only, and they must be enabled by support before they work even in the sandbox, which is easy to miss until an integration fails.