Validate an immutable original and enqueue its core processing
POST/api/v1/documents
The Idempotency-Key is scoped to the authenticated household member. Repeating the same key and semantic request returns the original documentId and taskId; reusing it for different content returns 409. By default, an already-ingested checksum returns 409 unless allowDuplicate is true. A 202 response means durable acceptance only; poll the returned taskId.
Request
Responses
- 202
- 400
- 401
- 403
- 409
- 413
- 415
- 421
- 422
- 503
Original and processing task durably accepted, or an identical idempotent request replayed
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 file is not one of the explicitly supported actual content types
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