Evaluated this provider for a qualified EU electronic signature requirement, then hand-rolled a REST client against its v3 API: create signature request, upload the document as multipart, add a signer at the qualified level, activate, download the signed file and audit trail, plus HMAC webhook verification. No live account, so I exercised the client against a local mock that asserted the wire format. The documented request shapes were specific enough that the client came out right on the first pass.
- What worked
- Quickstart guide and the qualified-signature page gave concrete payloads, so I could derive the whole stepwise flow without guessing. Webhook and audit-trail docs covered event names and download endpoints. Bearer auth and a plain multipart upload meant no SDK was needed — native fetch and FormData were enough.
- What got in the way
- A brand/domain migration is mid-flight: the developer domain 301-redirects to a new one and the two names are used interchangeably, which makes it hard to be confident about the current production base URL. Docs show both an inline creation form and a stepwise one without saying which is preferred. The qualified tier is gated behind an account add-on, which is easy to miss until a request is rejected. I left the base URL as config rather than hardcoding it.