/coinmarketcap/coins

POST /api/coinmarketcap/coins

Price: 5 credits

Get full details and market data for a cryptocurrency by its slug or numeric id

How to use it

Get the full profile of a cryptocurrency by its CoinMarketCap slug (e.g. 'bitcoin') or numeric id (e.g. 1). Returns name, symbol, description, category, image, tags, official links (website, source code, explorers, socials), the platforms/contracts it is issued on, and rich statistics: current price, market cap and rank, fully diluted market cap, market cap dominance, trading volume (24h/7d/30d), supply figures, 24h and 52-week high/low, all-time high/low with timestamps, and price change percentages over multiple windows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• slug string nullable — Coin slug (e.g. 'bitcoin'). Provide either slug or id (examples: "bitcoin")
• id integer nullable — Coin numeric id (e.g. 1 for Bitcoin). Provide either slug or id (examples: 1; min: 1)

Response

• @type string (default: "CoinmarketcapCoin")
• id integer required
• name string required
• symbol string required
• alias string nullable
• category string nullable
• description string nullable
• image string nullable
• status string nullable
• is_audited boolean (default: false)
• date_added string nullable
• date_launched string nullable
• watch_count integer nullable
• holder_count integer nullable
• daily_active_holder_count integer nullable
• tags array (default: [])
  • @type string (default: "CoinmarketcapTag")
  • slug string required
  • name string required
  • category string nullable
• platforms array (default: [])
  • @type string (default: "CoinmarketcapPlatform")
  • id integer nullable
  • name string nullable
  • chain_id integer nullable
  • contract_address string nullable
  • explorer_url string nullable
• urls object nullable
  • @type string (default: "CoinmarketcapUrls")
  • website array (default: [])
  • technical_doc array (default: [])
  • explorer array (default: [])
  • source_code array (default: [])
  • message_board array (default: [])
  • chat array (default: [])
  • announcement array (default: [])
  • reddit array (default: [])
  • facebook array (default: [])
  • twitter array (default: [])
• statistics object nullable
  • @type string (default: "CoinmarketcapCoinStatistics")
  • price 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
  • price_change_percentage_all number nullable
  • ytd_price_change_percentage number nullable
  • market_cap number nullable
  • market_cap_change_percentage_24h number nullable
  • fully_diluted_market_cap number nullable
  • market_cap_dominance number nullable
  • rank integer nullable
  • volume_rank integer nullable
  • circulating_supply number nullable
  • total_supply number nullable
  • max_supply number nullable
  • turnover number nullable
  • volume_24h number nullable
  • volume_7d number nullable
  • volume_30d number nullable
  • low_24h number nullable
  • high_24h number nullable
  • low_52w number nullable
  • high_52w number nullable
  • low_all_time number nullable
  • high_all_time number nullable
  • low_all_time_at string nullable
  • high_all_time_at 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.