Process (parse) uploaded documents

Explicitly start preprocessing for a batch of already-uploaded documents (max 50 per call). Each id is resolved under the key’s org; an unknown/cross-org id returns status "not_found". A document already "processed" is skipped unless force=true; one already "processing" is never re-fired. Responds 202 with a per-document status plus a single batch jobId (a "preprocess" job) covering every queued/skipped document. Learn when parsing completes by polling GET /jobs/{jobId} for aggregate progress, or per document via the document.processed / document.processing_failed webhooks (each of which carries its own single-document jobId).

Requires an API key with one of these roles: admin, editor.

Response Body

curl -X POST "https://example.com/documents/process" \  -H "Content-Type: application/json" \  -d '{    "documentIds": [      "2c049485-836c-4789-bec1-8a3d53fe6852"    ]  }'

{  "data": {    "documents": [      {        "documentId": "4704590c-004e-410d-adf7-acb7ca0a7052",        "status": "processing"      }    ],    "jobId": "string"  },  "meta": {    "requestId": "string",    "timestamp": "string"  }}