/dappradar/dapps

POST /api/dappradar/dapps

Price: 5 credits

Get full details for a dapp by its slug

How to use it

Get the full profile of a decentralized application (dapp) by its DappRadar slug (e.g. 'hyperliquid'). Returns name, logo, category, supported chains, rank in category, market cap, 24h volume, token price, 24h price change, a description, similar dapps, and resource links (website, social media). Use the dapps search endpoint to discover slugs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dapp string required — Dapp slug from its DappRadar url (the part after /dapp/) (examples: "hyperliquid", "uniswap", "pancakeswap-amm-v3"; minLength: 1)

Response

• @type string (default: "DappradarDappDetail")
• alias string required
• name string required
• symbol string nullable
• image string nullable
• category string nullable
• chains array (default: [])
• rank_in_category integer nullable
• market_cap number nullable
• volume_24h number nullable
• token_price number nullable
• change_24h number nullable
• description string nullable
• similar_dapps array (default: [])
  • @type string (default: "DappradarSimilarDapp")
  • name string required
  • alias string nullable
  • category string nullable
  • chains array (default: [])
• resources array (default: [])
  • @type string (default: "DappradarResource")
  • label string required
  • url string required

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 — Dapp 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.