What are the rate limites on the pro yearly and ultra yearly? it just says Higher and you you have an API call to tell you where you are on the rate limits?
What are the rate limites on the pro yearly and ultra yearly? it just says Higher and you you have an API call to tell you where you are on the rate limits?
We previously posted the rate limits in another thread; we will post them here in this thread as soon as possible, presumably later today.
ok, thank you I will watch for the update. I tried search and can see discussions on rate limits but not the actual rate limits so I am curious.
@DeplorableTM
Limits are applied per API key.
There are two separate sets of limits:
- one for "/stats" endpoints;
- one for all other endpoints.
The minute window resets at the beginning of each minute, the hour window resets at the beginning of each hour, and the day window resets at "00:00 UTC".
---
STATS ENDPOINTS ("/stats")
Plan| Per minute| Per hour| Per day
Free| 40| 200| 400
Pro| 180| 1,500| 6,000
Yearly| 180| 1,500| 6,000
Ultra| 240| 2,400| 12,000
Ultra Yearly| 240| 2,400| 12,000
Mega| 320| 3,200| 24,000
Mega Yearly| 320| 3,200| 24,000
Enterprise| 600| 6,000| 60,000
---
ALL OTHER ENDPOINTS
Plan| Per minute| Per hour| Per day
Free| 20| 120| 300
Pro| 120| 1,000| 4,500
Yearly| 120| 1,000| 4,500
Ultra| 160| 1,600| 9,000
Ultra Yearly| 160| 1,600| 9,000
Mega| 220| 2,200| 18,000
Mega Yearly| 220| 2,200| 18,000
Enterprise| 400| 4,000| 45,000
---
MONTHLY QUOTA
Plan| Calls per month
Free| 3,000
Pro / Yearly| 50,000
Ultra / Ultra Yearly| 100,000
Mega / Mega Yearly| 200,000
Enterprise| 500,000
---
VIOLATIONS AND ESCALATION
Exceeding any rate-limit window returns an "HTTP 429" response.
Repeated violations within a rolling 24-hour period result in the following penalties:
Violations within 24 hours| Penalty
3| 1-hour block
5| 6-hour block
7| 24-hour ban
10| 7-day ban
The violation counter resets automatically after 24 consecutive hours without a violation, so normal usage should never reach these thresholds.
---
STAYING WITHIN THE LIMITS
Every response includes your current rate-limit status in the response headers, so you do not need to guess how many requests remain.
X-RateLimit-Plan
Your current plan bucket.
X-RateLimit-Type
The limit type applied to the request: "stats" or "default".
X-RateLimit-Minute-Limit
The request limit for the current minute window.
X-RateLimit-Minute-Remaining
The number of calls remaining in the current minute.
X-RateLimit-Minute-Reset
The ISO timestamp of the next minute-window reset.
The same information is also provided for the hourly and daily windows:
X-RateLimit-Hour-Limit
X-RateLimit-Hour-Remaining
X-RateLimit-Hour-Reset
X-RateLimit-Day-Limit
X-RateLimit-Day-Remaining
X-RateLimit-Day-Reset
---
HTTP 429 RESPONSE HEADERS
When an "HTTP 429" response is returned, the following headers are also included:
Retry-After
The number of seconds to wait before retrying the request.
X-RateLimit-Window
The window that was exceeded:
- "minute"
- "hour"
- "day"
X-RateLimit-Reason
The reason for the rate-limit response:
- "limit-minute"
- "limit-hour"
- "limit-day"
- "block-until"
- "ban-until"
Read the "*-Remaining" headers and reduce your request rate before the remaining value reaches zero.
When you receive an "HTTP 429" response, always honour the "Retry-After" header before sending another request. Following these rules is enough to avoid triggering the escalation ladder.
Topic not found or an error occurred.
← Back to Support