Rate Limiting
The Tella API implements rate limiting to ensure fair usage and protect the service for all users.Current limits
| Limit | Value |
|---|---|
| Requests per minute | 100 |
| Scope | Per user |
Rate limits are applied per user within an organization. All API keys created
by the same user share the same rate limit.
Rate limit headers
Every API response includes headers with rate limit information:| Header | Description | Example |
|---|---|---|
X-RateLimit-Limit | Maximum requests per window | 100 |
X-RateLimit-Remaining | Remaining requests in current window | 95 |
X-RateLimit-Reset | Unix timestamp when the window resets | 1704067200 |
Example response headers
Handling rate limits
429 Too Many Requests
When you exceed the rate limit, you’ll receive a429 status code:
Best practices
Check remaining requests
Check remaining requests
Monitor the
X-RateLimit-Remaining header and slow down before hitting the limit.Implement exponential backoff
Implement exponential backoff
When you receive a 429, wait before retrying with increasing delays:
Use the reset timestamp
Use the reset timestamp
The
X-RateLimit-Reset header tells you exactly when your limit resets:Batch requests efficiently
Batch requests efficiently
Instead of making many small requests, use pagination efficiently:
Rate limit scope
Rate limits are calculated per user within an organization:- All API keys created by the same user share the same 100 requests per minute limit
- Different users in the same organization have independent limits
- The limit applies across all endpoints