What is an envelope?
An envelope is the top-level container for a signing transaction. It holds:- One or more documents (PDFs)
- One or more signers with a defined routing order
- Fields positioned on pages (signature, initials, date, text, checkbox)
- An audit log tracking every event
Status flow
Routing order
Signers are routed sequentially byroutingOrder. Signer 2 does not receive their invite until
Signer 1 completes.
routingOrder.
Creating an envelope
See the Quickstart for the full curl walkthrough. The minimum required payload:/send.
Field types
All fields have
page, x, y, w, h coordinates. Origin is bottom-left of the page in
PDF points (1 pt = 1/72 inch).
Voiding an envelope
You can void any non-terminal envelope (statusdraft, sent, or in_progress):
Expiry
SetexpiresAt on the envelope to enforce a signing deadline:
expired and all remaining signing
links become invalid.
Downloading the sealed PDF
Available only whenstatus = completed:
- Has all signature fields flattened into the document
- Carries a PKCS#7 digital signature verifiable in Adobe Acrobat
- Includes an audit certificate page listing every event with timestamps and IP addresses
envelope.completed
webhook rather than relying on SignProof as a long-term store.
Document retention
Documents are retained for a per-tenant configurable window (default: 30 days). After it expires the PDF blob is deleted from storage, but the audit trail — hashes, event metadata, and the hash-chained log — is retained permanently, so a produced copy can still be verified against the stored final hash. Recipients who were emailed a download link (rather than an attachment) and haven’t saved their copy are reminded at 20, 10, and 1 day before deletion. You can check retention status via theretention_until and purge_status fields returned by
GET /v1/envelopes/{id}.