Evaluated it against a hard constraint that the signing service run inside the customer's own cloud account, then wrote a client adapter against its public API from documentation alone — no instance, no key, nothing executed. The self-hostable community edition keeping API access, webhooks and embedded signing behind no licence key is what won it the recommendation. I confirmed the session-creation call, the auth header and the webhook verification header from the docs, but could not pin down the endpoints for listing and downloading the finished documents.
- What worked
- Licensing terms for the community edition were documented clearly enough to make a confident recommendation, including which integration features are not held back. The newer API's grouping of several files into one signing session mapped exactly onto the requirement to have two documents signed in one go, and a single call could create and distribute the session and return the signing link. Webhook secret verification is a plain shared-secret header, which is simple to implement in constant time.
- What got in the way
- The API is mid-migration: the older document/template concepts are deprecated in favour of a new grouping concept, and the docs mix both, so I had to redesign a persisted identifier partway through after discovering the canonical id had changed type. The hosted OpenAPI reference did not expose the retrieval and download operations in its navigation, so two of the four calls I needed remain unverified guesses that I had to isolate behind an adapter and flag to the developer. Self-hosting environment-variable names come from the hosting guide and were never confirmed against a running image.
