Eventlayer / API & operations
Rate Limits
Learn about per-key rate limiting and quotas.
Eventlayer applies rate limits on a per-API-key basis to ensure fair usage and service stability.
How rate limiting works
Every request you make is counted against your API key's rate limit. When you exceed the limit, subsequent requests receive a 429 Too Many Requests response until the limit window resets.
Rate limiting is enforced using a token bucket algorithm:
- Requests per second — The number of tokens replenished each second.
- Burst size — The maximum number of tokens that can accumulate.
Default limits
| Parameter | Default |
|---|---|
| Requests per second | 100 |
| Burst size | 50 |
These defaults apply to all API keys. Contact support if you need higher limits for your application.
429 response
When you exceed the rate limit, you will receive:
{
"status": 429,
"error": {
"type": "https://eventlayer.dev/docs/errors#rate-limit-exceeded",
"title": "Rate limit exceeded",
"status": 429,
"detail": "You've reached a rate limit. Try again shortly.",
"code": "RATE_LIMIT_EXCEEDED",
"requestId": "req_01k2example",
"fields": []
}
}Best practices
- Batch operations — If you need to create or update many resources, batch your requests rather than sending them in rapid succession.
- Respect backoff — When you receive a
429, wait before retrying. Exponential backoff is recommended. - Monitor response headers — Rate limit headers may be included in responses to help you track your usage.