Send document (compliance-driven)
POST/v2/spaces/:spaceId/documents/:documentId:send
Preview: The API is in development or testing phases and the interface could still change slightly.
Runs the compliance check for the document, selects a connector — the first viable one, or the caller's connectorOverride — reprocesses the document when the confirmed participant identifier differs from the stored one, and triggers delivery asynchronously.
The request body is optional: an absent body, an empty body, or a body without overrides all mean "use the identifiers already on the document and the first viable connector".
202 means the request was accepted, not that the document was delivered; the delivery outcome
surfaces through the document's lifecycle events.
Scope: space_read, space_write
Request
Responses
- 202
- 400
- 403
- 404
- 422
Send document request accepted
Malformed request body
Access denied
Space or document not found
No viable connector for this delivery