Skip to content
throttle
Menu
HomeAPI LimitsDropbox API

Storage

Dropbox API

APIs for files, sharing, team administration, namespaces, and Dropbox content.

PUBLISHED PROVIDER LIMITS

Limits keep their provider-specific dimensions.

Dropbox does not publish a universal request allowance. Scope follows the authorization type and endpoint behavior.

Authentication: OAuth access token, App key and secret where app authentication is supported

Primary scope: Authorization, User, Team, Member, Or Namespace Depending On The Endpoint

Measured dimensions: Requests, Write Operations

Profile coverage: Dropbox authorization scope, unpublished general limits, 429 behavior, Retry-After semantics, write-conflict handling, and batching guidance. Endpoint-specific allocation limits remain outside this profile.

Rate limits

Dropbox API Rate limits
LimitValuePeriodScopeConditions and variability
General Dropbox API rate limitProvider-specificProvider-definedAuthorizationRate-limited requests count toward the applicable limit Exact general values are not published. User-linked apps are commonly limited per user, while team-linked business endpoints can be limited per team or selected team member.

Write Concurrency

Dropbox API Write Concurrency
LimitValuePeriodScopeConditions and variability
Concurrent write operationsProvider-specificProvider-definedNamespaceDropbox can return too_many_write_operations when concurrent writes conflict. The response can instruct the client to retry immediately and batching is recommended.

RESPONSE METADATA

Headers expose the applicable limit state.

Retry-AfterFormat: Integer Seconds
Integer seconds to wait before retrying a rate-limited request.

WHEN A LIMIT IS EXCEEDED

Read the response before choosing a delay.

  • Rate-limit responses can use HTTP 429.
  • Error.reason: Dropbox can distinguish too_many_requests from too_many_write_operations.

RECOMMENDED HANDLING

Protect both the provider and your own queue.

  • Honor Retry-After exactly.
  • Use exponential backoff only after the provider-specified delay.
  • Batch write operations where supported.
  • Avoid repeatedly sending requests while an authorization is rate limited.

VERIFICATION RECORD

Official sources reviewed