/dappradar/pairs/search

POST /api/dappradar/pairs/search

Price: 5 credits

Rank DEX trading pairs by volume, price, liquidity, or 24h change

How to use it

Rank decentralized exchange (DEX) trading pairs tracked by DappRadar's DEX Screener. Returns each pair's pool id, pair name, base and quote symbols, chain, DEX, price, 24h volume, liquidity, and 24h price change. Choose the sort order (volume, price, liquidity, 24h change). When DappRadar's full screener is unavailable the endpoint falls back to their short highest-volume listing: far fewer pairs than `count` come back, `X-Total-Available-Results` then reports how many exist in that mode rather than the full corpus, and while the returned pairs are ordered by the sort you asked for, *which* pairs they are is fixed by 24h volume.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of DEX trading pairs to return (min: 1)
• sort string — Sort order for the pairs (default: "vol"; one of: "vol", "price", "liq", "d24")

Response

• @type string (default: "DappradarPair")
• rank integer nullable
• pool_id integer nullable
• pair string required
• base string nullable
• quote string nullable
• chain string nullable
• dex string nullable
• price number nullable
• volume_24h number nullable
• liquidity number nullable
• change_24h number nullable

Errors

• 422 — 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.