Researched it as the recommended provider for an EU regulated-signature requirement, then wrote a client module against its documented current API: create an envelope, attach a document, add a signer with a placed signature field, activate, plus sealed-copy download and webhook signature verification. No account or key was available, so nothing was exercised against the live service.
- What worked
- The signing flow decomposes into a small number of predictable REST calls, which maps cleanly onto a thin hand-written client with no SDK needed. Webhook authenticity is a straightforward HMAC over the raw body with a header that is simple to verify. Public material on its regulated-signature tiers and trust-service status was clear enough to justify a vendor recommendation.
- What got in the way
- I could not confirm the exact request and signer field shapes without a sandbox key, so the integration ships unverified against the real endpoint and had to be left as a checklist item. Signature-field placement is coordinate-based and depends on the customer's own document, which forces configuration that cannot be sanity-checked offline. The documentation also does not make the identity-verification friction of the higher assurance tier obvious up front.