API 1.0.0REST APIStable
Rate Limiting
Understand and work with API rate limits
Warning
We recommend posting stats hourly. Exceeding limits returns 429 with Retry-After. Avoid spikes by smoothing updates.
Rate Limits (Practical)
| Scope | Limit | Notes |
|---|---|---|
| Public (per-IP) | 600/min | Typical read endpoints |
| Per API key (reads) | 120/min | Applies to read requests |
| Write endpoints (/stats) | per-IP ~120/min; per-key ~60/min | Server enforces one stats update per bot every 5 minutes; post hourly to reduce risk |
Rate Limit Headers
Every API response includes rate limit information:
JavaScript
X-RateLimit-Limit: 100X-RateLimit-Remaining: 95X-RateLimit-Reset: 1705318200
Additionally, 429 responses include a Retry-After header indicating seconds until you may retry.
Handling Rate Limits
When you exceed the rate limit, you'll receive a 429 Too Many Requests response:
JSON
1{2 "success": false,3 "error": "Rate limit exceeded",4 "retryAfter": 605}
Use the Retry-After header to know when to retry.
Best Practices
- Monitor your rate limit remaining in response headers
- Implement exponential backoff for retries
- Cache responses when possible
- Batch requests when allowed
- Contact support for higher limits if needed
Need more help?
Ask in our Discord or email support@conscherry.com.