/coinmarketcap/exchanges/search

POST /api/coinmarketcap/exchanges/search

Price: 5 credits

List cryptocurrency exchanges ranked by CoinMarketCap trust score

How to use it

List cryptocurrency exchanges ranked by CoinMarketCap trust score (the default exchange ranking). Returns each exchange's name, alias, image, rank, exchange type, trust and traffic scores, 24h spot and total USD volume, 7d and 30d total USD volume, 24h derivatives volume, 24h volume change, market share, liquidity, number of markets and listed coins, weekly visits, maker/taker fees, supported fiat currencies, and launch date.

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 exchanges to return (min: 1)

Response

• @type string (default: "CoinmarketcapSearchExchange")
• id integer required
• name string required
• alias string nullable
• image string nullable
• rank integer nullable
• score number nullable
• traffic_score number nullable
• type string nullable
• status string nullable
• spot_volume_usd number nullable
• total_volume_usd number nullable
• total_volume_7d number nullable
• total_volume_30d number nullable
• derivatives_volume_usd number nullable
• volume_change_percentage_24h number nullable
• market_share_percentage number nullable
• liquidity number nullable
• market_count integer nullable
• coin_count integer nullable
• weekly_visit_count integer nullable
• maker_fee number nullable
• taker_fee number nullable
• fiats array (default: [])
• date_launched string 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.