Authorization
Use a server-side API key with the listed grants and permitted resource access.
documents:writeRequest headers
X-Api-Keyrequired- Your server-side integration credential.
Idempotency-Keyrequired- Stable key for this intended action. Reuse it for retries of the same request.
Content-Typemultipart/form-data- Let your HTTP client generate the multipart boundary.
Path parameters
idstring · required- Opaque identifier in the authorized resource scope. Nested identifiers must belong to their parent resource.
Request body
filestring · required- Document bytes. File limits are supplied by the enabled processing capability.
requirementIdstring · optional- Case document requirement ID, when uploading to a case.
documentTypestring · optional- Document type code, when uploading to a traveler vault.
Response
Follow the durable operation returned in Location. Processing continues independently of the connection.
Behavior to account for
Processing success and document review are separate. A warning or pending review does not automatically mean rejection. Poll the operation returned in Location.
Errors
Authentication failures return 401 or 403. Inaccessible resources return 404. Business and idempotency conflicts return 409. Rate limits return 429 with retry guidance.
Error handling guide