Rate Limits
Kallglot uses rate limiting to ensure fair usage and maintain service quality. This page explains the limits and how to work with them.Rate Limit Tiers
| Plan | API Requests | Concurrent Sessions | WebSocket Messages |
|---|---|---|---|
| Free/Test | 60/min | 2 | 100/sec |
| Starter | 120/min | 10 | 500/sec |
| Pro | 600/min | 50 | 1000/sec |
| Enterprise | Custom | Custom | Custom |
Types of Limits
API Request Limits
Limits on HTTP API calls per minute:| Endpoint Group | Starter | Pro |
|---|---|---|
| Sessions (create, end) | 60/min | 300/min |
| Sessions (read) | 120/min | 600/min |
| Recordings | 60/min | 300/min |
| Analysis | 30/min | 150/min |
| Webhooks | 60/min | 300/min |
Concurrent Session Limits
Maximum number of active sessions at any time:| Plan | Concurrent Sessions |
|---|---|
| Free/Test | 2 |
| Starter | 10 |
| Pro | 50 |
| Enterprise | Unlimited* |
WebSocket Message Limits
Limits on messages sent to WebSocket per second:| Plan | Messages/Second | Audio Data/Second |
|---|---|---|
| Free/Test | 100 | 32KB |
| Starter | 500 | 64KB |
| Pro | 1000 | 128KB |
| Enterprise | Custom | Custom |
Rate Limit Headers
API responses include headers indicating your current rate limit status:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the window |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Unix timestamp when the limit resets |
Handling Rate Limits
When you exceed a rate limit, the API returns a429 Too Many Requests response:
Retry-After header:
Retry Logic
Proactive Rate Limiting
Check headers before hitting limits:Best Practices
Implement exponential backoff
Implement exponential backoff
When rate limited, use exponential backoff to avoid hammering the API:
Cache frequently accessed data
Cache frequently accessed data
Cache session info, transcripts, and recordings locally instead of fetching repeatedly:
Batch operations when possible
Batch operations when possible
Use batch endpoints or reduce redundant calls:
Use webhooks instead of polling
Use webhooks instead of polling
Subscribe to webhook events instead of polling for changes:
Monitor your usage
Monitor your usage
Track API usage to identify optimization opportunities:
Increasing Limits
Upgrading Your Plan
Upgrade to a higher plan for increased limits:- Go to Settings > Billing
- Select a new plan
- Limits increase immediately
Enterprise Custom Limits
Enterprise customers can request custom limits:- Higher API request limits
- More concurrent sessions
- Dedicated infrastructure
- SLA guarantees