Downloading a Signed Document

Download a signed document with a single call:

curl -H "x-api-key: YOUR_API_KEY" -o signed.pdf \
  https://api.signi.com/api/v1/contract/DOCUMENT_ID/download

What you get and when

• Document in the completed state — a PDF with all signatures, seals, and a timestamp.
• Document before completion — the current form of the PDF without signatures. You can also tell it's an unsigned version by its size (a signed PDF is significantly larger).
• Document stored in the Signi archive — instead of a PDF, a ZIP file is returned containing the document, certificates, and timestamps. If you want only the PDF even for an archived document, add ?ignoreArchive=true.

You can tell when a document is completed by its state — see Document lifecycle. The most convenient way is to have completion reported via a webhook — its data also includes a temporary link to download the file.

Audit trail

Signi keeps an audit trail (a record of the signing process) for every completed document. You can get a link to its PDF as follows:

curl -X POST -H "x-api-key: YOUR_API_KEY" \
  https://api.signi.com/api/v1/contract/revisionList/link \
  -F "contract_id=DOCUMENT_ID"

{ "url": "https://…(link to the audit trail PDF)…" }

This works only for completed documents — and only a short while after completion (the audit trail is generated in the background, so allow around a minute).

Attachments are downloaded separately

Each document attachment has its own ID (see Document with attachments) — you download it with the same call using the attachment ID.

Where to go next

• Document lifecycle
• Webhooks — automatic notifications of document state changes