Get Temporary Upload Link
Get a one-time use temporary upload link to upload a file to a Dropbox location. This
endpoint acts as a delayed upload(). The returned temporary upload link may be used to make
a POST request with the data to be uploaded. The upload will then be perfomed with the
CommitInfo previously provided to getTemporaryUploadLink() but evaluated only upon consumption.
Hence, errors stemming from invalid CommitInfo with respect to the state of the user's Dropbox
will only be communicated at consumption time. Additionally, these errors are surfaced as
generic HTTP 409 Conflict responses, potentially hiding issue details. The maximum temporary
upload link duration is 4 hours. Upon consumption or expiration, a new link will have to be
generated. Multiple links may exist for a specific upload path at any given time. The POST
request on the temporary upload link must have its Content-Type set to
"application/octet-stream". Example temporary upload link consumption request: curl -X POST
<temporary_upload_link_url> --header
"Content-Type: application/octet-stream" --data-binary @local_file.txt A successful temporary
upload link consumption request returns the content hash of the uploaded data in JSON format.
Example successful temporary upload link consumption response: {"content-hash":
"599d71033d700ac892a0e48fa61b125d2f5994"} An unsuccessful temporary upload link consumption
request returns any of the following status codes: HTTP 400 Bad Request: Content-Type is not
one of application/octet-stream and text/plain or request is invalid. HTTP 409 Conflict: The
temporary upload link does not exist or is currently unavailable, the upload failed, or
another error happened. HTTP 410 Gone: The temporary upload link is expired or consumed.
Example unsuccessful temporary upload link consumption response: Temporary upload link has
been recently consumed.
**Required scope:** `files.content.write`
**Endpoint format:** [RPC](https://docs.dropboxapi.com/dropbox-api/docs/technical-reference/request-response-formats#rpc-endpoints)
**Authentication:** [User](https://docs.dropboxapi.com/dropbox-api/docs/auth-types#user-authentication)
Authentication
AuthorizationBearer
OAuth 2.0 token issued to a specific user. Use `Authorization: Bearer <token>`.
Public clients should use the authorization code flow with PKCE (S256).
For background or offline access, send `token_access_type=offline` during authorization and use the returned refresh token to obtain new access tokens.
You can generate a short-lived access token from the App Console; see [Testing with a generated token](https://docs.dropboxapi.com/dropbox-api/docs/oauth#testing-with-a-generated-token).
Headers
Dropbox-API-Select-User
Acts on behalf of a team member for supported user-auth operations. Pass a team member ID such as dbmid:.... When used with a team token, that token must also include the team_data.member scope.
Dropbox-API-Path-Root
Scopes path-based operations to a namespace (root). The value is a JSON serialization of the `common.PathRoot` union: `{".tag": "home"}`, `{".tag": "root", "root": "<namespace_id>"}`, or `{".tag": "namespace_id", "namespace_id": "<namespace_id>"}`. On failure the request returns 422 with a `common.PathRootError`.
Request
This endpoint expects an object.
commit_info
Contains the path and other optional modifiers for the future upload commit. Equivalent to the parameters provided to upload.
duration
How long before this link expires, in seconds.
Attempting to start an upload with this link longer than this period
of time after link creation will result in an error.
Response headers
X-Dropbox-Request-Id
A unique identifier for the request, useful for debugging and support.
Response
Successful response
link
The temporary link which can be used to stream a file to a Dropbox location.
Errors
401
Unauthorized Error
403
Forbidden Error
409
Conflict Error
429
Too Many Requests Error
500
Internal Server Error