Validate two to one hundred originals as a durable intake batch
POST/api/v1/intake-batches
Files are processed and returned in request order. The batch envelope and item identities are durable, so repeating an identical ordered request with the same Idempotency-Key resumes or replays it. A changed filename, order, or content under that key returns 409. An intake rejection has null documentId/taskId plus a bounded error. A durable acceptance always preserves non-null documentId/taskId; while processing is active its error is null, and if processing later exhausts retries the replay preserves both IDs alongside the bounded error so clients recover the existing document rather than uploading it again.
Request
Responses
- 202
- 400
- 401
- 403
- 409
- 413
- 421
- 422
- 503
Every batch item has an accepted or rejected intake result
The multipart shape or Idempotency-Key is malformed
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Duplicate content is disallowed, or an idempotency key was reused for a different request
A configured streaming body or per-file size limit was exceeded. A transport-level rejection may omit the JSON body.
The Host authority is not allowed by the loopback deployment profile
The supplied bytes, filename, declared field value, or supported-content validation failed
A required core dependency is unavailable; retry with bounded backoff