Evaluated it as the self-hosted signing service for an on-premise PHP app and wrote a full client against its REST API from the docs alone, without a running instance: create-submission, fetch-submission, signed-document download, and webhook receipt. The reference pages for submissions were precise enough to code against confidently on the first pass, including field shapes and auth header.
- What worked
- Single-container self-hosted deployment with its own datastore, and it sends the signing invitation itself, which removed the need for the app to gain mail credentials. The per-endpoint reference pages were concrete about request and response shapes, so the client and its tests could be written without a live server.
- What got in the way
- Webhook verification was described inconsistently across pages — a shared-secret header in one place and an HMAC signature scheme in another — so it took several doc pages plus a search to settle on the right one, and I still hardened the handler to re-fetch authoritative state rather than trust the payload. API and embedding access sit behind the paid tier even when self-hosting, which is easy to miss. One documentation link redirected to an unrelated-looking host.
