# CoinGecko (/docs/nodes/data/coingecko) Token prices, pool data, OHLCV, trending tokens, and on-chain analytics via CoinGecko. CoinGecko provides comprehensive crypto market data. The CoinGecko node supports 25+ operations covering token prices, pool analytics, OHLCV charts, trending data, holder analysis, and DEX information. Prerequisites [#prerequisites] * CoinGecko API key ([coingecko.com/api](https://www.coingecko.com/en/api)) * Add as a credential in [Credentials](/docs/credentials/adding) * Set the `planType` field in your credential (`demo`, `analyst`, `lite`, or `pro`) Operations [#operations] | Operation | Description | Key inputs | | -------------------- | ---------------------------------- | ------------------------------------------ | | getTokenPrice | Get price for a token by address | address | | getBatchTokenPrice | Get prices for multiple tokens | addresses | | getTokenInfo | Get token metadata and stats | address | | getMultiTokenInfo | Get info for multiple tokens | addresses | | getPoolInfo | Get pool details | poolAddress | | getMultiPoolInfo | Get multiple pool details | poolAddresses | | getTrendingPools | List trending pools | duration, page | | getTopPools | List top pools by volume | page | | getNewPools | List newly created pools | page | | searchPools | Search pools by keyword | searchQuery, page | | megafilterPools | Advanced pool filtering | dexId, minLiquidity, minVolume, sortBy | | getPoolOHLCV | Get pool OHLCV candles | poolAddress, timeframe, aggregate, limit | | getTokenOHLCV | Get token OHLCV candles | address, timeframe, aggregate, limit | | getRecentTrades | Get recent trades for a pool | poolAddress | | listDexes | List all tracked DEXes | page | | getTopPoolsByDex | List top pools on a specific DEX | dexId, page | | getPoolTokenInfo | Get token info from pool context | poolAddress | | getTokenSecurityInfo | Get token security score | address | | getTopPoolsByToken | Get top pools for a token | address, page | | getTokenTrades | Get trades for a token | address | | getTokenHoldersChart | Get holder distribution chart | address, holdersChartDays | | getTopTokenHolders | Get top token holders | address, holdersCount | | getTopTokenTraders | Get top traders for a token | address, tradersCount | | getCoinOHLC | Get coin OHLC data by CoinGecko ID | coinId, vsCurrency, ohlcDays, ohlcInterval | Configuration [#configuration] | Field | Type | Required | Description | | ---------------- | ------ | ------------------------ | ----------------------------------------------------------------------------------- | | API Key | select | Yes | Your CoinGecko credential from Connections | | Response Name | text | Yes | Name used by downstream nodes, such as `{coingeckoResponse.data}` | | address | string | For most ops | Token contract address | | addresses | string | For batch ops | Comma-separated token addresses. Demo supports fewer addresses than paid plans | | poolAddress | string | For pool ops | Pool contract address | | poolAddresses | string | For multi pool | Comma-separated pool addresses | | searchQuery | string | For searchPools | Search keyword | | coinId | string | For getCoinOHLC | CoinGecko coin ID (e.g., `solana`) | | dexId | string | No | DEX identifier | | vsCurrency | string | No | Quote currency (default: `usd`) | | timeframe | string | No | Candle timeframe: `minute`, `hour`, `day` | | aggregate | number | No | OHLCV aggregation. Minute supports 1, 5, 15; hour supports 1, 4, 12; day supports 1 | | ohlcvCurrency | select | No | OHLCV currency: USD or token | | beforeTimestamp | number | No | Unix timestamp used to page OHLCV candles backward | | duration | select | No | Trending duration: 5m, 1h, 6h, or 24h | | page | number | No | Pagination page. Demo plan supports up to page 10 | | limit | number | No | OHLCV candle limit, max 1000 | | sortBy | string | No | Sort field for Megafilter Pools | | topPoolsSort | select | No | Top Pools sort: default, highest volume, or most transactions | | minVolume | number | No | Minimum volume filter | | minLiquidity | number | No | Minimum liquidity filter | | holdersChartDays | select | For getTokenHoldersChart | 7 days, 30 days, or Max | | holdersCount | number | For getTopTokenHolders | Number of holders to return, max 40 | | tradersCount | number | For getTopTokenTraders | Number of traders to return, max 50 | | ohlcDays | select | For getCoinOHLC | 1, 7, 14, 30, 90, 180, 365, or max depending on interval and plan | | ohlcInterval | select | No | Auto, daily, or hourly. Daily/hourly require a paid plan | Include options [#include-options] Several operations expose checkboxes that add richer data to the response: | Option | Available on | Description | | -------------------------------- | --------------------------------- | --------------------------------------------- | | Market Cap | getTokenPrice, getBatchTokenPrice | Adds market cap fields | | 24h Volume | getTokenPrice, getBatchTokenPrice | Adds 24h volume | | 24h Price Change % | getTokenPrice, getBatchTokenPrice | Adds 24h price change | | FDV Fallback for Market Cap | getTokenPrice, getBatchTokenPrice | Uses FDV when market cap is unavailable | | Total Reserve (USD) | getTokenPrice, getBatchTokenPrice | Adds reserve value | | Pool Composition | getTokenInfo, getPoolInfo | Adds related pool composition data | | Include Inactive Sources | getTokenInfo | Includes inactive token sources | | Volume Breakdown | getPoolInfo | Adds detailed pool volume breakdown | | Include Pool Context | getPoolTokenInfo | Adds pool context to token info | | Include Community Sentiment Data | getTrendingPools | Adds CoinGecko community sentiment data | | Include PnL Details | getTopTokenHolders | Adds holder profit/loss detail when available | Plan limits matter on some CoinGecko operations. Demo credentials use the demo API endpoint, paid plans use the pro endpoint, and some fields such as OHLC interval, `max` OHLC days, holder charts, top holders, and top traders may require a paid CoinGecko plan. Output [#output] CoinGecko returns a JSON:API envelope of the form `{ data, included?, meta? }`. The node unwraps it so downstream references don't need to traverse `data.data`: the inner `data` value is exposed at `.data`, and `included` / `meta` are surfaced as siblings when present. A typical response: ```json { "success": true, "operation": "getTokenPrice", "address": "So11111111111111111111111111111111111111112", "data": { /* inner JSON:API data (object or array) */ } } ``` Operations that take an `address` echo it at the top level. Reference fields with the response name (default `coingeckoResponse`), for example `{coingeckoResponse.data.attributes.token_prices.
}` for `getTokenPrice` or `{coingeckoResponse.data.attributes.name}` for `getTokenInfo`. Common use cases [#common-use-cases] * Comprehensive market data for multi-protocol analysis * Track new pool launches and trending tokens * Analyze holder distribution and whale movements Next steps [#next-steps] * [Birdeye](/docs/nodes/data/birdeye) - Solana-specific token analytics * [Dune](/docs/nodes/data/dune) - custom SQL queries on blockchain data