/coinmarketcap/global-metrics

POST /api/coinmarketcap/global-metrics

Price: 1 credit

Get aggregate cryptocurrency market metrics (dominance, total market cap, volumes, counts)

How to use it

Get a single snapshot of the overall cryptocurrency market: Bitcoin and Ethereum dominance, total market capitalization (current and previous day), total 24h trading volume, altcoin market cap and 24h volume, DeFi market cap and 24h volume, stablecoin market cap and 24h volume, derivatives 24h volume, and counts of active/total cryptocurrencies, exchanges and active market pairs. All figures are denominated in USD.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)

Response

• @type string (default: "CoinmarketcapGlobalMetrics")
• btc_dominance number nullable
• eth_dominance number nullable
• total_market_cap number nullable
• total_volume_24h number nullable
• total_market_cap_yesterday number nullable
• altcoin_market_cap number nullable
• altcoin_volume_24h number nullable
• defi_market_cap number nullable
• defi_volume_24h number nullable
• stablecoin_market_cap number nullable
• stablecoin_volume_24h number nullable
• derivatives_volume_24h number nullable
• active_cryptocurrencies integer nullable
• active_exchanges integer nullable
• active_market_pairs integer nullable
• total_cryptocurrencies integer nullable
• total_exchanges integer nullable
• last_updated_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 — 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.