There are couple of constraints with concurrent sessions to make them work. Finally finish the session with :route: upload_session/finish. After that, you can send file data in concurrent :route: upload_session/append:2 requests. To start a new concurrent session, set :field: ssion_type to :field: ncurrent. For better performance, you can instead optionally use a :field: ncurrent upload session. īy default, upload sessions require you to send content of the file in sequential order via consecutive :route: upload_session/start, :route: upload_session/append:2, :route: upload_session/finish calls. For more information, see the 🔗 Data transport limit page.

Attempting to use an :field: ssion_id with :route: upload_session/append:2 or :route: upload_session/finish more than 7 days after its creation will return a :field: UploadSessionLookupError.not_found.Ĭalls to this endpoint will count as data transport calls for any Dropbox Business teams with a limit on the number of data transport calls allowed per month. The maximum size of a file one can upload to an upload session is 350 GB.Īn upload session can be used for a maximum of 7 days. You can then use :route: upload_session/append:2 to add more data and :route: upload_session/finish to save all the data to a file in Dropbox.Ī single request should not upload more than 150 MB. This call starts a new upload session with the given data. Upload sessions allow you to upload a single file in one or more requests, for example where the size of the file is greater than 150 MB. Dropbox ( ) files/upload_session/start ( see docs)

Dropbox api access token