Rate Limiting
To ensure fair and reliable service for all clients, the Flowbrite API enforces rate limiting using the token bucket algorithm. This algorithm allows short bursts of requests while enforcing a maximum sustained rate over time.
How It Works
- Each client has a “bucket” of tokens.
- Every API request consumes one token.
- Tokens are automatically refilled at a fixed interval.
- If the bucket is empty, requests may be queued (up to a limit) or rejected until new tokens become available.
API Limits
| Description | Value | |
|---|---|---|
| Token Limit | Maximum burst size (maximum tokens in the bucket at any time) | 180 |
| Tokens per Period | Number of tokens added to the bucket each replenishment period | 30 |
| Replenishment Period | How often tokens are added to the bucket | Every 10 seconds |
| Queue Length | Maximum number of requests that can be queued if tokens are not available | 60 |
What does this mean for you?
- You can make up to 180 requests in a quick burst.
- After a burst, tokens are refilled at a rate of 30 every 10 seconds (so, max 180 per minute).
- If you exceed the limit, up to 60 requests will be queued and processed in FIFO order as the tokens refill.
- If you exceed the limit, you will receive a
429 Rate Limit Exceededresponse.
429 - Rate Limit Exceeded
{
"error": {
"status": 429,
"code": "api.common.rateLimitExceeded",
"message": "Rate limit exceeded. Please retry in 60 seconds"
}
}
If you frequently hit the rate limit, consider spacing out your API calls. Please reach out to our support team for assistance or to increase your rate limits.