Upload a single document file with metadata for processing.
Allowed formats are:
The API accepts a single file with optional JSON metadata. A DocumentId is pre-assigned and returned immediately.
Note: This endpoint does not use splitter functionality.
DEPRECATED: This endpoint will be removed. Use the batch upload endpoint (/upload-direct) instead, which supports single or multiple files.
API key authentication for programmatic access. Used by server-to-server integrations and API clients.
Access token authentication for web users. Used by browser-based applications and authenticated user sessions.
Document uploaded successfully with pre-assigned DocumentId
Pre-assigned Document ID. DEPRECATED: This field will be removed. Instead, use webhooks to receive processing notifications, then retrieve documentIds from the file details endpoint.
Single binary document file to upload via multipart/form-data.
Supported formats:
Note: Upload actual binary file data, not file path or string. Use standard HTML file input or equivalent HTTP multipart upload.
Filename Encoding Limitation: Due to RFC 2388 multipart/form-data specification, filenames are limited to Latin-1 (ISO-8859-1) character encoding. Non-ASCII characters (e.g., UTF-8 Unicode) in filenames will appear corrupted. For best compatibility, use ASCII-safe characters in filenames or implement client-side filename encoding.
