API reference
Rate limits
How many requests each route takes before it says wait.
Limits
How they count
- Sign in, launch, chat and settings limits are counted in the database, so they hold across the whole site.
- The other limits are counted by each server on its own. They slow down floods; they are not exact.
- Edge caching means most public reads never reach a limit.
When you hit one
The answer is status 429. Wait a moment and try again.
{
"success": false,
"message": "Too many requests. Wait a moment and try again.",
"error": "Too many requests. Wait a moment and try again.",
"data": null
}{
"error": "Too many searches. Wait a moment and try again.",
"code": "rate"
}