Version 1.1
Connector Overview: This page documents all 192 actions for the Dropboxconnector v1.1.
Account
POST set_profile_photo
/account/set_profile_photo
set_profile_photo
scope: account_info.write
Sets a user's profile photo.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Auth (2)
POST token/from_oauth1
/auth/token/from_oauth1
token/from_oauth1
scope: None
Creates an OAuth 2.0 access token from the supplied OAuth 1.0 access token.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The OAuth 1.0 token to be converted. |
|
|
The OAuth 1.0 token secret associated with the token. |
POST token/revoke
/auth/token/revoke
token/revoke
scope: None
Disables the access token used to authenticate the call.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Check (2)
POST app
/check/app
app
scope: None
This endpoint performs App Authentication, validating the supplied app key and secret, and returns the supplied string, to allow you to test your code and connection to the Dropbox API. It has no other effect. If you receive an HTTP 200 response with the supplied query, it indicates at least part of the Dropbox API infrastructure is working and that the app key and secret valid.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A query string to include in the check request for debugging purposes. |
POST user
/check/user
user
scope: None
This endpoint performs User Authentication, validating the supplied access token, and returns the supplied string, to allow you to test your code and connection to the Dropbox API. It has no other effect. If you receive an HTTP 200 response with the supplied query, it indicates at least part of the Dropbox API infrastructure is working and that the access token is valid.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A query string to include in the check request for debugging purposes. |
Contacts (2)
POST delete_manual_contacts
/contacts/delete_manual_contacts
delete_manual_contacts
scope: contacts.write
Removes all manually added contacts. You'll still keep contacts who are on your team or who you imported. New contacts will be added when you share.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST delete_manual_contacts_batch
/contacts/delete_manual_contacts_batch
delete_manual_contacts_batch
scope: contacts.write
Removes manually added contacts from the given list.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
An array of email addresses identifying the manual contacts to delete. |
Devices (4)
POST devices/list_member_devices
/team/devices/list_member_devices
devices/list_member_devices
scope: sessions.list
List all device sessions of a team's member.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (4)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the team member whose devices to list. |
|
|
Whether to include web session devices in the results. |
|
|
Whether to include desktop client devices in the results. |
|
|
Whether to include mobile client devices in the results. |
POST devices/list_members_devices
/team/devices/list_members_devices
devices/list_members_devices
scope: sessions.list
List all device sessions of a team.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST devices/revoke_device_session
/team/devices/revoke_device_session
devices/revoke_device_session
scope: sessions.modify
Revoke a device session of a team's member.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The type of session to revoke (e.g., web, desktop, mobile). |
|
|
The unique identifier of the session to revoke. |
|
|
The team member ID associated with the session. |
POST devices/revoke_device_session_batch
/team/devices/revoke_device_session_batch
devices/revoke_device_session_batch
scope: sessions.modify
Revoke a list of device sessions of team members.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Download
GET Download Asset
x-oneteg-downloader-path-with-authorization
Download a file or asset from Dropbox using a pre-signed URL with authorization. Use this action to retrieve file content directly.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The HTTP method to use for the download request. |
|
|
The pre-signed download URL for the asset. |
|
|
The name to assign to the downloaded asset. |
|
|
Number of download retry attempts. |
|
|
Read timeout in seconds for the download. |
|
|
Connection timeout in seconds for the download. |
|
|
This toggle enables you to load file content as the step output. Supported formats include JSON, XML, YML/YAML, CSV, TXT, and other text-based file types. Note that images, PDF files, and other binary formats cannot be loaded. Additionally, there is a file size limit for this feature; please check the logs for details. |
|
|
Enable or disable following URL redirects. If it is enabled, it will follow the URL redirects. |
|
|
Additional HTTP header name/value pairs to include in the request. |
File_properties (16)
POST properties/add
/file_properties/properties/add
properties/add
scope: files.metadata.write
Add property groups to a Dropbox file. See templates/add_for_user or templates/add_for_team to create new templates.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder to add properties to. |
POST properties/overwrite
/file_properties/properties/overwrite
properties/overwrite
scope: files.metadata.write
Overwrite property groups associated with a file. This endpoint should be used instead of properties/update when property groups are being updated via a "snapshot" instead of via a "delta". In other words, this endpoint will delete all omitted fields from a property group, whereas properties/update will only delete fields that are explicitly marked for deletion.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to overwrite. |
POST properties/remove
/file_properties/properties/remove
properties/remove
scope: files.metadata.write
Permanently removes the specified property group from the file. To remove specific property field key value pairs, see properties/update. To update a template, see templates/update_for_user or templates/update_for_team. To remove a template, see templates/remove_for_user or templates/remove_for_team.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder to remove properties from. |
|
|
An array of property template IDs to remove. |
POST properties/search
/file_properties/properties/search
properties/search
scope: files.metadata.read
Search across property templates for particular property field values.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The authorization token for the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A filter to narrow the search to a specific property template. |
POST properties/search/continue
/file_properties/properties/search/continue
properties/search/continue
scope: files.metadata.read
Once a cursor has been retrieved from properties/search, use this to paginate through all search results.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST properties/update
/file_properties/properties/update
properties/update
scope: files.metadata.write
Add, update or remove properties associated with the supplied file and templates. This endpoint should be used instead of properties/overwrite when property groups are being updated via a "delta" instead of via a "snapshot" . In other words, this endpoint will not delete any omitted fields from a property group, whereas properties/overwrite will delete any fields that are omitted from a property group.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
POST templates/add_for_team
/file_properties/templates/add_for_team
templates/add_for_team
scope: files.team_metadata.write
Add a template associated with a team. See properties/add to add properties to a file or folder.
Note: this endpoint will create team-owned templates.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The name of the new property template. |
|
|
A description of the property template. |
POST templates/add_for_user
/file_properties/templates/add_for_user
templates/add_for_user
scope: files.metadata.write
Add a template associated with a user. See properties/add to add properties to a file. This endpoint can't be called on a team member or admin's behalf.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The name of the new property template. |
|
|
A description of the property template. |
POST templates/get_for_team
/file_properties/templates/get_for_team
templates/get_for_team
scope: files.team_metadata.write
Get the schema for a specified template.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the template to retrieve. |
POST templates/get_for_user
/file_properties/templates/get_for_user
templates/get_for_user
scope: files.metadata.read
Get the schema for a specified template. This endpoint can't be called on a team member or admin's behalf.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the template to retrieve. |
POST templates/list_for_team
/file_properties/templates/list_for_team
templates/list_for_team
scope: files.team_metadata.write
Get the template identifiers for a team. To get the schema of each template use templates/get_for_team.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST templates/list_for_user
/file_properties/templates/list_for_user
templates/list_for_user
scope: files.metadata.read
Get the template identifiers for a team. To get the schema of each template use templates/get_for_user. This endpoint can't be called on a team member or admin's behalf.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST templates/remove_for_team
/file_properties/templates/remove_for_team
templates/remove_for_team
scope: files.team_metadata.write
Permanently removes the specified template created from templates/add_for_user. All properties associated with the template will also be removed. This action cannot be undone.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the template to remove. |
POST templates/remove_for_user
/file_properties/templates/remove_for_user
templates/remove_for_user
scope: files.metadata.write
Permanently removes the specified template created from templates/add_for_user. All properties associated with the template will also be removed. This action cannot be undone.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the template to remove. |
POST templates/update_for_team
/file_properties/templates/update_for_team
templates/update_for_team
scope: files.team_metadata.write
Update a template associated with a team. This route can update the template name, the template description and add optional properties to templates.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the template to remove. |
|
|
The name of the new property template. |
|
|
A description of the property template. |
POST templates/update_for_user
/file_properties/templates/update_for_user
templates/update_for_user
scope: files.metadata.write
Update a template associated with a user. This route can update the template name, the template description and add optional properties to templates. This endpoint can't be called on a team member or admin's behalf.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The unique ID of the template to remove. |
|
|
The name of the new property template. |
|
|
A description of the property template. |
File_requests (8)
POST count
/file_requests/count
count
scope: file_requests.read
Returns the total number of file requests owned by this user. Includes both open and closed file requests.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST create
/file_requests/create
create
scope: file_requests.write
Creates a file request for this user.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The title of the file request, displayed to recipients. |
|
|
The path in the Dropbox where uploaded files will be stored. |
|
|
If true, the file request will be open immediately upon creation; if false, it will be closed. |
POST delete
/file_requests/delete
delete
scope: file_requests.write
Delete a batch of closed file requests.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A list of file request IDs to delete. |
POST delete_all_closed
/file_requests/delete_all_closed
delete_all_closed
scope: file_requests.write
Delete all closed file requests owned by this user.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST get
/file_requests/get
get
scope: file_requests.read
Returns the specified file request.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to retrieve. |
POST list
/file_requests/list_v2
list
scope: file_requests.read
Returns a list of file requests owned by this user. For apps with the app folder permission, this will only return file requests with destinations in the app folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
POST list/continue
/file_requests/list/continue
list/continue
scope: file_requests.read
Once a cursor has been retrieved from list:2, use this to paginate through all file requests. The cursor must come from a previous call to list:2 or list/continue.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST update
/file_requests/update
update
scope: file_requests.write
Update a file request.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (4)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to update. |
|
|
The new title for the file request. |
|
|
The new destination path for uploaded files. |
|
|
Whether the file request should be open (true) or closed (false) after the update. |
Files (43)
POST copy
/files/copy_v2
copy
scope: files.content.write
Copy a file or folder to a different location in the user's Dropbox.
If the source path is a folder all its contents will be copied.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (5)
|
Option Name |
Description |
|---|---|
|
|
The path of the file or folder to copy. |
|
|
The destination path for the copy. |
|
|
If true, allows copying into a shared folder; if false, copying into a shared folder is disallowed. |
|
|
If true, automatically renames the copy if a conflict occurs at the destination. |
|
|
If true, allows the copy to transfer ownership if copying into a shared folder. |
POST copy_batch
/files/copy_batch_v2
copy_batch
scope: files.content.write
Copy multiple files or folders to different locations at once in the user's Dropbox.
This route will replace copy_batch:1. The main difference is this route will return status for each entry, while copy_batch:1 raises failure if any entry fails.
This route will either finish synchronously, or return a job ID and do the async copy job in background. Please use copy_batch/check:2 to check the job status.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
If true, automatically renames items when a conflict occurs during the batch copy. |
POST copy_batch/check
/files/copy_batch/check_v2
copy_batch/check
scope: files.content.write
Returns the status of an asynchronous job for copy_batch:2. It returns list of results for each entry.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST copy_reference/get
/files/copy_reference/get
copy_reference/get
scope: files.content.write
Get a copy reference to a file or folder. This reference string can be used to save that file or folder to another user's Dropbox by passing it to copy_reference/save.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
POST copy_reference/save
/files/copy_reference/save
copy_reference/save
scope: files.content.write
Save a copy reference returned by copy_reference/get to the user's Dropbox.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The copy reference string obtained from a file's share link or copy reference endpoint. |
|
|
The path to the file or folder whose properties to update. |
POST create_folder
/files/create_folder_v2
create_folder
scope: files.content.write
Create a folder at a given path.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
If true, automatically renames the folder if a conflict exists at the destination. |
POST create_folder_batch
/files/create_folder_batch
create_folder_batch
scope: files.content.write
Create multiple folders at once.
This route is asynchronous for large batches, which returns a job ID immediately and runs the create folder batch asynchronously. Otherwise, creates the folders and returns the result synchronously for smaller inputs. You can force asynchronous behaviour by using the CreateFolderBatchArg.force_async flag. Use create_folder_batch/check to check the job status.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
A list of paths where folders should be created. |
|
|
If true, automatically renames folders when a conflict occurs. |
|
|
If true, forces the operation to be performed asynchronously even if it could be done synchronously. |
POST create_folder_batch/check
/files/create_folder_batch/check
create_folder_batch/check
scope: files.content.write
Returns the status of an asynchronous job for create_folder_batch. If success, it returns list of result for each entry.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST delete
/files/delete_v2
delete
scope: files.content.write
Delete the file or folder at a given path.
If the path is a folder, all its contents will be deleted too.
A successful response indicates that the file or folder was deleted. The returned metadata will be the corresponding FileMetadata or FolderMetadata for the item at time of deletion, and not a DeletedMetadata object.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
POST delete_batch
/files/delete_batch
delete_batch
scope: files.content.write
Delete multiple files/folders at once.
This route is asynchronous, which returns a job ID immediately and runs the delete batch asynchronously. Use delete_batch/check to check the job status.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST delete_batch/check
/files/delete_batch/check
delete_batch/check
scope: files.content.write
Returns the status of an asynchronous job for delete_batch. If success, it returns list of result for each entry.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST download
/files/download
download
scope: files.content.read
Download a file from a user's Dropbox.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path and other download options. |
|
|
The response format expected from the API (e.g. application/json). |
POST download_zip
/files/download_zip
download_zip
scope: files.content.read
Download a folder from the user's Dropbox, as a zip file. The folder must be less than 20 GB in size and have fewer than 10,000 total files. The input cannot be a single file. Any single file must be less than 4GB in size.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object that defines the entries to include in the ZIP archive. |
|
|
The response format expected from the API (e.g. application/json). |
POST export
/files/export
export
scope: files.content.read
Export a file from a user's Dropbox. This route only supports exporting files that cannot be downloaded directly and whose ExportResult.file_metadata has ExportInfo.export_as populated.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path and the desired export format. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_file_lock_batch
/files/get_file_lock_batch
get_file_lock_batch
scope: files.content.read
Return the lock metadata for the given list of paths.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_metadata
/files/get_metadata
get_metadata
scope: files.metadata.read
Returns the metadata for a file or folder.
Note: Metadata for the root folder is unsupported.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The authorization token for the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (4)
|
Option Name |
Description |
|---|---|
|
|
If true, include metadata for deleted files or folders in the response. |
|
|
If true, include information about whether the item has explicit shared members. |
|
|
If true, include media metadata such as dimensions and duration for supported file types. |
|
|
The path to the file or folder whose properties to update. |
POST get_preview
/files/get_preview
get_preview
scope: files.content.read
Get a preview for a file.
Currently, PDF previews are generated for files with the following extensions: .ai, .doc, .docm, .docx, .eps, .gdoc, .gslides, .odp, .odt, .pps, .ppsm, .ppsx, .ppt, .pptm, .pptx, .rtf.
HTML previews are generated for files with the following extensions: .csv, .ods, .xls, .xlsm, .gsheet, .xlsx.
Other formats will return an unsupported extension error.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path and preview format options. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_temporary_link
/files/get_temporary_link
get_temporary_link
scope: files.content.read
Get a temporary link to stream content of a file. This link will expire in four hours and afterwards you will get 410 Gone. This URL should not be used to display content directly in the browser. The Content-Type of the link is determined automatically by the file's mime type.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
POST get_temporary_upload_link
/files/get_temporary_upload_link
get_temporary_upload_link
scope: files.content.write
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 get_temporary_upload_link 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 https://content.dropboxapi.com/apitul/1/bNi2uIYF51cVBND
--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 succesful 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.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The duration in seconds for which the temporary upload link remains valid. |
POST get_thumbnail
/files/get_thumbnail_v2
get_thumbnail
scope: files.content.read
Get a thumbnail for a file.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path, thumbnail size, and format. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_thumbnail_batch
/files/get_thumbnail_batch
get_thumbnail_batch
scope: files.content.read
Get thumbnails for a list of images. We allow up to 25 thumbnails in a single batch.
This method currently supports files with the following file extensions: jpg, jpeg, png, tiff, tif, gif and bmp. Photos that are larger than 20MB in size won't be converted to a thumbnail.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST list_folder
/files/list_folder
list_folder
scope: files.metadata.read
Starts returning the contents of a folder. If the result's ListFolderResult.has_more field is true, call list_folder/continue with the returned ListFolderResult.cursor to retrieve more entries.
If you're using ListFolderArg.recursive set to true to keep a local cache of the contents of a Dropbox account, iterate through each entry in order and process them as follows to keep your local state in sync:
For each FileMetadata, store the new entry at the given path in your local state. If the required parent folders don't exist yet, create them. If there's already something else at the given path, replace it and remove all its children.
For each FolderMetadata, store the new entry at the given path in your local state. If the required parent folders don't exist yet, create them. If there's already something else at the given path, replace it but leave the children as they are. Check the new entry's FolderSharingInfo.read_only and set all its children's read-only statuses to match.
For each DeletedMetadata, if your local state has something at the given path, remove it and all its children. If there's nothing at the given path, ignore this entry.
Note: auth.RateLimitError may be returned if multiple list_folder or list_folder/continue calls with same parameters are made simultaneously by same API app for same user. If your app implements retry logic, please hold off the retry until the previous request finishes.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (7)
|
Option Name |
Description |
|---|---|
|
|
If true, include deleted files in the folder listing. |
|
|
If true, include information about whether each item has explicit shared members. |
|
|
If true, include media metadata for supported files in the listing. |
|
|
If true, include mounted folders in the listing. |
|
|
If true, include files that are not downloadable in the listing. |
|
|
The path to the file or folder whose properties to update. |
|
|
If true, list contents of subfolders recursively. |
POST list_folder/continue
/files/list_folder/continue
list_folder/continue
scope: files.metadata.read
Once a cursor has been retrieved from list_folder, use this to paginate through all files and retrieve updates to the folder, following the same rules as documented for list_folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST list_folder/get_latest_cursor
/files/list_folder/get_latest_cursor
list_folder/get_latest_cursor
scope: files.metadata.read
A way to quickly get a cursor for the folder's state. Unlike list_folder, list_folder/get_latest_cursor doesn't return any entries. This endpoint is for app which only needs to know about new files and modifications and doesn't need to know about files that already exist in Dropbox.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (7)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
If true, include subfolders recursively when determining the cursor. |
|
|
If true, include media metadata in the cursor context. |
|
|
If true, include deleted files in the cursor context. |
|
|
If true, include explicit shared member info in the cursor context. |
|
|
If true, include mounted folders in the cursor context. |
|
|
If true, include non-downloadable files in the cursor context. |
POST list_folder/longpoll
/longpoll
list_folder/longpoll
scope: files.metadata.read
A longpoll endpoint to wait for changes on an account. In conjunction with list_folder/continue, this call gives you a low-latency way to monitor an account for file changes. The connection will block until there are changes available or a timeout occurs. This endpoint is useful mostly for client-side apps. If you're looking for server-side notifications, check out our webhooks documentation.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
|
|
The maximum time in seconds to wait for a response before returning. |
POST list_revisions
/files/list_revisions
list_revisions
scope: files.metadata.read
Returns revisions for files based on a file path or a file id. The file path or file id is identified from the latest file entry at the given file path or id. This end point allows your app to query either by file path or file id by setting the mode parameter appropriately.
In the ListRevisionsMode.path (default) mode, all revisions at the same file path as the latest file entry are returned. If revisions with the same file id are desired, then mode must be set to ListRevisionsMode.id. The ListRevisionsMode.id mode is useful to retrieve revisions for a given file across moves or renames.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
The sorting mode for revisions, such as 'path' or 'id', which determines the order of returned revisions. |
|
|
The maximum number of file requests to return in a single response. |
POST lock_file_batch
/files/lock_file_batch
lock_file_batch
scope: files.content.write
Lock the files at the given paths. A locked file will be writable only by the lock holder. A successful response indicates that the file has been locked. Returns a list of the locked file paths and their metadata after this operation.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST move
/files/move_v2
move
scope: files.content.write
Move a file or folder to a different location in the user's Dropbox.
If the source path is a folder all its contents will be moved.
Note that we do not currently support case-only renaming.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (5)
|
Option Name |
Description |
|---|---|
|
|
The path of the file or folder to copy. |
|
|
The destination path for the copy. |
|
|
If true, allows copying into a shared folder; if false, copying into a shared folder is disallowed. |
|
|
If true, automatically renames folders when a conflict occurs. |
|
|
If true, allows the copy to transfer ownership if copying into a shared folder. |
POST move_batch
/files/move_batch_v2
move_batch
scope: files.content.write
Move multiple files or folders to different locations at once in the user's Dropbox. Note that we do not currently support case-only renaming.
This route will replace move_batch:1. The main difference is this route will return status for each entry, while move_batch:1 raises failure if any entry fails.
This route will either finish synchronously, or return a job ID and do the async move job in background. Please use move_batch/check:2 to check the job status.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
If true, automatically renames folders when a conflict occurs. |
|
|
If true, allows the copy to transfer ownership if copying into a shared folder. |
POST move_batch/check
/files/move_batch/check_v2
move_batch/check
scope: files.content.write
Returns the status of an asynchronous job for move_batch:2. It returns list of results for each entry.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST permanently_delete
/files/permanently_delete
permanently_delete
scope: files.permanent_delete
Permanently delete the file or folder at a given path (see https://www.dropbox.com/en/help/40).
Note: This endpoint is only available for Dropbox Business apps.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
POST restore
/files/restore
restore
scope: files.content.write
Restore a specific revision of a file to the given path.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
The revision identifier of the file to restore, typically obtained from a previous list or delete operation. |
POST save_url
/files/save_url
save_url
scope: files.content.write
Save the data from a specified URL into a file in user's Dropbox.
Note that the transfer from the URL must complete within 5 minutes, or the operation will time out and the job will fail.
If the given path already exists, the file will be renamed to avoid the conflict (e.g. myfile (1).txt).
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
The URL of the file to save. |
POST save_url/check_job_status
/files/save_url/check_job_status
save_url/check_job_status
scope: files.content.write
Check the status of a save_url job.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST search
/files/search_v2
search
scope: files.metadata.read
Searches for files and folders.
Note: search:2 along with search/continue:2 can only be used to retrieve a maximum of 10,000 matches.
Recent changes may not immediately be reflected in search results due to a short delay in indexing. Duplicate results may be returned across pages. Some results may not be returned.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A query string to include in the check request for debugging purposes. |
POST search/continue
/files/search/continue_v2
search/continue
scope: files.metadata.read
Fetches the next page of search results returned from search:2.
Note: search:2 along with search/continue:2 can only be used to retrieve a maximum of 10,000 matches.
Recent changes may not immediately be reflected in search results due to a short delay in indexing. Duplicate results may be returned across pages. Some results may not be returned.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST unlock_file_batch
/files/unlock_file_batch
unlock_file_batch
scope: files.content.write
Unlock the files at the given paths. A locked file can only be unlocked by the lock holder or, if a business account, a team admin. A successful response indicates that the file has been unlocked. Returns a list of the unlocked file paths and their metadata after this operation.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST upload
/files/upload
upload
scope: files.content.write
Create a new file with the contents provided in the request.
Do not use this to upload a file larger than 150 MB. Instead, create an upload session with upload_session/start.
Calls 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. For more information, see the Data transport limit page.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path, thumbnail size, and format. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The file content to upload, provided as a string representation (e.g., base64-encoded data). |
POST upload_session/append
/files/upload_session/append_v2
upload_session/append
scope: files.content.write
Append more data to an upload session.
When the parameter close is set, this call will close the session.
A single request should not upload more than 150 MB. The maximum size of a file one can upload to an upload session is 350 GB.
Calls 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. For more information, see the Data transport limit page.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path, thumbnail size, and format. |
|
|
The response format expected from the API (e.g. application/json). |
POST upload_session/finish
/files/upload_session/finish
upload_session/finish
scope: files.content.write
Finish an upload session and save the uploaded data to the given file path.
A single request should not upload more than 150 MB. The maximum size of a file one can upload to an upload session is 350 GB.
Calls 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. For more information, see the Data transport limit page.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path, thumbnail size, and format. |
|
|
The response format expected from the API (e.g. application/json). |
POST upload_session/finish_batch
/files/upload_session/finish_batch
upload_session/finish_batch
scope: files.content.write
This route helps you commit many files at once into a user's Dropbox. Use upload_session/start and upload_session/append:2 to upload file contents. We recommend uploading many files in parallel to increase throughput. Once the file contents have been uploaded, rather than calling upload_session/finish, use this route to finish all your upload sessions in a single request.
UploadSessionStartArg.close or UploadSessionAppendArg.close needs to be true for the last upload_session/start or upload_session/append:2 call. The maximum size of a file one can upload to an upload session is 350 GB.
This route will return a job_id immediately and do the async commit job in background. Use upload_session/finish_batch/check to check the job status.
For the same account, this route should be executed serially. That means you should not start the next job before current job finishes. We allow up to 1000 entries in a single request.
Calls 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. For more information, see the Data transport limit page.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST upload_session/finish_batch/check
/files/upload_session/finish_batch/check
upload_session/finish_batch/check
scope: files.content.write
Returns the status of an asynchronous job for upload_session/finish_batch. If success, it returns list of result for each entry.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST upload_session/start
/files/upload_session/start
upload_session/start
scope: files.content.write
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. This call starts a new upload session with the given data. You can then use upload_session/append:2 to add more data and upload_session/finish to save all the data to a file in Dropbox.
A single request should not upload more than 150 MB. The maximum size of a file one can upload to an upload session is 350 GB.
An upload session can be used for a maximum of 48 hours. Attempting to use an UploadSessionStartResult.session_id with upload_session/append:2 or upload_session/finish more than 48 hours after its creation will return a UploadSessionLookupError.not_found.
Calls 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. For more information, see the Data transport limit page.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path, thumbnail size, and format. |
|
|
The response format expected from the API (e.g. application/json). |
Groups (12)
POST groups/create
/team/groups/create
groups/create
scope: groups.write
Creates a new, empty group, with a requested name.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The name for the new group. |
|
|
Whether the group creator should be added as an owner of the group. |
|
|
An external ID for the group, used to link with an external system. |
POST groups/delete
/team/groups/delete
groups/delete
scope: groups.write
Deletes a group.
The group is deleted immediately. However the revoking of group-owned resources may take additional time. Use the groups/job_status/get to determine whether this process has completed.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The type of session to revoke (e.g., web, desktop, mobile). |
|
|
The identifier of the group to delete. |
POST groups/get_info
/team/groups/get_info
groups/get_info
scope: groups.read
Retrieves information about one or more groups. Note that the optional field GroupFullInfo.members is not returned for system-managed groups.
Permission : Team Information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The type of session to revoke (e.g., web, desktop, mobile). |
|
|
A list of group identifiers for which to retrieve information. |
POST groups/job_status/get
/team/groups/job_status/get
groups/job_status/get
scope: groups.write
Once an async_job_id is returned from groups/delete, groups/members/add , or groups/members/remove use this method to poll the status of granting/revoking group members' access to group-owned resources.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST groups/list
/team/groups/list
groups/list
scope: groups.read
Lists groups on a team.
Permission : Team Information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
POST groups/list/continue
/team/groups/list/continue
groups/list/continue
scope: groups.read
Once a cursor has been retrieved from groups/list, use this to paginate through all groups.
Permission : Team Information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST groups/members/add
/team/groups/members/add
groups/members/add
scope: groups.write
Adds members to a group.
The members are added immediately. However the granting of group-owned resources may take additional time. Use the groups/job_status/get to determine whether this process has completed.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
Whether to return the updated list of group members after the operation. |
POST groups/members/list
/team/groups/members/list
groups/members/list
scope: groups.read
Lists members of a group.
Permission : Team Information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
POST groups/members/list/continue
/team/groups/members/list/continue
groups/members/list/continue
scope: groups.read
Once a cursor has been retrieved from groups/members/list, use this to paginate through all members of the group.
Permission : Team information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST groups/members/remove
/team/groups/members/remove
groups/members/remove
scope: groups.write
Removes members from a group.
The members are removed immediately. However the revoking of group-owned resources may take additional time. Use the groups/job_status/get to determine whether this process has completed.
This method permits removing the only owner of a group, even in cases where this is not possible via the web client.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
Whether to return the updated list of group members after the operation. |
POST groups/members/set_access_type
/team/groups/members/set_access_type
groups/members/set_access_type
scope: groups.write
Sets a member's access type in a group.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The new access type to assign to the members, such as "owner" or "member". |
|
|
Whether to return the updated list of group members after the operation. |
POST groups/update
/team/groups/update
groups/update
scope: groups.write
Updates a group's name and/or external ID.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (4)
|
Option Name |
Description |
|---|---|
|
|
Whether to return the updated list of group members after the operation. |
|
|
The new name to assign to the group. |
|
|
The new external ID to assign to the group. |
|
|
The new management type for the group, for example "user_managed" or "company_managed". |
Legal_holds (7)
POST legal_holds/create_policy
/team/legal_holds/create_policy
legal_holds/create_policy
scope: team_data.member
Creates new legal hold policy. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (4)
|
Option Name |
Description |
|---|---|
|
|
The name of the new property template. |
|
|
The list of member IDs to apply the legal hold to. |
|
|
The start date for the legal hold policy, in the format YYYY-MM-DD. |
|
|
The end date for the legal hold policy, in the format YYYY-MM-DD. |
POST legal_holds/get_policy
/team/legal_holds/get_policy
legal_holds/get_policy
scope: team_data.member
Gets a legal hold by Id. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to update. |
POST legal_holds/list_held_revisions
/team/legal_holds/list_held_revisions
legal_holds/list_held_revisions
scope: team_data.member
List the file metadata that's under the hold. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to update. |
POST legal_holds/list_held_revisions_continue
/team/legal_holds/list_held_revisions_continue
legal_holds/list_held_revisions_continue
scope: team_data.member
Continue listing the file metadata that's under the hold. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to update. |
POST legal_holds/list_policies
/team/legal_holds/list_policies
legal_holds/list_policies
scope: team_data.member
Lists legal holds on a team. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
Whether to include policies that have been released; set to true to include them. |
POST legal_holds/release_policy
/team/legal_holds/release_policy
legal_holds/release_policy
scope: team_data.member
Releases a legal hold by Id. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to update. |
POST legal_holds/update_policy
/team/legal_holds/update_policy
legal_holds/update_policy
scope: team_data.member
Updates a legal hold. Note: Legal Holds is a paid add-on. Not all teams have the feature.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the file request to update. |
|
|
The updated list of member IDs for the legal hold policy. |
Linked_apps (4)
POST linked_apps/list_member_linked_apps
/team/linked_apps/list_member_linked_apps
linked_apps/list_member_linked_apps
scope: sessions.list
List all linked applications of the team member.
Note, this endpoint does not list any team-linked applications.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The team member ID associated with the session. |
POST linked_apps/list_members_linked_apps
/team/linked_apps/list_members_linked_apps
linked_apps/list_members_linked_apps
scope: sessions.list
List all applications linked to the team members' accounts.
Note, this endpoint does not list any team-linked applications.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST linked_apps/revoke_linked_app
/team/linked_apps/revoke_linked_app
linked_apps/revoke_linked_app
scope: sessions.modify
Revoke a linked application of the team member.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST linked_apps/revoke_linked_app_batch
/team/linked_apps/revoke_linked_app_batch
linked_apps/revoke_linked_app_batch
scope: sessions.modify
Revoke a list of linked applications of the team members.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
Member_space_limits (7)
POST member_space_limits/excluded_users/add
/team/member_space_limits/excluded_users/add
member_space_limits/excluded_users/add
scope: members.write
Add users to member space limits excluded users list.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST member_space_limits/excluded_users/list
/team/member_space_limits/excluded_users/list
member_space_limits/excluded_users/list
scope: members.read
List member space limits excluded users.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
POST member_space_limits/excluded_users/list/continue
/team/member_space_limits/excluded_users/list/continue
member_space_limits/excluded_users/list/continue
scope: members.read
Continue listing member space limits excluded users.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST member_space_limits/excluded_users/remove
/team/member_space_limits/excluded_users/remove
member_space_limits/excluded_users/remove
scope: members.write
Remove users from member space limits excluded users list.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST member_space_limits/get_custom_quota
/team/member_space_limits/get_custom_quota
member_space_limits/get_custom_quota
scope: members.read
Get users custom quota. Returns none as the custom quota if none was set. A maximum of 1000 members can be specified in a single call.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST member_space_limits/remove_custom_quota
/team/member_space_limits/remove_custom_quota
member_space_limits/remove_custom_quota
scope: members.write
Remove users custom quota. A maximum of 1000 members can be specified in a single call.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST member_space_limits/set_custom_quota
/team/member_space_limits/set_custom_quota
member_space_limits/set_custom_quota
scope: members.read
Set users custom quota. Custom quota has to be at least 15GB. A maximum of 1000 members can be specified in a single call.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Members (20)
POST members/add
/team/members/add
members/add
scope: members.write
Adds members to a team.
Permission : Team member management
A maximum of 20 members can be specified in a single call.
If no Dropbox account exists with the email address specified, a new Dropbox account will be created with the given email address, and that account will be invited to the team.
If a personal Dropbox account exists with the email address specified in the call, this call will create a placeholder Dropbox account for the user on the team and send an email inviting the user to migrate their existing personal account onto the team.
Team member management apps are required to set an initial given_name and surname for a user to use in the team invitation and for 'Perform as team member' actions taken on the user before they become 'active'.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
If true, forces the operation to be performed asynchronously even if it could be done synchronously. |
POST members/add/job_status/get
/team/members/add/job_status/get
members/add/job_status/get
scope: members.write
Once an async_job_id is returned from members/add , use this to poll the status of the asynchronous request.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST members/delete_profile_photo
/team/members/delete_profile_photo
members/delete_profile_photo
scope: members.write
Deletes a team member's profile photo.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/get_info
/team/members/get_info
members/get_info
scope: members.read
Returns information about multiple team members.
Permission : Team information
This endpoint will return MembersGetInfoItem.id_not_found, for IDs (or emails) that cannot be matched to a valid team member.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/list
/team/members/list
members/list
scope: members.read
Lists members of a team.
Permission : Team information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
|
|
Whether to include members who have been removed from the team; set to true to include them. |
POST members/list/continue
/team/members/list/continue
members/list/continue
scope: members.read
Once a cursor has been retrieved from members/list, use this to paginate through all team members.
Permission : Team information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST members/move_former_member_files
/team/members/move_former_member_files
members/move_former_member_files
scope: members.write
Moves removed member's files to a different member. This endpoint initiates an asynchronous job. To obtain the final result of the job, the client should periodically poll members/move_former_member_files/job_status/check.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/move_former_member_files/job_status/check
/team/members/move_former_member_files/job_status/check
members/move_former_member_files/job_status/check
scope: members.write
Once an async_job_id is returned from members/move_former_member_files , use this to poll the status of the asynchronous request.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST members/recover
/team/members/recover
members/recover
scope: members.delete
Recover a deleted member.
Permission : Team member management
Exactly one of team_member_id, email, or external_id must be provided to identify the user account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/remove
/team/members/remove
members/remove
scope: members.delete
Removes a member from a team.
Permission : Team member management
Exactly one of team_member_id, email, or external_id must be provided to identify the user account.
Accounts can be recovered via members/recover for a 7 day period or until the account has been permanently deleted or transferred to another account (whichever comes first). Calling members/add while a user is still recoverable on your team will return with MemberAddResult.user_already_on_team.
Accounts can have their files transferred via the admin console for a limited time, based on the version history length associated with the team (180 days for most teams).
This endpoint may initiate an asynchronous job. To obtain the final result of the job, the client should periodically poll members/remove/job_status/get.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
If true, delete the member's data after removal. |
|
|
If true, keep the member's account active but remove from team. |
|
|
If true, retain the member's shares with the team after removal. |
POST members/remove/job_status/get
/team/members/remove/job_status/get
members/remove/job_status/get
scope: members.delete
Once an async_job_id is returned from members/remove , use this to poll the status of the asynchronous request.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST members/secondary_emails/add
/team/members/secondary_emails/add
members/secondary_emails/add
scope: members.write
Add secondary emails to users.
Permission : Team member management.
Emails that are on verified domains will be verified automatically. For each email address not on a verified domain a verification email will be sent.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/secondary_emails/delete
/team/members/secondary_emails/delete
members/secondary_emails/delete
scope: members.write
Delete secondary emails from users
Permission : Team member management.
Users will be notified of deletions of verified secondary emails at both the secondary email and their primary email.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/secondary_emails/resend_verification_emails
/team/members/secondary_emails/resend_verification_emails
members/secondary_emails/resend_verification_emails
scope: members.write
Resend secondary email verification emails.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/send_welcome_email
/team/members/send_welcome_email
members/send_welcome_email
scope: members.write
Sends welcome email to pending team member.
Permission : Team member management
Exactly one of team_member_id, email, or external_id must be provided to identify the user account.
No-op if team member is not pending.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The type of session to revoke (e.g., web, desktop, mobile). |
|
|
The team member ID associated with the session. |
POST members/set_admin_permissions
/team/members/set_admin_permissions
members/set_admin_permissions
scope: members.write
Updates a team member's permissions.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The new admin role to assign to the member (e.g., team_admin, user_management_admin). |
POST members/set_profile
/team/members/set_profile
members/set_profile
scope: members.write
Updates a team member's profile.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The new email address for the member. |
|
|
The new surname for the member. |
POST members/set_profile_photo
/team/members/set_profile_photo
members/set_profile_photo
scope: members.write
Updates a team member's profile photo.
Permission : Team member management.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST members/suspend
/team/members/suspend
members/suspend
scope: members.write
Suspend a member from a team.
Permission : Team member management
Exactly one of team_member_id, email, or external_id must be provided to identify the user account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
If true, delete the member's data upon suspension. |
POST members/unsuspend
/team/members/unsuspend
members/unsuspend
scope: members.write
Unsuspend a member from a team.
Permission : Team member management
Exactly one of team_member_id, email, or external_id must be provided to identify the user account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Namespaces (2)
POST namespaces/list
/team/namespaces/list
namespaces/list
scope: team_data.member
Returns a list of all team-accessible namespaces. This list includes team folders, shared folders containing team members, team members' home namespaces, and team members' app folders. Home namespaces and app folders are always owned by this team or members of the team, but shared folders may be owned by other users or other teams. Duplicates may occur in the list.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
POST namespaces/list/continue
/team/namespaces/list/continue
namespaces/list/continue
scope: team_data.member
Once a cursor has been retrieved from namespaces/list, use this to paginate through all team-accessible namespaces. Duplicates may occur in the list.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
Reports (4)
POST reports/get_activity
/team/reports/get_activity
reports/get_activity
scope: team_info.read
Retrieves reporting data about a team's user activity.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST reports/get_devices
/team/reports/get_devices
reports/get_devices
scope: team_info.read
Retrieves reporting data about a team's linked devices.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST reports/get_membership
/team/reports/get_membership
reports/get_membership
scope: team_info.read
Retrieves reporting data about a team's membership.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST reports/get_storage
/team/reports/get_storage
reports/get_storage
scope: team_info.read
Retrieves reporting data about a team's storage usage.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type header value for the request. |
|
|
The response format expected from the API (e.g. application/json). |
Sharing (37)
POST add_file_member
/sharing/add_file_member
add_file_member
scope: sharing.write
Adds specified members to a file.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (5)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to share. |
|
|
A custom message to include in the sharing notification. |
|
|
If true, do not send a notification to the added member. |
|
|
The access level to grant (e.g., viewer, editor). |
|
|
If true, add the custom message as a comment on the file. |
POST add_folder_member
/sharing/add_folder_member
add_folder_member
scope: sharing.write
Allows an owner or editor (if the ACL update policy allows) of a shared folder to add another member.
For the new member to get access to all the functionality for this folder, you will need to call mount_folder on their behalf.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
If true, do not send a notification to the added member. |
|
|
A custom message to include in the sharing notification. |
POST check_job_status
/sharing/check_job_status
check_job_status
scope: sharing.write
Returns the status of an asynchronous job.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST check_remove_member_job_status
/sharing/check_remove_member_job_status
check_remove_member_job_status
scope: sharing.write
Returns the status of an asynchronous job for sharing a folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST check_share_job_status
/sharing/check_share_job_status
check_share_job_status
scope: sharing.write
Returns the status of an asynchronous job for sharing a folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST get_file_metadata
/sharing/get_file_metadata
get_file_metadata
scope: sharing.read
Returns shared file metadata.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to get metadata for. |
|
|
An array of action names to include metadata for (e.g., edit, comment). |
POST get_file_metadata/batch
/sharing/get_file_metadata/batch
get_file_metadata/batch
scope: sharing.read
Returns shared file metadata.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
An array of file IDs or paths to get metadata for. |
|
|
An array of action names to include metadata for (e.g., edit, comment). |
POST get_folder_metadata
/sharing/get_folder_metadata
get_folder_metadata
scope: sharing.read
Returns shared folder metadata by its folder ID.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
An array of action names to include metadata for (e.g., edit, comment). |
POST get_shared_link_file
/sharing/get_shared_link_file
get_shared_link_file
scope: sharing.read
Download the shared link's file from a user's Dropbox.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The Dropbox-API-Arg header containing a JSON object with the file path, thumbnail size, and format. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_shared_link_metadata
/sharing/get_shared_link_metadata
get_shared_link_metadata
scope: sharing.read
Get the shared link's metadata.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
The URL of the file to save. |
POST list_file_members
/sharing/list_file_members
list_file_members
scope: sharing.read
Use to obtain the members who have been invited to a file, both inherited and uninherited members.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to get metadata for. |
|
|
If true, includes members inherited from parent folders; otherwise only direct members are returned. |
|
|
The maximum number of file requests to return in a single response. |
POST list_file_members/batch
/sharing/list_file_members/batch
list_file_members/batch
scope: sharing.read
Get members of multiple files at once. The arguments to this route are more limited, and the limit on query result size per file is more strict. To customize the results more, use the individual file endpoint.
Inherited users and groups are not included in the result, and permissions are not returned for this endpoint.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
An array of file IDs or paths to get metadata for. |
|
|
The maximum number of file requests to return in a single response. |
POST list_file_members/continue
/sharing/list_file_members/continue
list_file_members/continue
scope: sharing.read
Once a cursor has been retrieved from list_file_members or list_file_members/batch, use this to paginate through all shared file members.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST list_folder_members/continue
/sharing/list_folder_members/continue
list_folder_members/continue
scope: sharing.read
Once a cursor has been retrieved from list_folder_members, use this to paginate through all shared folder members.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST list_folders
/sharing/list_folders
list_folders
scope: sharing.read
Return the list of all shared folders the current user has access to.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
|
|
An array of action names to include metadata for (e.g., edit, comment). |
POST list_folders/continue
/sharing/list_folders/continue
list_folders/continue
scope: sharing.read
Once a cursor has been retrieved from list_folders, use this to paginate through all shared folders. The cursor must come from a previous call to list_folders or list_folders/continue.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST list_mountable_folders
/sharing/list_mountable_folders
list_mountable_folders
scope: sharing.read
Return the list of all shared folders the current user can mount or unmount.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
|
|
An array of action names to include metadata for (e.g., edit, comment). |
POST list_mountable_folders/continue
/sharing/list_mountable_folders/continue
list_mountable_folders/continue
scope: sharing.read
Once a cursor has been retrieved from list_mountable_folders, use this to paginate through all mountable shared folders. The cursor must come from a previous call to list_mountable_folders or list_mountable_folders/continue.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST list_received_files
/sharing/list_received_files
list_received_files
scope: sharing.read
Returns a list of all files shared with current user.
Does not include files the user has received via shared folders, and does not include unclaimed invitations.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
|
|
An array of action names to include metadata for (e.g., edit, comment). |
POST list_received_files/continue
/sharing/list_received_files/continue
list_received_files/continue
scope: sharing.read
Get more results with a cursor from list_received_files.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST list_shared_links
/sharing/list_shared_links
list_shared_links
scope: sharing.read
List shared links of this user.
If no path is given, returns a list of all shared links for the current user.
If a non-empty path is given, returns a list of all shared links that allow access to the given path - direct links to the given path and links to parent folders of the given path. Links to parent folders can be suppressed by setting direct_only to true.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST modify_shared_link_settings
/sharing/modify_shared_link_settings
modify_shared_link_settings
scope: sharing.write
Modify the shared link's settings.
If the requested visibility conflict with the shared links policy of the team or the shared folder (in case the linked file is part of a shared folder) then the LinkPermissions.resolved_visibility of the returned SharedLinkMetadata will reflect the actual visibility of the shared link and the LinkPermissions.requested_visibility will reflect the requested visibility.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The URL of the file to save. |
|
|
If true, removes any expiration date currently set on the shared link. |
POST mount_folder
/sharing/mount_folder
mount_folder
scope: sharing.write
The current user mounts the designated folder.
Mount a shared folder for a user after they have been added as a member. Once mounted, the shared folder will appear in their Dropbox.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
POST relinquish_file_membership
/sharing/relinquish_file_membership
relinquish_file_membership
scope: sharing.write
The current user relinquishes their membership in the designated file. Note that the current user may still have inherited access to this file through the parent folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to get metadata for. |
POST relinquish_folder_membership
/sharing/relinquish_folder_membership
relinquish_folder_membership
scope: sharing.write
The current user relinquishes their membership in the designated shared folder and will no longer have access to the folder. A folder owner cannot relinquish membership in their own folder.
This will run synchronously if leave_a_copy is false, and asynchronously if leave_a_copy is true.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
If true, a copy of the folder's contents will be retained in your Dropbox; otherwise the folder is removed. |
POST remove_file_member_2
/sharing/remove_file_member_2
remove_file_member_2
scope: sharing.write
Removes a specified member from the file.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to get metadata for. |
POST remove_folder_member
/sharing/remove_folder_member
remove_folder_member
scope: sharing.write
Allows an owner or editor (if the ACL update policy allows) of a shared folder to remove another member.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
If true, the removed member will keep a copy of the folder's contents; otherwise they lose access entirely. |
POST revoke_shared_link
/sharing/revoke_shared_link
revoke_shared_link
scope: sharing.write
Revoke a shared link.
Note that even after revoking a shared link to a file, the file may be accessible if there are shared links leading to any of the file parent folders. To list all shared links that enable access to a specific file, you can use the list_shared_links with the file as the ListSharedLinksArg.path argument.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The URL of the file to save. |
POST set_access_inheritance
/sharing/set_access_inheritance
set_access_inheritance
scope: sharing.write
Change the inheritance policy of an existing Shared Folder. Only permitted for shared folders in a shared team root.
If a ShareFolderLaunch.async_job_id is returned, you'll need to call check_share_job_status until the action completes to get the metadata for the folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
Specifies whether the shared folder should inherit access from its parent folder. |
POST share_folder
/sharing/share_folder
share_folder
scope: sharing.write
Share a folder with collaborators.
Most sharing will be completed synchronously. Large folders will be completed asynchronously. To make testing the async case repeatable, set ShareFolderArg.force_async.
If a ShareFolderLaunch.async_job_id is returned, you'll need to call check_share_job_status until the action completes to get the metadata for the folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (6)
|
Option Name |
Description |
|---|---|
|
|
The path to the file or folder whose properties to update. |
|
|
Determines who can update the access control list for the shared folder. |
|
|
If true, forces the operation to be performed asynchronously even if it could be done synchronously. |
|
|
Sets the policy for who can become a member of the shared folder. |
|
|
Controls the policy for shared links created from the folder. |
|
|
Indicates whether the folder inherits access permissions from its parent. |
POST transfer_folder
/sharing/transfer_folder
transfer_folder
scope: sharing.write
Transfer ownership of a shared folder to a member of the shared folder.
User must have AccessLevel.owner access to the shared folder to perform a transfer.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
The Dropbox ID of the user to whom the folder ownership will be transferred. |
POST unmount_folder
/sharing/unmount_folder
unmount_folder
scope: sharing.write
The current user unmounts the designated folder. They can re-mount the folder at a later time using mount_folder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
POST unshare_file
/sharing/unshare_file
unshare_file
scope: sharing.write
Remove all members from this file. Does not remove inherited members.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to get metadata for. |
POST unshare_folder
/sharing/unshare_folder
unshare_folder
scope: sharing.write
Allows a shared folder owner to unshare the folder.
You'll need to call check_job_status to determine if the action has completed successfully.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
If true, the removed member will keep a copy of the folder's contents; otherwise they lose access entirely. |
POST update_file_member
/sharing/update_file_member
update_file_member
scope: sharing.write
Changes a member's access on a shared file.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The file ID or path to get metadata for. |
|
|
The access level to grant (e.g., viewer, editor). |
POST update_folder_member
/sharing/update_folder_member
update_folder_member
scope: sharing.write
Allows an owner or editor of a shared folder to update another member's permissions.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
The access level to grant (e.g., viewer, editor). |
POST update_folder_policy
/sharing/update_folder_policy
update_folder_policy
scope: sharing.write
Update the sharing policies for a shared folder.
User must have AccessLevel.owner access to the shared folder to update its policies.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (4)
|
Option Name |
Description |
|---|---|
|
|
The ID of the shared folder to add the member to. |
|
|
New policy for who can become a member of the shared folder. |
|
|
New policy for who can update the access control list. |
|
|
New policy for shared links associated with the folder. |
Team (3)
POST features/get_values
/team/features/get_values
features/get_values
scope: team_info.read
Get the values for one or more featues. This route allows you to check your account's capability for what feature you can access or what value you have for certain features.
Permission : Team information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_info
/team/get_info
get_info
scope: team_info.read
Retrieves information about a team.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST token/get_authenticated_admin
/team/token/get_authenticated_admin
token/get_authenticated_admin
scope: team_info.read
Returns the member profile of the admin who generated the team access token used to make the call.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Team_folder (10)
POST team_folder/activate
/team/team_folder/activate
team_folder/activate
scope: team_data.team_space
Sets an archived team folder's status to active.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the team folder to activate. |
POST team_folder/archive
/team/team_folder/archive
team_folder/archive
scope: team_data.team_space
Sets an active team folder's status to archived and removes all folder and file members.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the team folder to archive. |
|
|
When true, forces the archiving to complete synchronously instead of asynchronously. |
POST team_folder/archive/check
/team/team_folder/archive/check
team_folder/archive/check
scope: team_data.team_space
Returns the status of an asynchronous job for archiving a team folder.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the asynchronous job to check. |
POST team_folder/create
/team/team_folder/create
team_folder/create
scope: team_data.team_space
Creates a new, active, team folder with no members.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The name of the new property template. |
|
|
The sync setting to apply to the new team folder (e.g., default or not synced). |
POST team_folder/get_info
/team/team_folder/get_info
team_folder/get_info
scope: team_data.team_space
Retrieves metadata for team folders.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A list of team folder IDs for which to retrieve information. |
POST team_folder/list
/team/team_folder/list
team_folder/list
scope: team_data.team_space
Lists all team folders.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
POST team_folder/list/continue
/team/team_folder/list/continue
team_folder/list/continue
scope: team_data.team_space
Once a cursor has been retrieved from team_folder/list, use this to paginate through all team folders.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
POST team_folder/permanently_delete
/team/team_folder/permanently_delete
team_folder/permanently_delete
scope: team_data.team_space
Permanently deletes an archived team folder.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The ID of the team folder to permanently delete. |
POST team_folder/rename
/team/team_folder/rename
team_folder/rename
scope: team_data.team_space
Changes an active team folder's name.
Permission : Team member file access.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the team folder to permanently delete. |
|
|
The name of the new property template. |
POST team_folder/update_sync_settings
/team/team_folder/update_sync_settings
team_folder/update_sync_settings
scope: team_data.team_space
Updates the sync settings on a team folder or its contents. Use of this endpoint requires that the team has team selective sync enabled.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The ID of the team folder to permanently delete. |
|
|
The sync setting to apply to the new team folder (e.g., default or not synced). |
Team_log (2)
POST get_events
/team_log/get_events
get_events
scope: events.read
Retrieves team events. If the result's GetTeamEventsResult.has_more field is true, call get_events/continue with the returned cursor to retrieve more entries. If end_time is not specified in your request, you may use the returned cursor to poll get_events/continue for new events.
Many attributes note 'may be missing due to historical data gap'.
Note that the file_operations category and & analogous paper events are not available on all Dropbox Business plans. Use features/get_values to check for this feature.
Permission : Team Auditing.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
The maximum number of file requests to return in a single response. |
|
|
Filter events by a specific category, such as "members" or "sharing", to narrow down results. |
POST get_events/continue
/team_log/get_events/continue
get_events/continue
scope: events.read
Once a cursor has been retrieved from get_events, use this to paginate through all events.
Permission : Team Auditing.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The cursor returned from a previous search request to continue pagination. |
Users (5)
POST features/get_values
/users/features/get_values
features/get_values
scope: account_info.read
Get a list of feature values that may be configured for the current account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_account
/users/get_account
get_account
scope: sharing.read
Get information about a user's account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
The account ID of the user whose details you want to retrieve. |
POST get_account_batch
/users/get_account_batch
get_account_batch
scope: sharing.read
Get information about multiple user accounts. At most 300 accounts may be queried per request.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A list of account IDs for the users you want to look up. |
POST get_current_account
/users/get_current_account
get_current_account
scope: account_info.read
Get information about the current user's account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST get_space_usage
/users/get_space_usage
get_space_usage
scope: account_info.read
Get the space usage information for the current user's account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |