Check whether a document is ready to send
Runs the checks POST /api/v1/documents/{id}/send runs before it sends, without sending. ready is true when no BLOCKER remains. Each issue has a code, such as MISSING_EMAIL or NO_EXPIRATION, an English message, and a Swedish userMessage that names the party or field.
When a send fails the same checks, it returns an HTTP 409 Conflict status code with code DOCUMENT_NOT_READY and this list in readiness.
AuthorizationBearer <token>API key, e.g. Authorization: Bearer sajn_svc_.... Not scope-limited: acts with its owner's workspace role.
id*stringThe document ID.
Sajn-Version?stringAPI 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"Sajn-Workspace?stringID 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.
200
application/json- response
ready*booleanTrue when nothing blocks sending the document; warnings can remain.
issues*array<>Blockers first, then warnings
curl -X GET 'https://app.sajn.se/api/v1/documents/cm4k2x9p10003abcd1234efgh/readiness'{ "ready": false, "issues": [ { "code": "MISSING_PHONE", "severity": "BLOCKER", "message": "A party invited by SMS has no phone number.", "userMessage": "Kai Lindqvist saknar telefonnummer för SMS-leverans." } ]}Was this page helpful?