Rate Limits

The rate limiter safeguards against bursts of incoming traffic to help maximize stability. If you send many requests in quick succession, you might see error responses with status code 429.

The current limit is 1000 requests within a 5-minute sliding window.

A basic technique for integrations to gracefully handle limiting is to watch for 429 status codes and build in a retry mechanism. The retry mechanism should follow an exponential backoff schedule to reduce request volume when necessary. We’d also recommend building some randomness into the backoff schedule to avoid a thundering herd effect.

Backoff only helps once you have already been limited. If your integration issues a long series of requests, the simplest way to avoid limiting altogether is to pace them. The limit works out to just over 3 requests per second sustained, so a short sleep of 500ms between sequential requests keeps you well under it.

Monthly Data Usage

Each project also has a monthly data usage limit, measured in bytes of response data rather than number of requests.

The current limit is 250 MB per 500 points of capacity. Once it is reached, future requests return 429 error responses until the limit resets at the start of the next calendar month.

Current usage for the month is shown on the API Keys tab under project settings.