POST /api/solscan/tokens/leaderboard
Price: 5 credits
Rank Solana tokens by trading volume or traders in a time window, by category, with thresholds
Rank Solana tokens of one list (trending, new, meme, DeFi, liquid staking, stablecoins, stocks, pump.fun) by volume or trader count in a 30-minute to 24-hour window, with optional minimum thresholds. Each token carries buy, sell and trader statistics for all four windows with their change in percent.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of tokens to return (min: 1)category string — Token list to read (default: "trending"; one of: "trending", "new", "meme", "defi", "lst", "stablecoin", "stocks", "pumpfun")window string — Time window the ranking and min_volume apply to (default: "24h"; one of: "30m", "1h", "4h", "24h")sort_by string — Metric to rank tokens by within the window, highest first (default: "volume"; one of: "volume", "trader_count")min_volume number nullable — Minimum USD trading volume in the window (min: 0)min_liquidity number nullable — Minimum USD liquidity (min: 0)min_market_cap number nullable — Minimum USD market cap (min: 0)min_holder_count integer nullable — Minimum number of holders (min: 0)min_trader_count_24h integer nullable — Minimum number of traders in 24 hours (min: 0)min_trade_count_24h integer nullable — Minimum number of trades in 24 hours (min: 0)@type string (default: "SolscanTokenListing")token_address string requiredname string nullablesymbol string nullableimage string nullabledecimals integer nullableprice number nullablemarket_cap number nullableliquidity number nullableholder_count integer nullablelisted_at integer nullableplatforms array (default: [])stats array (default: [])@type string (default: "SolscanTokenWindowStats")window string requiredprice_change number nullablevolume number nullablevolume_change number nullablebuy_volume number nullablebuy_volume_change number nullablesell_volume number nullablesell_volume_change number nullabletrade_count integer nullabletrade_count_change number nullablebuy_count integer nullablebuy_count_change number nullablesell_count integer nullablesell_count_change number nullabletrader_count integer nullabletrader_count_change number nullablebuyer_count integer nullablebuyer_count_change number nullableseller_count integer nullableseller_count_change number nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.