Docs menuRate limits

API reference

Rate limits

How many requests each route takes before it says wait.

Limits

RouteLimitCounted per
POST /api/auth (challenge)20 an hourAddress (IP)
POST /api/v1/launch/prepare6 an hourWallet
POST /api/v1/coin/{address}/comment10 a minuteWallet
PATCH /api/v1/user/preferences30 a minuteWallet
GET /api/v1/coins/search60 a minuteAddress (IP)
POST /api/v1/transaction/build20 a minuteAddress (IP)
GET /api/v1/transaction/status60 a minuteAddress (IP)
GET /api/v1/user/holdings20 a minuteWallet
POST /api/v1/referrals/visit30 a minuteAddress (IP)
POST /api/v1/referrals/me, POST /api/v1/referrals/link10 a minute eachWallet
Claims and redeems (.../payout/request)6 a minute eachWallet
POST /api/rpc120 a minute, of which 20 sendsAddress (IP)

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.

Routes with the envelope
{
  "success": false,
  "message": "Too many requests. Wait a moment and try again.",
  "error": "Too many requests. Wait a moment and try again.",
  "data": null
}
Search, trade builds, transaction status, holdings and the relay
{
  "error": "Too many searches. Wait a moment and try again.",
  "code": "rate"
}
Cookies On Our Website. We use cookies to keep you signed in and remember your settings.