API Rate Limits
Aevum News implements rate limiting to ensure platform stability and fair usage across all developers. Understand your quota, monitor response headers, and design your integration to handle limits gracefully.
Default Limits by Tier
| Tier | Requests / Minute | Requests / Day | Burst Capacity |
|---|---|---|---|
| Free | 60 | 10,000 | 10 requests |
| Pro | 300 | 100,000 | 50 requests |
| Enterprise | 1,200 | Unlimited* | 200 requests |
* Unlimited daily quotas require manual review and are subject to responsible usage policies.
Rate Limit Headers
Every API response includes headers indicating your current quota status. Use these to dynamically adjust request behavior:
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 247
X-RateLimit-Reset: 1715892400
Retry-After: 42
Handling 429 Too Many Requests
When you exceed your rate limit, the API returns a 429 status code with the following JSON payload:
{
"error": {
"code": 429,
"message": "Rate limit exceeded. Please retry after the specified time.",
"retry_after": 42
}
}
Best Practice: Implement exponential backoff with jitter. Never cache the 429 response to avoid retry storms.
Recommended Retry Logic (JavaScript)
async function fetchWithRetry(url, options = {}, retries = 3) {
try {
const response = await fetch(url, options);
if (response.status === 429) {
const retryAfter = parseInt(response.headers.get('Retry-After')) || 1;
await new Promise(res => setTimeout(res, retryAfter * 1000 * (Math.random() + 0.5)));
return fetchWithRetry(url, options, retries - 1);
}
return response;
} catch (error) {
if (retries > 0) return fetchWithRetry(url, options, retries - 1);
throw error;
}
}
Endpoint-Specific Limits
Certain high-compute or sensitive endpoints enforce stricter limits to protect infrastructure:
| Endpoint | Limit | Notes |
|---|---|---|
GET /v1/search |
30 req/min | Heavy indexing; use cached results |
POST /v1/articles/publish |
10 req/min | Requires editorial approval workflow |
GET /v1/author/export |
5 req/hour | Large payload; generates archive |
GET /v1/analytics/realtime |
60 req/min | WebSocket fallback recommended |
Monitoring & Alerts
Track your API usage and rate limit consumption via the Developer Dashboard. Configure email or webhook alerts when usage crosses 80% of your tier limits.
Increasing Your Limits
If your application requires higher throughput:
- Upgrade your subscription tier via the Billing Portal
- Request a custom quota for enterprise workflows
- Optimize requests by using pagination, filtering, and webhook subscriptions
Learn how to handle errors gracefully in our Error Handling Guide, or explore authentication patterns in our OAuth 2.0 Reference.