Ingest file from URL
POST /files/from-url
Authorizations
Section titled “Authorizations ”Request Body
Section titled “Request Body ”object
URL to download the file from
ID of the team that will own this file
Custom key-value metadata to attach to the file
object
Optional fetch configuration (headers, method, redirects, timeout)
object
Custom HTTP headers to send with the request
object
HTTP method to use (GET or POST)
Request body (for POST requests)
How to handle redirects
Request timeout in milliseconds (1s - 60s)
Responses
Section titled “ Responses ”File ingested successfully
object
Unique identifier for the file
ID of the team that owns this file
File name or relative path (e.g., ‘file.txt’ or ‘docs/file.txt’). Slashes preserved for directory structure.
Size of the file in bytes
MIME type of the file (e.g., text/csv, application/json)
SHA-256 hash of the file contents for deduplication
User ID of who uploaded this file, or null for system uploads
Source URL if file was ingested from a URL, or null for direct uploads
Custom key-value metadata attached to the file
object
Latest processing status for the file, or null if never processed
object
Type of the latest processing event (JOB_CREATED, JOB_STARTED, JOB_FAILED, JOB_SUCCEEDED)
When this processing event occurred
Version of the processor that handled this file
Additional event-specific data
When the file was uploaded
When the file was last modified
ID of the processing job created for this file, or null if job creation failed
Bad Request - Validation error or invalid input
object
Unauthorized - Authentication required or invalid token
object
Forbidden - Insufficient permissions
object
Bad Gateway - failed to fetch file from URL