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
Too many write request on Javascript SDK Upload File
I have tons of user that needs to upload their files to dropbox through my application. I'm using Javascript API that use generated access token. I've made the upload one by one so it will not get ...
- The Dropbox API does have a rate limiting system, but we don't have any specific numbers documented, nor can we increase or remove the limits for any particular app, user, or team.
Also note that not all 429s or 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential back-off, if not.
For example, you can check the body of the response for a more specific error. If the error is 'too_many_write_operations', that's not explicit rate limiting, but rather "lock contention". There isn't a way to remove that limitation either, but there are ways to avoid it. You can find more information about that here:
https://www.dropbox.com/developers/reference/data-ingress-guide
Greg-DB
Dropbox Staff
Dropbox StaffThe Dropbox API does have a rate limiting system, but we don't have any specific numbers documented, nor can we increase or remove the limits for any particular app, user, or team.
Also note that not all 429s or 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential back-off, if not.
For example, you can check the body of the response for a more specific error. If the error is 'too_many_write_operations', that's not explicit rate limiting, but rather "lock contention". There isn't a way to remove that limitation either, but there are ways to avoid it. You can find more information about that here:
https://www.dropbox.com/developers/reference/data-ingress-guide
Also note that not all 429s or 503s indicate explicit rate limiting, but in any case that you get a 429 or 503 the best practice is to retry the request, respecting the Retry-After header if given in the response, or using an exponential back-off, if not.
For example, you can check the body of the response for a more specific error. If the error is 'too_many_write_operations', that's not explicit rate limiting, but rather "lock contention". There isn't a way to remove that limitation either, but there are ways to avoid it. You can find more information about that here:
https://www.dropbox.com/developers/reference/data-ingress-guide
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
