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.
- The routes that cost the site money at its providers (the Solana connection, private holding, the wallet service) also have a ceiling for the whole site per day, counted in the database. When one is reached the route answers 429 until the next day (UTC). Nothing anybody holds is affected.
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"
}