/coingecko/coins/markets

POST /api/coingecko/coins/markets

Price: 10 credits

List cryptocurrencies ranked by market capitalization with their market data

How to use it

List cryptocurrencies ranked by market capitalization (top coins) with a compact market snapshot for each: name, symbol, image, current price, market cap and rank, fully diluted valuation, trading volume, 24h high/low, all-time high/low with dates, supply figures, and price change percentages over multiple windows. Choose the sort order (market cap, trading volume, or coin id) and the currency. Each coin's 'id' can be passed to 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 (min: 1)
• vs_currency string — Currency to express price and market metrics in (default: "usd"; one of: "usd", "eur", "gbp", "jpy", "btc", "eth")
• order string — Sort order for the coin list (default: "market_cap_desc"; one of: "market_cap_desc", "market_cap_asc", "volume_desc", "volume_asc", "id_asc", "id_desc")

Response

• @type string (default: "CoingeckoCoinMarket")
• id string required
• symbol string required
• name string required
• image string nullable
• current_price number nullable
• market_cap number nullable
• market_cap_rank integer nullable
• fully_diluted_valuation number nullable
• total_volume number nullable
• high_24h number nullable
• low_24h number nullable
• price_change_24h number nullable
• price_change_percentage_24h number nullable
• market_cap_change_24h number nullable
• market_cap_change_percentage_24h number nullable
• price_change_percentage_1h number nullable
• price_change_percentage_7d number nullable
• price_change_percentage_14d number nullable
• price_change_percentage_30d number nullable
• price_change_percentage_200d number nullable
• price_change_percentage_1y number nullable
• circulating_supply number nullable
• total_supply number nullable
• max_supply number nullable
• ath number nullable
• ath_change_percentage number nullable
• ath_date string nullable
• atl number nullable
• atl_change_percentage number nullable
• atl_date string nullable
• roi object nullable
  • @type string (default: "CoingeckoMarketRoi")
  • times number nullable
  • currency string nullable
  • percentage number nullable
• 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 — 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.