Skip to main content

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, it will be created automatically.

Uploads are atomic; it is not possible resume an interrupted upload.

In order to upload a file using the v1.2 legacy ExaVault API, it was originally necessary to first use the getFileUploadUrl function 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.

NameData TypeDescription
access_tokenstringRequired. The session key that identifies which user is authenticated. Either an access token returned by the authenticateUser function, or a a Files.com user API Key.
fileSizeintegerRequired. Size of the file to upload, in bytes.
destinationPathstringRequired. Full path, including the filename, where the file will be uploaded.
allowOverwritebooleantrue if the file should be overwritten, false if different file names should be generated.
This will override the site-wide setting for allowing overwrites.

Ready to Transform Your File Infrastructure?

Join over 4,000 organizations that trust Files.com to manage their mission-critical file flows. Start your free trial today and see why we're the #1 rated file orchestration platform.

No credit card required • 7-day free trial • Setup in minutes