cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Share your feedback on the Document Scanning Experience in the Dropbox App right here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Too many write request on Javascript SDK Upload File

Too many write request on Javascript SDK Upload File

yanlyan
Explorer | Level 3
Go to solution

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 429 error if there's just one user active, but if 3 or more user active at the same time, sometime each user get 429 error.

 

How to fix this ?

1 Accepted Solution

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution
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

View solution in original post

1 Reply 1

Greg-DB
Dropbox Staff
Go to solution
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
Need more support?
Who's talking

Top contributors to this post

  • User avatar
    Greg-DB Dropbox Staff
What do Dropbox user levels mean?