Use Cases
- Collecting document uploads from users via your application
- Enabling file uploads in public-facing forms
- Gathering user-submitted files for processing in workflows
How It Works
- Your application requests a pre-signed upload URL from Cortex
- Cortex returns the upload URL and a future file ID
- Your application shares the upload URL with the end-user
- The user uploads their file directly to this URL
- The file becomes available in Cortex and can be referenced using the file ID
Creating a Pre-signed URL
upload_url
: URL where users can upload filesfuture_file_id
: ID that will be assigned to the file once uploaded
Uploading to the Pre-signed URL
Once you have the upload URL, you upload files to it:Using Uploaded Files in Workflows
After a file is uploaded, The uploaded file is now available using the future_file_id and can be referenced wherever the upload URL was created, such as when running a workflow that requires a file input, for example:File Uploads API Reference
Complete API documentation including all available parameters and response
fields