/dappradar/chains

POST /api/dappradar/chains

Price: 10 credits

Get a blockchain's profile and its top dapps by chain slug

How to use it

Get a blockchain's profile by its DappRadar slug (e.g. 'ethereum', 'solana'). Returns the chain name, a description, and its top dapps ranked by activity (each with name, slug, symbol, chains, market cap, price, 24h change, volume, UAW, and TVL). Optionally filter the dapps by category and choose the activity time window. Use the chains search endpoint to discover chain slugs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chain string required — Chain slug from its DappRadar url (the part after /rankings/protocol/) (examples: "ethereum", "solana", "bnb-chain", "base"; minLength: 1)
• count integer required — Number of top dapps on the chain to return (min: 1)
• category string nullable — Filter dapps by category (one of: "games", "defi", "gambling", "exchanges", "collectibles", "marketplaces", "social", "other", "high-risk")
• range string nullable — Time window for the dapp activity metrics (one of: "24h", "7d", "30d")

Response

• @type string (default: "DappradarChainDetail")
• alias string required
• name string nullable
• description string nullable
• dapps array (default: [])
  • @type string (default: "DappradarDapp")
  • rank integer nullable
  • name string required
  • alias string nullable
  • symbol string nullable
  • image string nullable
  • chains array (default: [])
  • market_cap number nullable
  • price number nullable
  • change_24h number nullable
  • volume_24h number nullable
  • volume_share number nullable
  • uaw integer nullable
  • tvl 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 — Chain not found 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.