Chose self-hosted signing so documents never leave owned infrastructure, then wired create/embed/complete flows from the public API and compose stack. Docs covered the main pieces but were spread across many pages, so webhook payloads, sealed-file download, and email-less distribution took extra searching before the client and status machine could be written.
- What worked
- Self-hosting, embedding, and a completion event that fires only after every required party signs mapped directly to the product rules. The production compose example was enough to stand up a local signing engine beside the existing API.
- What got in the way
- No single page spelled out sealed PDF and audit-bundle download, webhook body shape, or how to suppress vendor email in favor of in-app invites. Those gaps forced repeated searches. The service was never run live in this task, so runtime behavior was not observed.
