/coinmarketcap/coins/pairs

POST /api/coinmarketcap/coins/pairs

Price: 5 credits

List the trading pairs (markets) of a cryptocurrency across exchanges

How to use it

List where a cryptocurrency trades, by its CoinMarketCap slug (e.g. 'bitcoin') or numeric id (e.g. '1'). Each market returns the exchange (name, slug, id), the trading pair (e.g. BTC/USDT with base and quote symbols), the market category (spot, perpetual, etc.), the market and center type (cex/dex), the fee type, a direct link to the market on the exchange, the latest price, 24h volume in USD as well as in the base and quote currencies, effective liquidity, order-book depth at +/-2% in USD, and the market's score and reputation.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• coin string required — Coin slug (e.g. 'bitcoin') or numeric id (e.g. '1') (examples: "bitcoin", "1"; minLength: 1)
• count integer required — Number of trading pairs to return (min: 1)

Response

• @type string (default: "CoinmarketcapMarketPair")
• exchange object required
  • @type string (default: "CoinmarketcapPairExchange")
  • id integer nullable
  • name string nullable
  • alias string nullable
• market_pair object required
  • @type string (default: "CoinmarketcapPairMarket")
  • name string required
  • base_symbol string nullable
  • quote_symbol string nullable
• category string nullable
• type string nullable
• center_type string nullable
• fee_type string nullable
• market_url string nullable
• price number nullable
• volume_usd number nullable
• volume_base number nullable
• volume_quote number nullable
• liquidity number nullable
• depth_negative_usd number nullable
• depth_positive_usd number nullable
• market_score number nullable
• market_reputation number nullable
• is_verified boolean (default: false)
• last_updated 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 — Coin 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.