/coingecko/coins

POST /api/coingecko/coins

Price: 1 credit

Get full details and market data for a cryptocurrency by its CoinGecko coin id

How to use it

Get the full profile of a cryptocurrency by its CoinGecko coin id (e.g. 'bitcoin', not 'btc'). Returns name, symbol, description, categories, image, market cap rank, links (homepage, whitepaper, source code, social), and rich market data (current price, market cap, fully diluted valuation, trading volume, 24h high/low, all-time high/low with dates, supply figures, and price change percentages over multiple windows), plus community and developer activity metrics. 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)

Response

• @type string (default: "CoingeckoCoin")
• id string required
• symbol string required
• name string required
• alias string nullable
• image string nullable
• description string nullable
• categories array (default: [])
• market_cap_rank integer nullable
• hashing_algorithm string nullable
• genesis_date string nullable
• country_origin string nullable
• sentiment_votes_up_percentage number nullable
• sentiment_votes_down_percentage number nullable
• watchlist_portfolio_user_count integer nullable
• platforms object (default: {})
  • * string
• links object nullable
  • @type string (default: "CoingeckoLinks")
  • homepage string nullable
  • whitepaper string nullable
  • blockchain_site array (default: [])
  • official_forum_url array (default: [])
  • repos_url array (default: [])
  • subreddit_url string nullable
  • twitter_screen_name string nullable
  • telegram_channel_identifier string nullable
  • facebook_username string nullable
• market_data object nullable
  • @type string (default: "CoingeckoMarketData")
  • 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_1h number nullable
  • price_change_percentage_24h number nullable
  • price_change_percentage_7d number nullable
  • price_change_percentage_14d number nullable
  • price_change_percentage_30d number nullable
  • price_change_percentage_60d number nullable
  • price_change_percentage_200d number nullable
  • price_change_percentage_1y number nullable
  • market_cap_change_24h number nullable
  • market_cap_change_percentage_24h 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
  • total_value_locked number nullable
  • circulating_supply number nullable
  • total_supply number nullable
  • max_supply number nullable
  • last_updated string nullable
• community_data object nullable
  • @type string (default: "CoingeckoCommunityData")
  • twitter_follower_count integer nullable
  • reddit_subscriber_count integer nullable
  • reddit_average_posts_48h number nullable
  • reddit_average_comments_48h number nullable
  • reddit_accounts_active_48h number nullable
  • telegram_channel_user_count integer nullable
• developer_data object nullable
  • @type string (default: "CoingeckoDeveloperData")
  • fork_count integer nullable
  • star_count integer nullable
  • subscriber_count integer nullable
  • total_issue_count integer nullable
  • closed_issue_count integer nullable
  • pull_requests_merged_count integer nullable
  • pull_request_contributor_count integer nullable
  • commit_count_4_weeks integer 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.