We use rate limiting to safeguard the stability of our API. The default rate limiter allows up to 300 requests per minute timeframe.

|-------------|-------------|--------
0sec          60sec          120sec
1        250          250
[  timeframe  ]       [  timeframe  ]

You can see your rate limits at API > Rate Limits. To increase this limit, please contact us.

Any request over the limit will return a 429 Too Many Requests error.

Our server responses also return your API limit, remaining requests, and seconds until the limit resets as headers. If you curl the endpoints with the -vvv flag, you'll see the headers as such.

...
< ratelimit-limit: 300
< ratelimit-remaining: 280
< ratelimit-reset: 53

Best Practices

• Structured Retry Logic - To react to a 429, we recommend implementing an exponential backoff strategy. This approach helps manage rate limits effectively, ensuring your requests are processed as soon as capacity becomes available. A sample backoff interval could start with delays of 5 seconds, then progressively increase to 10, 20, 40 seconds, and so forth.
• Monitoring RateLimit response headers - Rate limits and quotas are available in the dashboard, with additional details provided dynamically in response headers for each API request. We recommend monitoring the RateLimit-Remaining header and, if it drops below 15% of the RateLimit-Limit, begin throttling requests to avoid reaching the limit. This is especially useful for operations that are high volume. You should also consider building alerting in your system to notify you when you're approaching your rate limit.