A request is Completed only after the final files exist and match their recorded digests. Until then the downloads say the files are not ready, and a request that is finishing up shows its progress: see Finishing a request.
For your team
Open the request and choose Signed PDF or Evidence bundle. You need the signing:export permission, and an API token needs the same ability.
- Signed PDF. The document with the signature marks drawn on its pages, followed by a signature page. It begins with the exact bytes of the original, so the original can still be checked against its digest.
- Evidence bundle. A ZIP file:
| File | What it is |
|---|---|
document.pdf |
The exact PDF that was signed |
signature-page.pdf |
The signature page on its own |
signed-document.pdf |
The signed PDF, as above |
evidence.json |
Sender, recipients and roles, each status, how each was verified, the time of each signature, the consent wording shown and its version, the package digest and the complete history |
manifest.json |
A machine-readable list of every file with its SHA-256 digest, the binding of each signature to its history entry, and a plain statement of the assurance level |
manifest.sha256 |
The same digests in a format sha256sum -c understands |
Every file is re-hashed against the digest recorded when the request was completed before it is served. If one no longer matches, it is not served and the problem is raised, rather than handing you something altered. Every export is written to the request's history.
For a request that was declined, voided or expired, the bundle is marked incomplete: it shows what was recorded up to that point and nothing is presented as signed.
Checking it yourself
You do not have to trust the page. Unzip the bundle and run sha256sum -c manifest.sha256, or compare the digests in manifest.json with your own. The request page and GET /api/v1/signing-requests/{id}/verify also check the history chain, and report either History intact or the first entry that does not fit.
What this shows: the files and the history are the ones recorded when the request completed. What it does not show: who a signer is beyond control of their mailbox, or the time from an independent source. The manifest says so itself, in its statement: simple electronic signature, email control checked, no qualified identity verification included.
For recipients
A recipient who signed gets an email with a link to the completed document. The link needs a new email code, then offers the signed PDF and a short summary of the names and times of those who signed. Download links work for a few minutes and every download is recorded. The completion link works for 30 days. The summary has no other signer's address or device details.
A recipient of a declined, voided or expired request sees a status page only.
After a plan change
Records you already hold stay downloadable if you move to a plan without signing, within their retention period. See Retention.
