EaserixDocs
DevelopersAPI referenceSignLifecycle

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.

View as Markdown
GET
/v1/documents/{id}/audit

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/documents/string/audit"
{  "events": [    {      "id": "string",      "recipientId": "string",      "actor": "string",      "event": "string",      "detail": "string",      "ip": "string",      "userAgent": "string",      "hash": "string",      "createdAt": "2019-08-24T14:15:22Z"    }  ]}

In-person signing (owner session)

Records a signature for a signer on the owner's device — self-sign or hand-the-device signing. External signers use their tokenized link instead. Requires a PNG data-URL signature; targets the given recipientId or the first unsigned signer; enforces sequential order; zero-signer documents cannot complete. Completion triggers the same finalize path as remote signing (stamped final PDF + certificate + emails).

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.