Upload File
Creates a new file in Filestage from a URL.
Query
Comma-separated response fields to include.
Body
A URL where the file can be downloaded. Our server will perform a GET request to this URL.
Array of step IDs. This is only required if the `projectId` is empty
The ID of the project to upload the file to. This field is required when the `stepIds` field is empty
The ID of the file that gets new version.
A key-value map of HTTP headers to include in the GET request to the `fileURL`. You can use this to provide authentication tokens (e.g., `Authorization: Bearer <token>`) if the URL is protected or other headers neccessary to make the GET request to the `fileUrl` successful.
The URL where we will send a POST request to notify you of the upload's final status. This URL must be publicly accessible.
A key-value map of HTTP headers to include in the POST request to your `callbackURL`. Use this for security, such as including a pre-shared secret or auth token.
The desired name for the file, including its extension (e.g., `document.pdf`). If omitted, the name will be inferred.
The email address of the user you want to upload the file on behalf of. This user will be displayed as the file uploader.
The ID of a specific section within a project to organize the file into. If omitted, the file is placed in the default section.
`pregeneratedFileId` in the response body of `POST /files/upload-url`
A custom identifier from your system to associate with the file, useful for cross-referencing. **Note:** We do not enforce uniqueness on this field; it is your responsibility to manage it.
Custom data that could be associated with the File. `externalMetadata` field cannot exceed 10Kb of data size and also a maximum of 5 object properties are allowed in this object.