POST /api/solscan/markets/search
Price: 10 credits
Search Solana DEX markets (liquidity pools) ranked by 24-hour volume or TVL
Search Solana DEX markets (liquidity pools) ranked by 24-hour volume or by TVL, optionally only one DEX program or only pools trading a given token. Returns each pool's address and name, its program, the pooled tokens with names and symbols, creation time, 24-hour volume, trades and traders with their changes, TVL, score and the burnt and locked liquidity rates.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of markets to return (min: 1)sort_by string — Metric to rank markets by, highest first (default: "volume_24h"; one of: "volume_24h", "tvl")program_id string nullable — Only markets of this DEX program (examples: "whirLbMiicVdio4qvUfM5KAg6Ct8VwpYzGff3uctyCc")token_address string nullable — Only markets trading this token mint (examples: "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v")@type string (default: "SolscanMarket")pool_id string requiredname string nullableprogram_id string nullableprogram_name string nullabletokens array (default: [])@type string (default: "SolscanMarketToken")token_address string requiredtoken_account string nullablename string nullablesymbol string nullablecreated_at integer nullablevolume_24h number nullablevolume_change_24h number nullabletvl number nullabletrade_count_24h integer nullabletrade_count_change_24h number nullabletrader_count_24h integer nullabletrader_count_change_24h number nullablescore number nullableburnt_liquidity_rate number nullablelocked_liquidity_rate 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.