Upload files by URL
Authentication
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.
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.
Upload files by providing URLs from which files will be downloaded and processed asynchronously. Allowed formats are
The API accepts an array of file URLs with optional metadata for processing.
Array of file URLs to download and process.
Dual-Level Metadata Structure: Each file can have individual metadata (type, data, clientData) via the ‘info’ field within each FileUrlInfoDto. However, company can only be set at the batch level via the root ‘info’ field.
Per-File Metadata: Each file can specify its own document type, processing data, and client data. Batch Metadata: Company applies to ALL files in this request.
Batch-level metadata that applies to ALL files in this request.
Important: This is where you set company context for the entire batch. Individual files cannot override company - this is a batch-level setting only.
Use this field for:
Individual file metadata like document type, processing data, and client data should be set in each file’s ‘info’ field.