EaserixDocs
DevelopersAPI referenceSignNotary

Return the sealed document

The Phase A handoff. The session ran on the notary's own registered RON technology; uploading the sealed PDF (multipart field "file", 25 MB max, validated as PDF) completes the envelope — it becomes the final artifact, the audit chain records the notary's commission, and a journal entry auto-files for the notary to review.

View as Markdown
POST
/v1/notary/requests/{id}/complete

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Request Body

multipart/form-data

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/notary/requests/string/complete" \  -F file="string"
{  "request": {    "id": "string",    "documentId": "string",    "state": "string",    "stateName": "string",    "status": "string",    "docType": "string",    "signerCity": "string",    "timingNote": "string",    "scheduledAt": "2019-08-24T14:15:22Z",    "sessionNote": "string",    "completedAt": "2019-08-24T14:15:22Z",    "created": "2019-08-24T14:15:22Z",    "notary": {      "slug": "string",      "fullName": "string",      "commissionNumber": "string",      "state": "string"    }  }}

Download the document for the session

The signed envelope PDF, available to the claiming notary only once every signer has signed (the document is awaiting notarization) — before that the notary has no business reading it (409).

My e-journal

Entries newest-first (200 max) plus the money summary: act count, notarial fees, non-notarial fees, and logged miles. The journal records ALL the notary's acts, not just Easerix sessions — it is the notary's record, exportable in full, never mined.