The API is rate limited to 100 requests every 60 seconds. If the rate limit is exceeded, the API will respond with a 429 Too Many Requests status code. The response will include a Retry-After header containing a UNIX timestamp indicating the time of the next period reset. To ensure your next request will succeed, your application should delay any further requests until this time has been reached.
Some API endpoints don't count towards the rate limit; they will not use up any of your remaining requests for the current period. See the route listings in this documentation for information on which endpoints are exempt from rate limiting.
Most API responses will include headers describing the current rate limit amounts and reset times.
|X-Rate-Limit-Limit||The total number of requests allowed in each period.|
|X-Rate-Limit-Remaining||The number of remaining requests in the current period.|
|X-Rate-Limit-Reset||The number of seconds until the next period reset.|
Error responses will not include the above headers.