Upload a File
Summary
Upload a file to your site. The authenticated user must have write permissions. If you provide a folder path that does not exist, the API creates it automatically.
Uploads are atomic. You cannot resume an interrupted upload.
The v1.2 legacy ExaVault API originally required calling getFileUploadUrl first to generate a target URL, and legacy code may still use that function.
Endpoint
POST https://mysite.files.com/v1.2/upload
Replace mysite.files.com with your site address.
Request Parameters
All of the parameters listed below are query parameters. The body of the request should contain only the bytes to be uploaded for the file.
| Name | Data Type | Description |
|---|---|---|
access_token | string | Required. The session key that identifies which user is authenticated. Either an access token returned by the authenticateUser function, or a Files.com user API Key. |
fileSize | integer | Required. Size of the file to upload, in bytes. |
destinationPath | string | Required. Full path, including the filename, where the file will be uploaded. |
allowOverwrite | boolean | true to overwrite an existing file at the destination path, false to generate a different file name instead. Overrides the site-wide setting for allowing overwrites. |
Get The File Orchestration Platform Today
4,000+ organizations trust Files.com for mission-critical file operations. Start your free trial now and build your first flow in 60 seconds.
No credit card required • 7-day free trial • Setup in minutes