You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Upload/Download files via API using AWS Lambda - Rate Limiting
Hi all, I am designing a system to copy files to/from Dropbox via the HTTP API using AWS Lambda functions. We may be copying large quantities of files (up to 10,000 in a batch) using a singl...
Thanks. It sounds like I need to do some trial-and-error. Marking this solved - but I may be back :)
Greg-DB
Dropbox Staff
Dropbox StaffThere's no accumulating penalty. The additional calls will just receive the 429 response with the Retry-After value. The Retry-After value is generally not more than a few minutes. (I believe the Retry-After value may effectively get reset with each rate limited call within the rate limiting window, but if they're all getting sent at the same time anyway like you describe, this shouldn't make any meaningful difference.)
By the way, for the upload case, make sure you read about "lock contention" in the data ingress guide I linked earlier. That has important information about a 429 error you can hit in that case, which isn't explicit rate limiting, and offers a solution.
By the way, for the upload case, make sure you read about "lock contention" in the data ingress guide I linked earlier. That has important information about a 429 error you can hit in that case, which isn't explicit rate limiting, and offers a solution.
Thanks. It sounds like I need to do some trial-and-error. Marking this solved - but I may be back :)
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
