Rate Limiting and Terms of Service

Rate Limiting

Being a good citizen in the Reverb API ecosystem is important. We ask that all our integrators take precautions to avoid flooding Reverb with too many requests.

If Reverb detects a large volume of requests from a particular application, we may issue a Rate Limit response which will consist of a HTTP status code of 429. More information on the exact response is coming soon.

Applications that have higher rate limit requirements may ask for a rate limit increase. To do so, please contact [email protected].

These are the current API rate limits:

• GET operations: 10,000 requests per 10-minutes OR 2,000 requests per 1-minute. Beyond that, you will need to throttle. Overflow will result in 429s until the triggered monitoring period expires.
• UPDATE (PUT / POST) operations: 3,000 requests per 10-minutes OR 600 requests per 1-minute. Beyond that, you will need to throttle. Overflow will result in 429s until the triggered monitoring period expires.