Dropbox API v2

What authentication does the Dropbox API v2 use?

The Dropbox API v2 uses OAuth 2.0 for authentication. Apps obtain an access token through the OAuth flow and include it as a Bearer token in the Authorization header. Through Jentic, OAuth tokens are stored encrypted in your Jentic One instance - agents receive scoped access without handling raw tokens directly.

Can I upload files larger than 150 MB with the Dropbox API v2?

Yes. Files up to 150 MB can be uploaded in a single call. For larger files, use the chunked upload session endpoints: start a session with /2/files/upload_session/start, append chunks with /2/files/upload_session/append_v2, and finalize with /2/files/upload_session/finish. Sessions support files up to 350 GB.

How do I search for files in Dropbox through Jentic?

Search Jentic for the intent 'search for files in Dropbox' to load the /2/files/search_v2 operation schema. This endpoint searches by filename, file content, or extension across the entire account. Pass a query string and optional filters (file type, path, modification date) to narrow results. Install the SDK with pip install jentic to get started.

What are the rate limits for the Dropbox API v2?

Dropbox enforces per-app and per-user rate limits. Individual apps are limited to roughly 1,000 calls per user per 5 minutes for most endpoints. Write-heavy endpoints like upload and batch operations have lower limits. The API returns HTTP 429 with a Retry-After header when limits are exceeded.

Can I track file changes in real-time with the Dropbox API v2?

The API supports near-real-time change detection through cursor-based polling. Call /2/files/list_folder to get an initial cursor, then use /2/files/list_folder/continue to receive only new changes. For immediate notification, the long-poll endpoint at https://notify.dropboxapi.com/2/files/list_folder/longpoll blocks until changes occur or times out after a configurable interval.

Can I limit what my agent is allowed to do with the Dropbox API v2?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Dropbox operations and credentials your agent may use. You grant only the OAuth scopes the task needs, such as files.content.read for listing a folder or sharing.write for creating a shared link, so a destructive call like /2/files/delete_v2 is unavailable unless you explicitly add its scope. Since each request names the target file or folder in its body, you can keep the agent confined to specific operations and paths while your stored credentials are exchanged for scoped tokens at execution time.