Rate Limiting
Learn about API rate limits based on operation types. Understand token bucket policies, burst capacity, and how to handle rate limiting responses effectively.
Overview
Rate limits are applied per operation type, with each having its own limit and burst capacity. Exceeding these limits will result in a 429 Too Many Requests response.
If you consistently need higher limits, please contact us.
Rate Limits by Operation Type
We apply different rate limits based on the type of operation you're performing:
| Operation Type | Limit | Burst Capacity | Window |
|---|---|---|---|
| Read | 1,200 | 1,000 | 1 minute |
| List | 600 | 200 | 1 minute |
| Write | 360 | 120 | 1 minute |
| Update | 480 | 160 | 1 minute |
| Delete | 240 | 80 | 1 minute |
Handling Rate Limits
When you hit a rate limit:
- You'll receive a
429 Too Many Requestsresponse - The response will include a
Retry-Afterheader - Wait for the specified time before retrying
Example error response:
{
"type": "too_many_requests_error",
"url": "https://www.mixedbread.com/api-reference",
"message": "Rate limit exceeded. Please try again later.",
"details": {
"retry_after": 60,
"limit": "1200",
"remaining": "0",
"reset": "1730000000"
}
}