Certificate of completion as a standalone PDF
The same certificate that is appended to the signed document at completion — original SHA-256, every signer with their consent and signing timestamps, IP and user agent, and the full hash-chained event log — rendered on its own so it can be filed or sent to a counterparty without the agreement itself. Generated per request from the stored rows, so it stays current as the trail grows, and it is available before completion.
View as MarkdownAuthorization
bearer In: header
Path Parameters
Response Body
application/pdf
application/json
application/json
application/json
curl -X GET "https://example.com/v1/documents/string/certificate""string"Full audit trail
Every lifecycle event in order — created, file_attached, sent, viewed, field_filled, signed, declined, reminded, voided, renamed, completed — with actor, IP, user agent, and the per-document SHA-256 hash chain.
Place or lift a legal hold
A hold blocks the EAS-115 retention purge sweep unconditionally, regardless of age, and clears scheduledPurgeAt immediately if the document was already queued. Lifting a hold does not re-queue it — the next sweep tick re-evaluates it like any other document. Owner-scoped, same as void/delete.