From the API limits documentation:
The API has requests rate limits per key/token powered by a Leaky Bucket algorithm. If requests come too frequently, they are queued in a bucket. If the queue reaches the bucket limit, the API responds with HTTP 429 error.
Current limit is 5 requests per second with a bucket size up to 100 requests.
I’ve hit the rate limit a couple of times, but have been unable to inspect the 429 response for headers myself - are there headers present to indicate the state of the leaky bucket, or perhaps more simply information about when the rate limit will be reset (i.e. X-RateLimit-Reset
)?