/coinmarketcap/coins/search

POST /api/coinmarketcap/coins/search

Price: 5 credits

List cryptocurrencies ranked by market capitalization

How to use it

List cryptocurrencies ranked by market capitalization (rank 1 = the largest). Returns each coin's name, symbol, slug, image, market-cap rank, category tags, audited flag, circulating/total/max supply, and current market data in the chosen currency: price, 24h trading volume, market cap, fully diluted market cap, market-cap dominance, and price change percentages over multiple windows. Set convert to denominate the figures in USD, EUR, GBP, JPY, BTC or ETH. Use a returned slug with the 'coins' endpoint for the full profile.

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 coins to return, ranked by market cap (min: 1)
• convert string — Currency to denominate price, volume and market cap in (default: "USD"; one of: "USD", "EUR", "GBP", "JPY", "BTC", "ETH")

Response

• @type string (default: "CoinmarketcapListingCoin")
• id integer required
• name string required
• symbol string required
• alias string nullable
• rank integer nullable
• image string nullable
• is_audited boolean (default: false)
• tags array (default: [])
• market_pair_count integer nullable
• circulating_supply number nullable
• total_supply number nullable
• max_supply number nullable
• date_added string nullable
• convert string nullable
• price number nullable
• volume_24h number nullable
• market_cap number nullable
• fully_diluted_market_cap number nullable
• market_cap_dominance number nullable
• turnover number nullable
• price_change_percentage_1h number nullable
• price_change_percentage_24h number nullable
• price_change_percentage_7d number nullable
• price_change_percentage_30d number nullable
• price_change_percentage_60d number nullable
• price_change_percentage_90d number nullable
• price_change_percentage_1y number nullable
• ytd_price_change_percentage number nullable
• volume_change_percentage_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.