Does your API V2 have any limitations by number requests from one IP address or for one account?
We don't have specific numbers documented for the general rate limiting system. Please write your app to catch and handle any rate limit responses as described above.
The rate limiting system and parameters are subject to change, so this strategy is preferred as it produces a more dynamic way of handling rate limiting, as opposed to relying on a hard-coded number.
The Dropbox API does have a general rate limiting system. It operates on a per-user account basis, not per-IP address.
Also note that not all 429s and 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.
Thank you, @Greg-DB !Could you please clarify what specific limits are used in the Dropbox API? How many requests allowed to do in 1 sec, min, day etc.
Thank You!
