Rate Limits

All our APIs have rate limits in place to safeguard our infrastructure against excessive request rates and maintain their speed and stability for all users.

Rate limiting is done across the account. When you exceed the rate limits for an endpoint, you will receive a 429 (Too many requests) response code.

Staying within the rate limits 🙌 If you receive a response status code of 429 (Too Many Requests), please sleep/pause for the number of milliseconds specified by the value of X-RateLimit-Reset response header before making additional requests to that endpoint.

Interval window

Rate limits apply to a designated timeframe. If, for instance, an endpoint permits 100 requests within a second (equivalent to 1000 milliseconds), surpassing this rate will result in your application receiving a 429 response code. Each endpoint may feature distinct limitations, and these thresholds are disclosed through rate-limiting headers, as described below.

A single endpoint can have multiple limits, such as a 100 requests per second limit, in addition to 1000 limits for a 15-minute duration.

Response headers to understand rate limits

After each API request, you will also receive the subsequent response headers. Utilize these headers to adhere to rate limitations or temporarily halt your workflow should you surpass the defined limits.

Response header	Description
X-RateLimit-Limit	The maximum number of requests that can be made to this endpoint in interval specified by X-RateLimit-Interval response header.
X-RateLimit-Reset	The amount of time in milliseconds, before you can make another request to this endpoint. Pause/sleep your workflow for this duration.
X-RateLimit-Interval	The duration of interval in milliseconds for which this rate limit was exceeded.

Request higher rate limits

If your workflow demands a higher rate limits, please reach out to us at [e-mail]