/coingecko/exchanges

POST /api/coingecko/exchanges

Price: 5 credits

Get details and trust metrics for a cryptocurrency exchange by its CoinGecko exchange id

How to use it

Get the profile of a cryptocurrency exchange by its CoinGecko exchange id (e.g. 'binance', 'gdax' for Coinbase Exchange). Returns name, year established, country, description, website, logo image, trust score and trust score rank, 24h trading volume in BTC, the number of coins and trading pairs listed, and social/other links (facebook, twitter, telegram, reddit, and two additional links). Use the search endpoint to resolve an exchange name to its id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Exchange id as used by CoinGecko (not the display name) (examples: "binance", "gdax", "kraken"; minLength: 1)

Response

• @type string (default: "CoingeckoExchange")
• id string required
• name string required
• year_established integer nullable
• country string nullable
• description string nullable
• url string nullable
• image string nullable
• has_trading_incentive boolean nullable
• is_centralized boolean nullable
• trust_score integer nullable
• trust_score_rank integer nullable
• trade_volume_24h_btc number nullable
• coin_count integer nullable
• pair_count integer nullable
• facebook_url string nullable
• twitter_url string nullable
• telegram_url string nullable
• reddit_url string nullable
• other_url_1 string nullable
• other_url_2 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 — Exchange 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.