Overview
Chunked uploads use a sequence of API calls.- : The application creates an upload session for a new file or new version of a file. The session defines the (new) name of the file, its size, and the parent folder.
- (optional): When uploading a new version of a file, the application sends the offset, size, and
SHA-512hash of each part. Box returns the parts it already stores, so the application can skip them. - : The application uploads the separate parts of the file as chunks. If the application planned the session, it only uploads the parts Box doesn’t already store.
- : The application commits the session. Box checks the integrity of the file, then places it in the location specified when the session was created.
Most of out of the box and remove
the complexity from the application code.
Skip parts Box already stores
A new version of a large file often shares most of its content with the previous version. Instead of uploading every part, you can plan the upload session first, so that you only upload the parts that changed. Planning is optional. For details on the plan request and response, see the .Box only reuses parts from the previous version of the same file, and only
when the user uploading the file has permission to download that version.
