Overview
To ensure fair usage and system stability, Orwel implements rate limiting on all API requests. Rate limits are applied per API key.Rate Limits
Production Keys
1,000 requests per minuteSuitable for production workloads and high-traffic applications
Development Keys
100 requests per minutePerfect for testing and development environments
Rate Limit Headers
Every API response includes rate limit information in the headers:Maximum number of requests allowed in the current window
Number of requests remaining in the current window
Unix timestamp when the rate limit resets
Rate Limit Exceeded
When you exceed the rate limit, you’ll receive a429 Too Many Requests response:
Retry-After header indicating how many seconds to wait before retrying.
Best Practices
Monitor Rate Limit Headers
Monitor Rate Limit Headers
Always check the
X-RateLimit-Remaining header to know how many requests you have left. Implement logic to slow down requests as you approach the limit.Implement Exponential Backoff
Implement Exponential Backoff
When you receive a 429 response, wait before retrying. Use exponential backoff to gradually increase wait times.
Batch Requests
Batch Requests
Instead of making many individual requests, batch your operations when possible. For example, use pagination to fetch multiple items in a single request.
Cache Responses
Cache Responses
Cache API responses when appropriate to reduce the number of requests. Use ETags or implement your own caching strategy.
Monitoring Usage
Track your API usage in the Orwel dashboard:- Navigate to Settings → API Keys
- View usage metrics for each key
- Monitor rate limit violations
- Set up alerts for high usage
Increasing Limits
If you need higher rate limits for your production workload:Contact Support
Email support@orwel.io with your use case
Enterprise plans include higher rate limits by default. Contact sales to learn more.