/coingecko/coins/tickers

POST /api/coingecko/coins/tickers

Price: 5 credits

List the trading pairs (tickers) for a cryptocurrency across exchanges

How to use it

List the trading pairs (tickers) for a cryptocurrency by its CoinGecko coin id (e.g. 'bitcoin', not 'btc') across exchanges. Each ticker gives the base and target currencies, the exchange (market name and identifier), the last traded price, the trading volume, the price and volume converted to USD, the exchange trust score, the bid/ask spread, when the pair last traded, liquidity flags (anomaly, stale), the coin's USD market cap, the trade url, and the coin ids of both sides of the pair. 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)
• count integer required — Number of trading pairs to return (min: 1)

Response

• @type string (default: "CoingeckoTicker")
• base string nullable
• target string nullable
• market object nullable
  • @type string (default: "CoingeckoTickerMarket")
  • name string nullable
  • identifier string nullable
• last number nullable
• volume number nullable
• converted_last_usd number nullable
• converted_volume_usd number nullable
• trust_score string nullable
• bid_ask_spread_percentage number nullable
• timestamp string nullable
• last_traded_at string nullable
• is_anomaly boolean nullable
• is_stale boolean nullable
• coin_mcap_usd number nullable
• trade_url string nullable
• coin_id string nullable
• target_coin_id 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.