/coingecko/coins/chart

POST /api/coingecko/coins/chart

Price: 1 credit

Get the historical price, market cap, and volume time series for a cryptocurrency

How to use it

Get the historical market chart for a cryptocurrency by its CoinGecko coin id (e.g. 'bitcoin', not 'btc'). Returns a time series of points, each with a unix-millisecond timestamp and the price, market cap, and trading volume at that moment, denominated in the chosen currency. The 'days' parameter sets how far back the series reaches (up to 365 days); shorter ranges return finer-grained points. Points are ordered oldest to newest. Use the search endpoint to resolve a ticker symbol or name to a coin id.

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 id (not the ticker symbol). Resolve a symbol or name to an id via the search endpoint (examples: "bitcoin", "ethereum", "solana"; minLength: 1)
• days integer required — Number of days of history to return, counting back from now (min: 1; max: 365)
• vs_currency string — Currency to denominate prices in (default: "usd"; one of: "usd", "eur", "gbp", "jpy", "btc", "eth")

Response

• @type string (default: "CoingeckoChartPoint")
• timestamp integer required
• price number nullable
• market_cap number nullable
• volume number 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.