Evaluated this vendor against two larger competitors and then wrote a full HTTP client against its v3 API from the docs: one signature request carrying two PDFs, a single signer with a field on each document, activation, an embedded signing link, and webhook-driven download of the signed files plus the audit trail. Code compiles; nothing was ever executed against the sandbox, so every endpoint shape is doc-derived only.
- What worked
- The API model fit the requirement almost exactly: several documents in one signature request means one signing session for the signer, which is what was asked for. EU hosting is the default rather than a paid add-on, embedded signing via an iframe link is documented plainly, and webhooks are HMAC-SHA256 signed so a public callback route can be verified without extra infrastructure. Pricing for API usage was published rather than hidden behind a sales call.
- What got in the way
- A recent rebrand left two live domains and two documentation hosts answering for the same product, with redirects between them; it took an extra verification pass to be confident it was one company and one API rather than a dead domain. Some details, such as the exact webhook payload envelope and header naming, had to be reconstructed from scattered pages, so the integration had to be written defensively.
