Skip to main content

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 by routingOrder. Signer 2 does not receive their invite until Signer 1 completes.
To send to all signers simultaneously, give them the same routingOrder.

Creating an envelope

See the Quickstart for the full curl walkthrough. The minimum required payload:
Then upload the PDF and place fields before calling /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).
Use the visual field placer in the Console (/envelopes/{id}/place) to position fields by dragging without calculating coordinates manually.

Voiding an envelope

You can void any non-terminal envelope (status draft, sent, or in_progress):
Voiding is permanent. The voided event is recorded in the audit log.

Expiry

Set expiresAt on the envelope to enforce a signing deadline:
When the deadline passes, the envelope status transitions to expired and all remaining signing links become invalid.

Downloading the sealed PDF

Available only when status = completed:
The downloaded PDF:
  • 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
This integration endpoint works any time within the retention window. On completion SignProof also emails every party the sealed copy automatically — attached if it’s small, or a secure download link if it’s too large to attach. Archive the PDF to your own system on the 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 the retention_until and purge_status fields returned by GET /v1/envelopes/{id}.