/coinmarketcap/exchanges

POST /api/coinmarketcap/exchanges

Price: 1 credit

Get full details and trading stats for a cryptocurrency exchange by its slug

How to use it

Get the full profile of a cryptocurrency exchange by its CoinMarketCap slug (e.g. 'binance'). Returns name, description, image, status, launch date, maker/taker fees, 24h spot/perpetual/futures trading volume in USD, derivatives open interest, reserve net worth, supported fiat currencies and countries, and official links (website, blog, fee schedule, socials).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• slug string required — Exchange slug (e.g. 'binance') (examples: "binance"; minLength: 1)

Response

• @type string (default: "CoinmarketcapExchange")
• id integer required
• name string required
• alias string nullable
• description string nullable
• image string nullable
• status string nullable
• date_launched string nullable
• maker_fee number nullable
• taker_fee number nullable
• spot_volume_usd number nullable
• perpetual_volume_usd number nullable
• futures_volume_usd number nullable
• derivatives_open_interest_usd number nullable
• net_worth_usd number nullable
• fiats array (default: [])
• countries array (default: [])
• urls object nullable
  • @type string (default: "CoinmarketcapExchangeUrls")
  • website array (default: [])
  • blog array (default: [])
  • fee array (default: [])
  • twitter array (default: [])
  • chat array (default: [])

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