While Dropbox does not publish exact rate limits, these limits are not designed to inhibit normal applications. Rate limited requests themselves also count towards rate limits, and thus rapid retry loops without pause or respecting this header will be counter-productive.

Rate limited responses always include a Retry-After header that provides the limit in seconds that your app would need to wait before retrying to ensure a successful response. If your application experiences a rate limit, the API call will return an HTTP 429 error, returning the reason of too_many_requests (in JSON, or plaintext per the Content-Type HTTP header). If your team-linked app is calling User Endpoints on behalf of team members with Dropbox-API-Select-User, the rate limits apply per team member.

For team-links, rate limits apply per team when calling Business Endpoints.

Multiple apps that a user may have linked don’t contribute to each other’s rate limiting.

For user-link s, rate limits apply per user who has linked your app.

The Dropbox API enforces rate limits on the number of API calls issued over a period of time on a per-authorization basis

Dropbox call support