Complete a document before every party has signed
Complete a sent document now and seal it with the signatures it has. Use it when a party will never sign and the signatures already collected are enough. It can’t be undone.
Status Requirements:
- Document must be in
PENDINGorEXPIREDstatus, and at least one party must have signed. Otherwise it returns409 INVALID_STATE.
Permissions:
- Requires the
FORCE_COMPLETE_DOCUMENTworkspace permission.
Request Body:
reason(optional) - Free-text reason, stored on the audit log.
What happens when you complete:
- Pending reminders are cancelled
- The document is sealed in the background with the signatures it has
- Each party that didn’t sign is emailed that the document was completed without them
- The
document.completedwebhook is triggered once the document is sealed
Response: Returns the document in the same shape as GET /api/v1/documents/{id}, without fields. Sealing runs in the background, so the status is still PENDING or EXPIRED until document.completed arrives.
Authorizations
Personal API key, e.g. Authorization: Bearer sajn_sk_.... Not scope-limited — acts as the issuing user.
Headers
API version for this request. Without it, the request uses the organization's default version; an organization without a default is pinned to the latest version by its first request.
2026-09, 2026-10 ID of the workspace this request acts in, from GET /api/v1/workspaces. Without it, an API key acts in its default workspace. The token's user must be a member of the workspace; an OAuth token only accepts the workspace it was granted for. A workspace that doesn't exist or can't be reached returns 403 WORKSPACE_ACCESS_DENIED.
Makes retries safe. A retry with the same key and the same request replays the stored response for 24 hours (header Idempotent-Replayed: true); the same key with a different request returns 400.
255Path Parameters
The document ID.
Body
Body
Complete a PENDING or EXPIRED document before every party has signed. Seals it with the signatures it has.
Optional reason for completing the document before every party has signed. Stored on the audit log.
Response
200
Unique document identifier
Your external reference ID for this document
Date and time when the document expires
Document name/title
Document status
DRAFT, PENDING_APPROVAL, PENDING, COMPLETED, EXPIRED, CANCELLED, REJECTED, IMPORTED Document metadata including subject, message, signing order, etc.
Date and time when the document was created
Date and time when the document was last updated
Date and time when all signers completed signing
Date and time when the document moved to the trash, or null when it isn't in the trash
ID of the template the document was created from, or null
ID of the folder that holds the document, or null at the top level
ID of the workspace member responsible for the document
Array of document parties (signers and other participants).
Content blocks in position order when you pass expand=content, and null otherwise. See the content endpoints for the per-type shapes.
Every product table on the document, resolved: each row carries the recipient's final selected state and quantity, and the totals count the selected rows only. Empty when the document has no product table.
ID of the document's approval request, or null when it has none. To read it, call GET /api/v1/approval-requests/{id}.
ID of the bundle the document was sent in, or null. Every document in a bundle also fires its own events, so this is the key that groups them. To read the bundle, call GET /api/v1/bundles/{id}.

