File Operations | Dropbox API Documentation

User access tokens and agent runtime tokens call the same Dropbox file APIs. The credential changes the available files, not the endpoint.

The table shows Dropbox file API routes and their scopes. All listed operations support user and agent tokens except files/list_revisions, which is Coming soon for agent tokens.

Agent Filesystem is in Private Preview and is subject to change. Contact your Dropbox representative to request access.

Operation	Required scope	Dropbox API endpoint
Upload a file	`files.content.write`	`files/upload`
Download a file	`files.content.read`	`files/download`
List a folder	`files.metadata.read`	`files/list_folder`
Create a folder	`files.content.write`	`files/create_folder_v2`
Move a file or folder	`files.content.write`	`files/move_v2`
Copy a file or folder	`files.content.write`	`files/copy_v2`
Delete a file or folder	`files.content.write`	`files/delete_v2`
Get metadata	`files.metadata.read`	`files/get_metadata`
List file versions (user tokens only)	`files.metadata.read`	`files/list_revisions`

The app and token must include the listed scope. The user must also have access to the target. For an agent token, the workspace must grant read or read_write access for read operations and read_write access for changes.

Use the returned file ID when you need a stable reference to a file or folder. Paths can change after a move or rename.

Operations on a folder must respect workspace rules for the files and subfolders they affect. When creating new folders, the nearest existing parent must allow read_write access.

See Workspaces for rule inheritance and effective access.