Ingest documents (text, files, or mixed)
Unified document ingestion endpoint.
Accepts a multipart form with:
- manifest (required): JSON array describing each item
- files (optional): one or more file uploads, referenced by file_index in the manifest
Manifest format (JSON array):
[
{"type": "file", "file_index": 0, "title": "Report"},
{"type": "text", "title": "FAQ", "content": "What is..."},
{"type": "file", "file_index": 1, "title": "Old Report", "document_id": "uuid"}
]
Path parameters
Response
Successful Response
Changes
Changed in 1 of the 3 revisions of this API.6
- ○
added the optional property
retry_afterto the response with the400statusresponse-optional-property-added
- ○
added the optional property
retry_afterto the response with the401statusresponse-optional-property-added
- ○
added the optional property
retry_afterto the response with the404statusresponse-optional-property-added
- ○
added the optional property
retryableto the response with the400statusresponse-optional-property-added
- ○
added the optional property
retryableto the response with the401statusresponse-optional-property-added
- ○
added the optional property
retryableto the response with the404statusresponse-optional-property-added
This revision also has 40 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○