Overview
Akhara enforces rate limits to ensure fair usage and system stability. Rate limits are applied per API key and vary by endpoint and plan tier.Rate Limits
Default Limits by Plan
Limits by Endpoint Category
Endpoint-Specific Limits
Some endpoints have specific limits due to resource intensity:Rate Limit Headers
Every API response includes rate limit information in headers:Example Response Headers
Example 429 Response
Usage Quotas
Quotas limit total usage over billing periods, separate from rate limits.Quota Types by Plan
Checking Quota Usage
Response
Handling Rate Limits
Basic Retry with Backoff
Proactive Rate Limiting
Check remaining quota before making requests:Batch Operations
Reduce API calls by using batch endpoints:Parallel Requests with Limits
Control concurrency to stay within limits:Quota Alerts
Configure alerts when approaching quota limits:Webhook Payload
Requesting Limit Increases
Temporary Increases
For one-time events (e.g., large data migration):Permanent Increases
Contact sales for permanent limit increases:- Pro → Enterprise upgrade: Unlimited quotas
- Custom enterprise limits: Tailored to your needs
- Dedicated infrastructure: Isolated rate limits
Best Practices
Use Batch APIs
Combine multiple operations into batch requests when possible
Implement Backoff
Always implement exponential backoff for 429 responses
Cache Responses
Cache read results to reduce API calls
Monitor Usage
Set up alerts before hitting limits
Do’s and Don’ts
Related
Errors & Status Codes
Handling API errors
Billing
Upgrade your plan