Reference · built on requestConnectorFiles, documents & spreadsheets

Dropbox

Files, folders, sharing links, and team folders in Dropbox through the Dropbox API v2, with cursor-based change polling.

Request accessPricing ↗

About

Dropbox stores files for individuals and for Dropbox Business teams. Its HTTP API v2 groups endpoints into namespaces: files for listing, uploading, and moving content, sharing for shared links and shared folders, and team and team_log for members, team folders, and the audit log. Change tracking is cursor based: files/list_folder returns a cursor, and files/list_folder/continue returns what changed since.

Through Fibric, an operator holds a cursor per folder, wakes on a webhook or a longpoll, and proposes an upload, a shared link, or a share of a folder. You approve the path and the audience. Each approved change is written once, with a receipt that says what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Dropbox and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Files and folders through files/list_folder, with FileMetadata, FolderMetadata, and DeletedMetadata entries and a cursor
  • Changes since a cursor through files/list_folder/continue, with recursive listing and deleted entries when requested
  • A signal that changes are waiting, from files/list_folder/longpoll at notify.dropboxapi.com without a token
  • Webhook notifications that name the accounts with changes, signed with X-Dropbox-Signature, and never the file details
  • Shared folder membership and shared link metadata through the sharing namespace
  • Team audit events through team_log/get_events, up to 1000 a call, with cursor continuation

Proposed actions

  • Target capability: propose an upload through files/upload for files up to 150 MiB, or an upload session above that
  • Target capability: propose a shared link through sharing/create_shared_link_with_settings, with audience, expiry, and password
  • Target capability: propose sharing a folder through sharing/share_folder, polled through check_share_job_status when async

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • File proof of delivery from a driver's folder

    The operator polls the cursor on a shared folder, reads new photo entries, and proposes each one as the proof on the matching delivery.

    With Delivery Proof

  • Remove a leaver from every shared folder

    The operator reads shared folder members across the team, lists what a departing member can still reach, and proposes the removals for your approval.

    With Offboarding Sweep, Access Review

  • Send a link that expires

    When a document is requested, the operator proposes a shared link with the audience, expiry, and password you set, and records who received it.

    With Sample Request, Escalation Packet

Requirements

  • A Dropbox app in the App Console, set to App Folder or Full Dropbox access, with the scopes it needs
  • For team endpoints, a team-level token authorized by a Dropbox Business admin, with Dropbox-API-Select-User to act as a member
  • An HTTPS webhook URI that answers the challenge verification within ten seconds
  • For team_log/get_events, a plan that includes team auditing and the events.read scope
Authentication
OAuth 2.0 with short-lived access tokens and a refresh token when token_access_type=offline is requested; scopes such as files.metadata.read, files.content.write, sharing.write, and events.read set what the app may call.

Limits

  • Dropbox does not publish exact rate limits; a 429 with too_many_requests carries Retry-After, and retries count against the limit
  • Writes to one namespace take a lock; too many at once return 429 with too_many_write_operations
  • A webhook notification carries account ids only; your app then calls files/list_folder/continue with its cursor
  • files/upload stops at 150 MiB; an upload session runs for at most 7 days and takes chunks of at most 150 MiB each

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Dropbox ↗

Questions and answers

How does an app know when a Dropbox folder changes?
Three ways. Poll files/list_folder/continue with your cursor. Block on files/list_folder/longpoll, which needs no token and answers with changes true. Or register a webhook: Dropbox posts the account ids with changes, and your app calls list_folder/continue for each.
Do Dropbox access tokens expire?
Yes. Access tokens are short-lived, with the expiry returned by /oauth2/token. Add token_access_type=offline to the authorization URL to receive a refresh_token, then call the token endpoint with grant_type refresh_token for a new access token.
How large a file can be uploaded?
files/upload takes files up to 150 MiB. Above that, upload_session/start, upload_session/append:2, and upload_session/finish carry chunks of at most 150 MiB each, sequentially or concurrently, for up to 7 days, to a maximum of 2,199,019,061,248 bytes.
Ask about Dropbox

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Dropbox through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy