> ## Documentation Index > Fetch the complete documentation index at: https://docs.coingecko.com/llms.txt > Use this file to discover all available pages before exploring further. # Changelog > Product updates and announcements ## New Endpoints: Onchain Price and Token Data across Networks πŸ—“οΈ **September 10, 2026** Query tokens on different networks in a single call, instead of one call per network. | Endpoint | Description | | :-------------------------------------------------------------------------- | :--------------------------------------------------------------- | | [/onchain/simple/token\_price/multi](/reference/onchain-simple-price-multi) | Token price by token contract addresses across networks | | [/onchain/tokens/multi](/reference/tokens-data-contract-addresses-multi) | Multiple tokens data by token contract addresses across networks | Both take a new `tokens` param, up to 50 `network_id:token_address` pairs: `?tokens=eth:0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2,`
`polygon_pos:0x0d500b1d8e8ef31e21c99d1db9a6444d3adf1270` > πŸ‘‘ Exclusive for Enterprise plan subscribers. [Contact sales β†’](https://www.coingecko.com/en/api/enterprise) *** ## Market Chart Endpoints: 1-Minutely Data with `interval=1m` πŸ—“οΈ **September 10, 2026** `interval=1m` now returns 1-minutely historical data on: * [/coins/\{id}/market\_chart](/reference/coins-id-market-chart) * [/coins/\{id}/market\_chart/range](/reference/coins-id-market-chart-range) * [/coins/\{id}/contract/\{contract\_address}/market\_chart](/reference/contract-address-market-chart) * [/coins/\{id}/contract/\{contract\_address}/market\_chart/range](/reference/contract-address-market-chart-range) `interval=1m` is capped at **1 day** per request, with data available from 1 June 2026 onward. > πŸ‘‘ Exclusive for Enterprise plan subscribers. [Contact sales β†’](https://www.coingecko.com/en/api/enterprise) *** ## Introducing Wallet Endpoints β€” Token Balances and Transfers by Wallet Address πŸ—“οΈ **September 9, 2026** CoinGecko now supports wallet-level onchain data via the API β€” every token a wallet holds, and the raw transfers behind those holdings. | Endpoint | Description | | :--------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------- | | [/onchain/wallets/\{address}/balances](/reference/wallet-token-balances) | Token balances of a wallet across networks, with USD value and liquidity per holding | | [/onchain/networks/\{network}/wallets
/\{address}/transfers](/reference/wallet-token-transfers) | Token transfers of a wallet on a network, cursor-paginated | Supported at launch on Ethereum, Base, BNB Chain, Polygon, Arbitrum, Optimism, Avalanche, Stable and Robinhood, with more networks and more [Wallets](/reference/onchain-wallets-overview) endpoints to follow. > πŸ’Ό Exclusive for [Analyst plan & above](https://www.coingecko.com/en/api/pricing) subscribers. *** ## Trades Endpoints: Cursor Pagination and `trading_period` Lookback πŸ—“οΈ **September 8, 2026** [Trades by Pool Address](/reference/pool-trades-contract-address) and [Trades by Token Address](/reference/token-trades-contract-address) now look back further than 24 hours and page through results with a cursor, lifting the previous 300-trade ceiling. | Param | Description | | :--------------- | :------------------------------------------------------------------------------ | | `trading_period` | Lookback period β€” `1d`, `7d` or `30d`. Defaults to `1d` | | `cursor` | Cursor from the previous response, passed back unchanged to fetch the next page | | `per_page` | Total results per page. Defaults to 300 | Responses now carry `meta.next_cursor` β€” pass it back as `cursor` to page through the full set of trades. > `trading_period`, `cursor` and `per_page` require [Analyst plan & above](https://www.coingecko.com/en/api/pricing).
> Both endpoints remain available to all paid plans, with [Trades by Pool Address](/reference/pool-trades-contract-address) also on [Demo](/demo/reference/endpoint-overview). *** ## New Endpoints: Trades within Time Range πŸ—“οΈ **September 7, 2026** Query onchain trades inside an absolute `from`/`to` window β€” for a named period such as March 2026, which a relative lookback cannot express. | Endpoint | Description | | :------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------- | | [/onchain/networks/\{network}/pools
/\{pool\_address}/trades/range](/reference/pool-trades-contract-address-range) | Trades within a time range by pool address | | [/onchain/networks/\{network}/tokens
/\{token\_address}/trades/range](/reference/token-trades-contract-address-range) | Trades within a time range across all pools by token address | `from` and `to` are both required, accept an ISO date string or a UNIX timestamp, and may span at most 30 days. Results are cursor-paginated through `meta.next_cursor`. > πŸ’Ό Exclusive for [Analyst plan & above](https://www.coingecko.com/en/api/pricing) subscribers. ## New CGSimplePrice Fields: Price Change Percentages, Circulating Supply & FDV πŸ—“οΈ **August 28, 2026** [CGSimplePrice](/websocket/cgsimpleprice) now streams six additional fields, included by default with no extra parameter. | Key | Field | Description | | :------ | :---------------------------- | :----------------------------------------------------- | | `pp7d` | `price_7d_change_percentage` | Price change percentage over the last 7 days | | `pp30d` | `price_30d_change_percentage` | Price change percentage over the last 30 days | | `pp60d` | `price_60d_change_percentage` | Price change percentage over the last 60 days | | `pp1y` | `price_1y_change_percentage` | Price change percentage over the last 1 year | | `cs` | `circulating_supply` | Circulating supply of coin | | `fdv` | `fully_diluted_value` | Fully diluted valuation in the specified `vs_currency` | ```json Example Payload highlight={7-10,12-13} theme={null} { "c": "C1", "i": "bitcoin", "vs": "usd", "p": 61696.67928656691, "pp": 1.4192404041947198, "pp7d": 3.8214, "pp30d": -2.1543, "pp60d": 12.4512, "pp1y": 120.8541, "m": 1236047139289.684, "cs": 19734150, "fdv": 1312500000000, "v": 30595921115.53988, "t": 1780839768 } ``` > [WebSocket](/websocket) requires [Basic plan & above](https://www.coingecko.com/en/api/pricing). *** ## Introducing RWA Endpoints β€” Aggregated Tokenized Market Data πŸ—“οΈ **August 27, 2026** CoinGecko now supports tokenized real world assets (RWAs) via the API β€” aggregated market data for tokenized stocks and commodities, and the issuers behind them. | Endpoint | Description | | :----------------------------------------------------------- | :--------------------------------------------------------------- | | [/rwas/list](/reference/rwas-list) | All supported RWAs with RWA ID, name and symbol | | [/rwas/markets](/reference/rwas-markets) | All RWAs with price, market cap, volume and market data | | [/rwas/\{id}](/reference/rwas-id) | Metadata, market data and tokens of an RWA | | [/rwas/\{id}/tickers](/reference/rwas-id-tickers) | RWA token tickers across centralized and decentralized exchanges | | [/rwas/\{id}/market\_chart](/reference/rwas-id-market-chart) | Historical price, market cap and volume | | [/rwas/issuers/list](/reference/rwas-issuers-list) | All supported RWA issuers with issuer ID and name | | [/rwas/issuers/\{id}](/reference/rwas-issuers-id) | Market data and tokens of an issuer | See live data on [Real World Assets](https://www.coingecko.com/en/real-world-assets), [Stocks](https://www.coingecko.com/en/stocks), and [Commodities](https://www.coingecko.com/en/commodities). All market data reflects the aggregated onchain tokenized market, not the underlying stock or commodity spot market. All values are in USD. > [/rwas/\{id}/tickers](/reference/rwas-id-tickers) and [/rwas/\{id}/market\_chart](/reference/rwas-id-market-chart) require **Basic plan and above**.
> All other RWA endpoints are available on every plan, including [Demo](/demo/reference/endpoint-overview). *** ## Upcoming Change Notice: Removal of community\_data and developer\_data πŸ—“οΈ **August 14, 2026** **Effective August 28, 2026**
The `community_data` and `developer_data` objects will be removed from the following endpoints: * [Coin Data by ID](/reference/coins-id) * [Coin Historical Data by ID](/reference/coins-id-history) * [Coin Data by Token Address](/reference/coins-contract-address) Until then, both objects remain in the response, but the values are no longer being updated and will stay stale. ```json What we're deprecating expandable theme={null} "community_data": { "facebook_likes": null, "reddit_average_posts_48h": 7.333, "reddit_average_comments_48h": 384.667, "reddit_subscribers": 6127543, "reddit_accounts_active_48h": 3498, "telegram_channel_user_count": null }, "developer_data": { "forks": 36433, "stars": 76697, "subscribers": 3967, "total_issues": 7743, "closed_issues": 7379, "pull_requests_merged": 11204, "pull_request_contributors": 829, "code_additions_deletions_4_weeks": { "additions": 1264, "deletions": -1314 }, "commit_count_4_weeks": 108, "last_4_weeks_commit_activity_series": [0, 3, 2, 0, 1, 0, 0] } ``` If your application relies on this, update your code to handle its absence. ## Pro API Update: More Consistent Historical Price Data Spacing πŸ—“οΈ **July 21, 2026** We're improving the historical data returned by the endpoints below so that 5-minute and hourly data points are interval-aligned, landing precisely on fixed interval boundaries (for example, exactly on the hour) rather than slightly before or after. This is a data-quality improvement: response schemas and structure are unchanged, and no request or response format changes are required on your end. **Who this affects** This rollout applies to all paid plan users: **Basic, Analyst, Lite, Pro, Pro+, and Enterprise**. Please refer to the rollout schedule below for the exact effective date and time for each plan tier. **Improved endpoints** * [/coins/:id/market\_chart](/reference/coins-id-market-chart) * [/coins/:id/market\_chart/range](/reference/coins-id-market-chart-range) * [/coins/:id/contract/:contract\_address/market\_chart](/reference/contract-address-market-chart) * [/coins/:id/contract/:contract\_address/market\_chart/range](/reference/contract-address-market-chart-range) * [/coins/:id/history](/reference/coins-id-history) * [/coins/:id/circulating\_supply\_chart](/reference/coins-id-circulating-supply-chart) * [/coins/:id/circulating\_supply\_chart/range](/reference/coins-id-circulating-supply-chart-range) **What's improving** * Previously, data points landed close to, but not exactly on, each interval boundary. For example, hourly data might return timestamps like: ```json theme={null} 1704067241 (2024-01-01 00:00:41) 1704070877 (2024-01-01 01:01:17) 1704074383 (2024-01-01 01:59:43) ``` * After the rollout, data points will land precisely on the interval boundary: ```json theme={null} 1704067200 (2024-01-01 00:00:00) 1704070800 (2024-01-01 01:00:00) 1704074400 (2024-01-01 02:00:00) ``` This makes historical series easier to align, join, and compare programmatically, without needing to round or bucket timestamps yourself. **What you need to do** Values, not structure, will change. The JSON schema and field structure for these endpoints stay exactly the same, so you don't need to update any parsing logic. What differs is the value returned for a given historical timestamp, since it now reflects the interval-aligned data point. | **Endpoints** | **Improved fields** | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------ | | [/coins/:id/market\_chart](/reference/coins-id-market-chart),
[/coins/:id/market\_chart/range](/reference/coins-id-market-chart-range),
[/coins/../contract/../market\_chart](/reference/contract-address-market-chart),
[/coins/../contract/../market\_chart/range](/reference/contract-address-market-chart-range) | `prices`,
`market_caps`,
`total_volumes` | | [/coins/:id/history](/reference/coins-id-history) | `market_data.current_price`,
`market_data.market_cap`,
`market_data.total_volume` | | [/coins/:id/circulating\_supply\_chart](/reference/coins-id-circulating-supply-chart),
[/coins/:id/circulating\_supply\_chart/range](/reference/coins-id-circulating-supply-chart-range) | `circulating_supply` | If you cache or store historical data locally, expect that re-querying a historical timestamp after your plan's effective date may return a value that differs slightly from what you previously stored, since it's now sourced from the corrected, interval-aligned timestamp. If your integration does exact-timestamp matching or joins against externally stored data, this change should make that easier and more reliable going forward, but double-check any logic written to accommodate the old unaligned timestamps. **Why values may look different β€” this is an improvement, not an error.**
If you compare historical values before and after this change, you may notice differences. This is expected: the new data pipeline sources prices more accurately than the previous system. We've measured and validated the new values against major assets and confirmed the differences fall within an acceptable, expected range.
If you see something that looks like an outlier beyond that, let us know by submitting a ticket at [support.coingecko.com](https://support.coingecko.com). **Rollout schedule** This will roll out progressively by plan tier: | **Plan** | **Effective time** | | --------------- | :-------------------------- | | Basic, Analyst | 4 August 2026, 02:00:00 UTC | | Lite, Pro, Pro+ | 5 August 2026, 02:00:00 UTC | | Enterprise | 6 August 2026, 02:00:00 UTC | No action is needed on your end during this window. *** ## Public API Update: More Consistent Historical Price Data Spacing πŸ—“οΈ **July 17, 2026** We're improving the historical data returned by the endpoints below so that 5-minute and hourly data points are interval-aligned, landing precisely on fixed interval boundaries (for example, exactly on the hour) rather than slightly before or after. This is a data-quality improvement: response schemas and structure are unchanged, and no request or response format changes are required on your end. **Who this affects** This rollout applies to **free-tier users only**, including both keyless (unauthenticated) requests and requests made with a registered Demo API key. If you're on a paid plan (Basic, Analyst, Lite, Pro/Pro+, or Enterprise), this change doesn't affect you yet. You'll be notified separately when it's extended to your plan, on its own schedule. **Improved endpoints** * [/coins/:id/market\_chart](/demo/reference/coins-id-market-chart) * [/coins/:id/market\_chart/range](/demo/reference/coins-id-market-chart-range) * [/coins/:id/contract/:contract\_address/market\_chart](/demo/reference/contract-address-market-chart) * [/coins/:id/contract/:contract\_address/market\_chart/range](/demo/reference/contract-address-market-chart-range) * [/coins/:id/history](/demo/reference/coins-id-history) **What's improving** * Previously, data points landed close to, but not exactly on, each interval boundary. For example, hourly data might return timestamps like: ```json theme={null} 1704067241 (2024-01-01 00:00:41) 1704070877 (2024-01-01 01:01:17) 1704074383 (2024-01-01 01:59:43) ``` * After the rollout, data points will land precisely on the interval boundary: ```json theme={null} 1704067200 (2024-01-01 00:00:00) 1704070800 (2024-01-01 01:00:00) 1704074400 (2024-01-01 02:00:00) ``` This makes historical series easier to align, join, and compare programmatically, without needing to round or bucket timestamps yourself. **What you need to do** Values, not structure, will change. The JSON schema and field structure for these endpoints stay exactly the same, so you don't need to update any parsing logic. What differs is the value returned for a given historical timestamp, since it now reflects the interval-aligned data point. | **Endpoints** | **Improved fields** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------ | | [/coins/:id/market\_chart](/demo/reference/coins-id-market-chart),
[/coins/:id/market\_chart/range](/demo/reference/coins-id-market-chart-range),
[/coins/../contract/../market\_chart](/demo/reference/contract-address-market-chart),
[/coins/../contract/../market\_chart/range](/demo/reference/contract-address-market-chart-range) | `prices`,
`market_caps`,
`total_volumes` | | [/coins/:id/history](/demo/reference/coins-id-history) | `market_data.current_price`,
`market_data.market_cap`,
`market_data.total_volume` | If you cache or store historical data locally, expect that re-querying a historical timestamp after the rollout may return a value that differs slightly from what you previously stored, since it's now sourced from the corrected, interval-aligned timestamp. If your integration does exact-timestamp matching or joins against externally stored data, this change should make that easier and more reliable going forward, but double-check any logic written to accommodate the old unaligned timestamps. **Why values may look different β€” this is an improvement, not an error.**
If you compare historical values before and after this change, you may notice differences. This is expected: the new data pipeline sources prices more accurately than the previous system. We've measured and validated the new values against major assets and confirmed the differences fall within an acceptable, expected range.
If you see something that looks like an outlier beyond that, let us know by submitting a ticket at [support.coingecko.com](https://support.coingecko.com). **Rollout: 02:00 UTC, 23 July 2026** This will roll out at 02:00 UTC on 23 July 2026 via phased deployment. Traffic will shift gradually over approximately 2 hours, so during this window some requests may be served by the improved pipeline while others are still served by the previous one. This is expected and temporary. Once the rollout completes, all traffic will be fully migrated to the improved pipeline. No action is needed on your end during this window. Other plans (Basic, Analyst, Lite, Pro, Pro+, Enterprise) will follow on a separate, staggered schedule to be announced. *** ## Pay for Your API Subscription with Crypto πŸ—“οΈ **July 14, 2026** You can now pay for an annual Analyst plan (or above) API subscription with crypto instead of a card. * Supported chains: **Solana**, **Ethereum**, **Base**, **Polygon**, **Arbitrum**, and **BNB Chain** * **USDC** and **USDT** are supported on every chain, with more available at checkout Learn more in [Pay with Crypto](/docs/crypto-payment). *** ## New Supported Chain: Robinhood for Top Token Holders πŸ—“οΈ **July 2, 2026** Robinhood chain is now supported on [Top Token Holders by Token Address](/reference/top-token-holders-token-address) and [Historical Token Holders Chart by Token Address](/reference/token-holders-chart-token-address). *** ## Robinhood Chain is now live on CoinGecko Onchain Data πŸ—“οΈ **July 1, 2026** * CoinGecko API now supports the Robinhood network across [onchain endpoints](/reference/endpoint-overview#onchain). Pass `robinhood` as the `network` parameter to query it like any other supported chain. * Prefer CoinGecko's aggregated coin data over onchain? You can also fetch Robinhood coins via [Token Lists](/reference/token-lists) (`asset_platform_id=robinhood`) or [Coins Markets](/reference/coins-markets) filtered to the Robinhood ecosystem category. * Robinhood joins our lineup as we keep pushing the widest chain coverage in the industry. ## Deprecation: VEF (Venezuelan BolΓ­var Fuerte) Currency πŸ—“οΈ **June 24, 2026** Starting June 30, 2026, we will begin a phased deprecation of the **VEF (Venezuelan BolΓ­var Fuerte)** currency across all API endpoints, affecting all query parameters and endpoint responses. This means that **only the specific data points involving VEF** will either be missing or inaccurate. To avoid any service disruptions, all clients must update their integrations and completely remove any dependencies on this deprecated currency **by June 30, 2026.** *** ## Top Token Traders: New `token_balance_desc` Sort Option πŸ—“οΈ **June 21, 2026** [Top Token Traders by Token Address](/reference/top-token-traders-token-address) now supports `token_balance_desc` as a `sort` option, allowing you to sort traders by their current remaining token balance. *** ## New Token Info Field: Banner Image URL πŸ—“οΈ **June 21, 2026** New `banner_image_url` field is now available on: * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Token Info by Token Address](/reference/pool-token-info-contract-address) ```json Example Payload highlight={8} theme={null} { "data": { "id": "solana_Dfh5DzRgSvvCFDoYc2ciTkMrbDfRKybA4SoFbPmApump", "type": "token", "attributes": { ... "image": { ... }, "banner_image_url": "https://assets.geckoterminal.com/kn680ou6904r03syp0ecu52ihy9c", "coingecko_coin_id": "pippin", ``` *** ## New Token Info Fields: Developer Address & Holding Percentage πŸ—“οΈ **June 16, 2026** [Token Info by Token Address](/reference/token-info-contract-address) and [Pool Token Info by Token Address](/reference/pool-token-info-contract-address) now include: * `developer_address` β€” developer wallet address * `developer_holding_percentage` β€” developer holding as a percentage of total supply ```json Example Payload highlight={4-5} theme={null} ... "freeze_authority": "no", "is_honeypot": "unknown", "developer_address": "4t7dHZcUzNC96d79won5TRZsvwP1bumhPNf3awR5BHdu", "developer_holding_percentage": "0.0" } ``` *** ## New Megafilter Parameters: Holder Count & Top Holders Percentage πŸ—“οΈ **June 15, 2026** [Megafilter for Pools](/reference/pools-megafilter) now supports filtering by holder count and top holder concentration: * `holder_count_min` / `holder_count_max` β€” filter pools by token holder count * `top_10_holders_percentage_min` / `top_10_holders_percentage_max` β€” filter by top 10 holders' percentage of total supply *** ## New Endpoint: Coin Supply Breakdown πŸ—“οΈ **June 10, 2026** New [/coins/\{id}/supply\_breakdown](/reference/coins-id-supply-breakdown) endpoint β€” query the supply breakdown of a coin, including non-circulating wallet addresses and balances. * Returns `supply_data` with total, circulating, non-circulating, and outstanding supply * Includes `non_circulating_wallets` with wallet address, label, balance, percentage of total supply, and anomaly flag * Use the new `has_supply_breakdown` field in [/coins/\{id}](/reference/coins-id) and [/coins/\{id}/contract/\{contract\_address}](/reference/coins-contract-address) to check if breakdown data is available for a coin ```json Example Payload expandable theme={null} { "id": "uniswap", "symbol": "uni", "name": "Uniswap", "supply_data": { "total_supply": 894488420.0329479, "circulating_supply": 622353561.5538775, "outstanding_supply": 0.0, "non_circulating_supply": 272134858.4790704, "last_updated": "2026-06-11T09:16:07.477Z" }, "non_circulating_wallets": [ { "address": "0x1a9C8182C09F50C8318d769245beA52c32BE35BC", "label": "UNI Timelock", "balance": 272134858.4790704, "percentage_of_total_supply": 30.423383405422996, "anomaly": false, "last_updated": "2026-06-11T06:14:14.076Z" } ] } ``` > πŸ’Ό Exclusive for paid plan subscribers (Analyst, Lite, Pro, and Enterprise). [View pricing β†’](https://www.coingecko.com/en/api/pricing) *** ## New Endpoint: Coin Insights πŸ—“οΈ **June 10, 2026** New [/insights](/reference/insights) endpoint β€” query the latest AI-generated coin insights on CoinGecko. * Filter by `coin_id`, `from`, and `to` date parameters ```json Example Payload theme={null} [ { "title": "BTC Prague 2026 Conference Goes Live", "description": "The BTC Prague 2026 conference is now live, featuring high-profile speakers and institutional attendance...", "related_coin_ids": ["bitcoin"], "posted_at": "2026-06-11T07:57:14.180091Z" } ] ``` > πŸ‘‘ Exclusive for Enterprise plan subscribers. [Contact sales β†’](https://www.coingecko.com/en/api/enterprise) ## Breaking Change: Sparkline Image URL Domain Migration for Trending Search πŸ—“οΈ **May 20, 2026** **Effective June 4, 2026** β€” `sparkline` image URLs returned by [Trending Search List](/reference/trending-search) are migrating from `www.coingecko.com` to `data.coingecko.com`. Affects the `sparkline` field across **coins**, **NFTs**, and **categories**: | Section | Before | After | | :--------- | :-------------------------------------------------------- | :--------------------------------------------------------- | | Coins | `https://www.coingecko.com/coins/{id}/sparkline.svg` | `https://data.coingecko.com/coins/{id}/sparkline.svg` | | NFTs | `https://www.coingecko.com/nft/{id}/sparkline.svg` | `https://data.coingecko.com/nft/{id}/sparkline.svg` | | Categories | `https://www.coingecko.com/categories/{id}/sparkline.svg` | `https://data.coingecko.com/categories/{id}/sparkline.svg` | If your application references or validates the sparkline URL domain, update your code to use `data.coingecko.com`. *** ## Introducing Webhooks β€” Real-Time Push Notifications for Coin Data Changes πŸ—“οΈ **May 19, 2026** CoinGecko now supports [Webhooks](/webhooks) β€” real-time push notifications to your server when data changes occur, eliminating constant API polling. * Supports the [`cg.coin.info.updated`](/webhooks/cg-coin-info-updated) event β€” triggers on updates to coin info (`name`, `symbol`, `categories`, `platforms`, `links`, `image`, `public_notices`, and more) * Set up via the [Developer Dashboard](https://www.coingecko.com/en/developers/dashboard#webhook) β€” payloads are signed with HMAC SHA256 * 10 credits per event delivery β€” retries are free * Up to 5 webhook endpoints per account > πŸ’Ό Exclusive for paid plan subscribers (Analyst, Lite, Pro, and Enterprise). [Learn more β†’](/webhooks) *** ## Higher Minute Rate Limits for Demo & Basic Plans πŸ—“οΈ **May 17, 2026** Requests-per-minute (RPM) rate limits have been increased: | Plan | Previous | New | | :---------- | :------: | :-----: | | Demo (Free) | 30 | **100** | | Basic | 250 | **300** | No action required β€” new limits are already in effect. *** ## Track Per-Key Monthly API Usage with `/key` Endpoint πŸ—“οΈ **May 17, 2026** [/key](/reference/api-usage) now returns `api_key_current_total_monthly_calls` β€” the total API calls made this month by the specific API key used to authenticate the request. ```json Example Payload highlight={8} theme={null} { "plan": "Other", "rate_limit_request_per_minute": 1000, "monthly_call_credit": 1000000, "current_total_monthly_calls": 104, "current_remaining_monthly_calls": 999896, ... "api_key_current_total_monthly_calls": 8 } ``` Available for accounts with custom per-key rate limits. [Contact sales](https://www.coingecko.com/en/api/enterprise) to set up per-key limits. ## Stay Ahead with the New Crypto News Endpoint πŸ—“οΈ **March 27, 2026** New [/news](/reference/news) endpoint β€” query crypto news and guides as seen on [CoinGecko News](https://www.coingecko.com/en/news). * Filter by `coin_id`, `language`, and `type` (news, guides, or both) * Pagination with `page` and `per_page` ```json Example Payload expandable theme={null} [ { "title": "Bitcoin stalls: Why BTC risks $65K fall despite $23M whale buy", "url": "https://ambcrypto.com/bitcoin-stalls-why-btc-risks-65k-fall-despite-23m-whale-buy/", "image": "https://assets.coingecko.com/articles/images/106731445/large/open-uri20260327-7-fuq6r9.?1774609423", "author": "Gladys Makena", "posted_at": "2026-03-27T11:00:42Z", "type": "news", "source_name": "AMBCrypto", "related_coin_ids": [ "1-token-2", "1-token", "bitcoin" ] } ] ``` > πŸ’Ό Exclusive for paid plan subscribers (Analyst, Lite, Pro, and Enterprise). *** ## CGSimplePrice WebSocket Now Supports `vs_currencies` πŸ—“οΈ **March 25, 2026** [CGSimplePrice](/websocket/cgsimpleprice) now supports `vs_currencies` to specify preferred exchange rates. Choose from any currency supported by [/simple/supported\_vs\_currencies](/reference/simple-supported-currencies). Defaults to USD if not specified. A new `vs` field in every response indicates the target currency. **Input:** ```json theme={null} { "command": "message", "identifier": "{\"channel\":\"CGSimplePrice\"}", "data": "{\"coin_id\":[\"ethereum\",\"bitcoin\"],\"vs_currencies\":[\"usd\",\"eur\"],\"action\":\"set_tokens\"}" } ``` **Response:** ```json highlight={4} theme={null} { "c": "C1", "i": "ethereum", "vs": "usd", "m": 312938652962.8005, "p": 2591.080889351465, "pp": 1.3763793110454519, "t": 1747808150.269067, "v": 20460612214.801384 } ``` *** ## `interval=hourly` Now Available for All Plans on Coin Market Chart Endpoints πŸ—“οΈ **March 24, 2026** `interval=hourly` is now accessible to all API users (Demo, Basic, Analyst & above) on: * [/coins/\{id}/market\_chart](/reference/coins-id-market-chart) β€” hourly data up to the **past 100 days** * [/coins/\{id}/market\_chart/range](/reference/coins-id-market-chart-range) β€” hourly data up to **any 100-day** range per request Previously restricted to Enterprise subscribers. The `interval=5m` parameter remains Enterprise-only. *** ## GT Verified Badge & Outstanding Token Value for Coin Endpoints πŸ—“οΈ **March 23, 2026** ### New `gt_verified` Field New `gt_verified` boolean field on [Token Info by Token Address](/reference/token-info-contract-address) and [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address). [Learn more about GT Verified β†’](https://support.coingecko.com/hc/en-us/articles/54413671274649-What-is-GT-Verified-Badge) ```json Example Payload highlight={4} theme={null} { ... "gt_score": 92.6605504587156, "gt_verified": true, "discord_url": null, ... } ``` ### New `outstanding_token_value_usd` & `outstanding_supply` Fields Two new fields in `market_data` for [Coin Data by ID](/reference/coins-id) and [Coin Data by Token Address](/reference/coins-contract-address): * `outstanding_token_value_usd` β€” outstanding token value in USD (nullable) * `outstanding_supply` β€” tokens outstanding in the market, including circulated/tradable or planned-for-circulation tokens (nullable) ```json Example Payload highlight={3,7} theme={null} "market_data": { "market_cap_rank": 1, "outstanding_token_value_usd": null, ... "circulating_supply": 19675962, "total_supply": 21000000, "outstanding_supply": 20003043.0, ... } ``` ## Comprehensive Token Holder Analytics with PnL Details πŸ—“οΈ **February 25, 2026** [Top Token Holders by Token Address](/reference/top-token-holders-token-address) now supports `include_pnl_details=true` to return PnL metrics and trading analytics for each holder: * `average_buy_price_usd` β€” average purchase price per token * `total_buy_count` / `total_sell_count` β€” transaction counts * `unrealized_pnl_usd` / `unrealized_pnl_percentage` β€” unrealized P\&L * `realized_pnl_usd` / `realized_pnl_percentage` β€” realized P\&L * `explorer_url` β€” link to the holder's address on the blockchain explorer ```json Example Payload expandable highlight={15-22} theme={null} { "data": { "id": "base_0x6921b130d297cc43754afba22e5eac0fbf8db75b", "type": "top_holder", "attributes": { "last_updated_at": "2026-02-16T09:56:34.328Z", "holders": [ { "rank": 1, "address": "0x56bbe4200fdd412854bcf05f2c992827b64ee5c1", "label": null, "amount": "9703812154.0", "percentage": "14.3507", "value": "966572.07", "average_buy_price_usd": null, "total_buy_count": null, "total_sell_count": null, "unrealized_pnl_usd": null, "unrealized_pnl_percentage": null, "realized_pnl_usd": null, "realized_pnl_percentage": null, "explorer_url": "https://basescan.org/address/0x56bbe4200fdd412854bcf05f2c992827b64ee5c1" }, ``` *** ## Enhanced Pool Discovery and Treasury Analytics with New Sorting and Holdings Metrics πŸ—“οΈ **February 12, 2026** ### New Sort Options for Megafilter [Megafilter for Pools](/reference/pools-megafilter) now supports four new sort options: `price_asc`, `price_desc`, `h24_tx_count_asc`, `h24_volume_usd_asc` ### Enriched Treasury Holdings Data [Crypto Treasury Holdings by Entity ID](/reference/public-treasury-entity) now returns additional financial metrics by default: * `total_treasury_value_usd`, `unrealized_pnl`, `m_nav`, `total_asset_value_per_share_usd` * Per-holding: `amount_per_share`, `entity_value_usd_percentage`, `current_value_usd`, `total_entry_value_usd`, `average_entry_value_usd`, `unrealized_pnl` ```json Example Payload expandable highlight={9-12,18-23} theme={null} { "name": "Strategy", "id": "strategy", "type": "company", "symbol": "MSTR.US", "country": "US", "website_url": "https://www.strategy.com/", "twitter_screen_name": "Strategy", "total_treasury_value_usd": 48119580010.663155, "unrealized_pnl": -6554973853.336845, "m_nav": 0.99, "total_asset_value_per_share_usd": 150.46302495438903, "holdings": [ { "coin_id": "bitcoin", "amount": 714644.0, "percentage_of_total_supply": 3.403, "amount_per_share": 0.0022345892873893874, "entity_value_usd_percentage": 100.0, "current_value_usd": 48119580010.663155, "total_entry_value_usd": 54674553864.0, "average_entry_value_usd": 76506.0, "unrealized_pnl": -6554973853.336845 } ] } ``` **New optional parameters for historical tracking:** * `holding_amount_change` β€” absolute holding changes over time * `holding_change_percentage` β€” percentage changes in holdings * Supported timeframes: `7d`, `14d`, `30d`, `90d`, `1y`, `ytd` (comma-separated) ```json Example Payload expandable highlight={14-29} theme={null} ... "total_asset_value_per_share_usd": 150.46302495438903, "holdings": [ { "coin_id": "bitcoin", "amount": 714644.0, "percentage_of_total_supply": 3.403, "amount_per_share": 0.0022345892873893874, "entity_value_usd_percentage": 100.0, "current_value_usd": 48119580010.663155, "total_entry_value_usd": 54674553864.0, "average_entry_value_usd": 76506.0, "unrealized_pnl": -6554973853.336845, "holding_amount_change": { "7d": 1142.0, "14d": 1997.0, "30d": 27234.0, "90d": 72952.0, "1y": 235904.0, "ytd": 42144.0 }, "holding_change_percentage": { "7d": 0.16, "14d": 0.28, "30d": 3.962, "90d": 11.369, "1y": 49.276, "ytd": 6.267 } } ] } ``` ## \[Upcoming Change] Starknet Address Format Update πŸ—“οΈ **January 30, 2026** **Effective February 10, 2026, 02:00 UTC** β€” Starknet addresses (tokens and pools) are being standardized to the **padded format** (66 characters). This only affects onchain API endpoints and onchain WebSocket channels. | Feature | Change | | :--------------- | :-------------------------------------------------------- | | API Responses | All address fields return in **padded format** (`0x0...`) | | API Requests | Both padded and unpadded formats accepted | | WebSockets | Broadcasted messages use **padded format** | | WS Subscriptions | Both padded and unpadded formats accepted | ### Padded vs. Unpadded * **Unpadded:** `0x4718...` (65 characters) * **Padded:** `0x04718...` (66 characters) ### Impact * **API requests** continue to work with unpadded addresses β€” the system normalizes inputs automatically * **String matching** β€” if your app performs strict comparisons, normalize addresses to a consistent length before comparing * **Data storage** β€” future records will include the padding > This change is specific to **Starknet**. Address formats for other chains remain unaffected. *** ## Streamlined Notification Management with Multi-Recipient Email Alerts πŸ—“οΈ **January 27, 2026** Account owners can now add multiple email recipients for billing alerts and usage threshold notifications from the [Notifications](https://www.coingecko.com/en/developers/dashboard#notifications) dashboard tab. Recipients don't need CoinGecko accounts. **Available on:** Analyst plans and above (expanded recipient limits for Enterprise). [Learn more β†’](https://support.coingecko.com/hc/en-us/articles/54516497903129-How-to-Manage-API-Email-Recipients) *** ## Enhanced Team Collaboration with Role-Based Dashboard Access πŸ—“οΈ **January 26, 2026** Invite team members to collaborate on your API subscription via the [Access](https://www.coingecko.com/en/developers/dashboard#access) dashboard tab β€” no shared login credentials needed. Collaborators can: * Manage API keys * Monitor credit usage across API and WebSocket * Access billing details from the Stripe portal A dashboard switcher lets users toggle between multiple team views. **Available on:** All plans (increased seat limits for higher tiers). **Learn more:** * [How to Manage Team Access on Your API Dashboard](https://support.coingecko.com/hc/en-us/articles/54503844273945-How-to-Manage-Team-Access-on-Your-API-Dashboard) * [Team Access for API Plans FAQ](https://support.coingecko.com/hc/en-us/articles/54503941840025-Team-Access-for-API-Plans-FAQ) *** ## Advanced Filtering with Pagination for Treasury Data and Price Change Filters for Megafilter πŸ—“οΈ **January 22, 2026** ### Pagination and Sorting for Public Treasury [Crypto Treasury Holdings by Coin ID](/reference/companies-public-treasury) now supports: * `per_page` β€” results per page (1–250, default: 250) * `page` β€” paginate through results (default: 1) * `order` β€” `total_holdings_usd_desc` (default) or `total_holdings_usd_asc` ### Price Change Filters for Megafilter [Megafilter for Pools](/reference/pools-megafilter) now supports filtering by price change percentage: * `price_change_percentage_min` β€” minimum threshold * `price_change_percentage_max` β€” maximum threshold * `price_change_percentage_duration` β€” time window: `5m`, `1h`, `6h`, `24h` *** ## Enhanced Market Analytics with Volume Change Tracking and Historical OHLC for Inactive Coins πŸ—“οΈ **January 21, 2026** ### Volume Change Percentage for Global Market Data New `volume_change_percentage_24h_usd` field in [Crypto Global Market Data](/reference/crypto-global): ```json Example Payload highlight={3} theme={null} { "market_cap_change_percentage_24h_usd": 0.7227196786856437, "volume_change_percentage_24h_usd": -0.2692391926571914, "updated_at": 1769062741 } ``` ### Historical OHLC for Inactive Coins Historical candlestick data is now available for inactive and delisted coins: * [Coin OHLC by ID](/reference/coins-id-ohlc) * [Coin OHLC Range by ID](/reference/coins-id-ohlc-range) *** ## Expanded WebSocket Streaming with New Intervals and Quote Token Data πŸ—“οΈ **January 20, 2026** ### New Intervals for OnchainOHLCV [OnchainOHLCV](/websocket/onchainohlcv) now supports three new intervals: `15m`, `12h`, `1d` Complete interval options: `1s`, `1m`, `5m`, `15m`, `1h`, `2h`, `4h`, `8h`, `12h`, `1d` ### Quote Token Amount for OnchainTrade New `toq` (quote\_token\_amount) field in [OnchainTrade](/websocket/onchaintrade) β€” the amount of quote token transacted in each swap: ```json Example Payload highlight={7} theme={null} { "c": "G2", "n": "bsc", "pa": "0x172fcd41e0913e95784454622d1c3724f546f849", "ty": "b", "to": 11.0818733869477, "toq": 0.0124384489204242, "vo": 11.0724584599832, "tx": "0xbc6afc1584fcbef90efe69b96602ef3ba4778727bacfdfece46bbbb075721bb4" } ``` *** ## Breaking Change: Ticker Trust Score Deprecation πŸ—“οΈ **January 19, 2026** **Effective March 3, 2026** β€” the `trust_score` field (previously `green`, `yellow`, or `red`) now returns `null` across all affected endpoints: * [Coin Tickers by ID](/reference/coins-id-tickers) * [Exchange Tickers by ID](/reference/exchanges-id-tickers) * [Exchange Data by ID](/reference/exchanges-id) * [Coin Data by ID](/reference/coins-id) * [Coin Data by Token Address](/reference/coins-contract-address) ```json Example Payload highlight={4} theme={null} "trust_score": null, "bid_ask_spread_percentage": 0.010014, "timestamp": "2024-04-08T04:02:01+00:00", ``` If your application relies on `trust_score`, update your code to handle `null` values. ## Access Inactive Token Data with New `include_inactive_source` Parameter πŸ—“οΈ **December 16, 2025** New `include_inactive_source` query parameter for retrieving data on tokens with no active pools (no valid swaps in the past 7 days). When set to `true`, the API sources data from the pool with the most recent swap, regardless of age. **Updated endpoints:** * [Token Data by Token Address](/reference/token-data-contract-address) and [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) β€” new `last_trade_timestamp` field: ```json Example Payload highlight={2} theme={null} "market_cap_usd": "1544052409.96629", "last_trade_timestamp": 1712534400 ``` * [Top Pools by Token Address](/reference/top-pools-contract-address) β€” new `last_trade_timestamp` field: ```json Example Payload highlight={2} theme={null} "reserve_in_usd": "163988541.3812", "last_trade_timestamp": 1712534400 ``` * [Token Price by Token Addresses](/reference/onchain-simple-price) β€” new `last_trade_timestamp` object: ```json Example Payload highlight={4-6} theme={null} "total_reserve_in_usd": { "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "1576179559.946697" }, "last_trade_timestamp": { "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": 1712534400 } ``` * [Token OHLCV Chart by Token Address](/reference/token-ohlcv-token-address) β€” no payload changes *** ## Upcoming Changes to Market Cap Rankings and API for Rehypothecated Tokens πŸ—“οΈ **December 15, 2025** Changes to how rehypothecated tokens (wrapped assets, liquid staking tokens) are ranked in market cap data. [Read the full announcement β†’](https://www.coingecko.com/learn/upcoming-changes-to-market-cap-rankings-and-api-for-rehypothecated-tokens) **Effective February 4, 2026.** If your application does not handle rehypothecated tokens specifically, no action is required. ### Coin Data by ID and Coin Data by Token Address [/coins/\{id}](/reference/coins-id) and [/coins/\{id}/contract/\{contract\_address}](/reference/coins-contract-address): * **Breaking:** `market_cap_rank` returns `null` for rehypothecated tokens * **New field:** `market_cap_rank_with_rehypothecated` β€” available in both the parent object and `market_data` ```json Example Payload highlight={3,7} theme={null} { "market_cap_rank": 1, "market_cap_rank_with_rehypothecated": 1, "market_data": { ... "market_cap_rank": 1, "market_cap_rank_with_rehypothecated": 1, "fully_diluted_valuation": { ... } } } ``` ### Coins List with Market Data [/coins/markets](/reference/coins-markets): * **Breaking:** Rehypothecated tokens are **excluded by default** (when using `category`, they're included but `market_cap_rank` returns `null`) * **New parameter:** `include_rehypothecated` (boolean, default: `false`) * **New field (conditional):** `market_cap_rank_with_rehypothecated` β€” only present when `include_rehypothecated=true` ```json Example Payload highlight={4} theme={null} { "market_cap_rank": 1, "last_updated": "2026-02-05T08:44:05.527Z", "market_cap_rank_with_rehypothecated": 1 } ``` *** ## New Top Traders by Token Address Endpoint πŸ—“οΈ **December 4, 2025** [Top Traders by Token Address](/reference/top-token-traders-token-address) β€” monitor whale activity, track significant holders, and analyze trading patterns for any token. ```json Example Payload expandable theme={null} { "data": { "id": "base_0x6921b130d297cc43754afba22e5eac0fbf8db75b", "type": "top_trader", "attributes": { "traders": [ { "address": "0xf748879edbe8cca140940788163d7be4d2a2e46a", "name": "@zimagetsfox", "label": "zimagetsfox.eth", "type": "other", "realized_pnl_usd": "1157358.77", "unrealized_pnl_usd": "255071.37", "token_balance": "1454984.43", "average_buy_price_usd": "0.01144", "average_sell_price_usd": "0.03460", "total_buy_count": 48, "total_sell_count": 109, "total_buy_token_amount": "51422264.86", "total_sell_token_amount": "49967280.42", "total_buy_usd": "588308.47", "total_sell_usd": "1729021.16", "explorer_url": "https://etherscan.io/address/0xf748879edbe8cca140940788163d7be4d2a2e46a" } ] } } } ``` ## New Public Treasury Endpoints: Historical Holdings and Transactions History πŸ—“οΈ **November 27, 2025** Two new treasury endpoints β€” both support ID lookup via entity or coin IDs. See live data at [coingecko.com/en/treasuries/companies/strategy](https://www.coingecko.com/en/treasuries/companies/strategy). ### Historical Holdings Chart [Crypto Treasury Holdings Historical Chart Data by ID](/reference/public-treasury-entity-chart) β€” query historical holdings for public companies and governments. ```json Example Payload theme={null} { "holdings": [ [1763683200000, 649870.0], ... ], "holding_value_in_usd": [ [1763683200000, 56311217680.033195], ... ] } ``` ### Transaction History [Crypto Treasury Transaction History by Entity ID](/reference/public-treasury-transaction-history) β€” retrieve detailed transaction history. ```json Example Payload expandable theme={null} { "transactions": [ { "date": 1763337600000, "source_url": "https://assets.contentstack.io/v3/assets/.../form-8-k_11-17-2025.pdf", "coin_id": "bitcoin", "type": "buy", "holding_net_change": 8178.0, "transaction_value_usd": 835554438.0, "holding_balance": 649870.0, "average_entry_value_usd": 102171.0 } ] } ``` *** ## GT Community Data for More Pool Endpoints, plus Farcaster and Zora Social URL Support πŸ—“οΈ **November 15, 2025** ### GT Community Data for More Pool Endpoints Flag `include_gt_community_data=true` to receive sentiment voting and community reporting data: ```json Example Payload highlight={2-4} theme={null} "reserve_in_usd": "163988541.3812", "sentiment_vote_positive_percentage": 60, "sentiment_vote_negative_percentage": 40, "community_sus_report": 18 ``` Improved endpoints: * [Trending Pools List](/reference/trending-pools-list) * [New Pools by Network](/reference/latest-pools-network) * [Trending Pools by Network](/reference/trending-pools-network) * [Top Pools by Network](/reference/top-pools-network) * [Top Pools by DEX](/reference/top-pools-dex) * [New Pools List](/reference/latest-pools-list) ### Farcaster and Zora Social URLs `farcaster_url` and `zora_url` fields are now included by default in token info endpoints: ```json Example Payload highlight={2-3} theme={null} "discord_url": null, "farcaster_url": null, "zora_url": null, "telegram_handle": null, ``` * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) *** ## True Real-Time Data Update: Cache Removed for Key On-chain Endpoints πŸ—“οΈ **November 14, 2025** > Applicable to all [paid plan](https://www.coingecko.com/en/api/pricing) subscribers. The 10-second edge cache has been **completely removed** for the following endpoints β€” requests now return data directly from origin with zero cache delay: | Effective From | Endpoints | | :--------------- | :------------------------------------------------------------------------------- | | December 1, 2025 | [Token Price by Token Addresses](/reference/onchain-simple-price) | | December 2, 2025 | [Past 24 Hour Trades by Pool Address](/reference/pool-trades-contract-address) | | December 3, 2025 | [Past 24 Hour Trades by Token Address](/reference/token-trades-contract-address) | Requests that hit the origin server may use additional credits. To avoid extra credit usage, maintain a polling interval of 10 seconds or more. *** ## Onchain OHLCV Support Extended to Pools with 3+ Tokens πŸ—“οΈ **November 8, 2025** Onchain OHLCV endpoints now support pools with more than 2 tokens β€” e.g. [crvUSD/WETH/CRV](https://www.geckoterminal.com/eth/pools/0x4ebdf703948ddcea3b11f675b4d1fba9d2414a14). * [Pool OHLCV Chart by Pool Address](/reference/pool-ohlcv-contract-address) * [Token OHLCV Chart by Token Address](/reference/token-ohlcv-token-address) ## WebSocket is now supported for Self-serve API subscribers πŸ—“οΈ **October 23, 2025** ### WebSocket (Beta) for Paid Plan Subscribers Self-serve customers (Analyst, Lite, Pro, Pro+) can now stream real-time data via [WebSocket](/websocket) using monthly API plan credits: * **Max connections:** 10 concurrent sockets * **Max subscriptions:** 100 token or pool subscriptions per channel, per socket * **Channel access:** [all 4 channels](/websocket#channel-%26-data-support) * **Credit charge:** 0.1 credit per response ### Notice: Temporary MagicEden NFT Data Disruption Due to MagicEden API updates, NFT data endpoints may temporarily return incomplete data while the integration is updated. *** ## More Bonding Curve Support and New Ascending Sort for Megafilter πŸ—“οΈ **October 4, 2025** ### Bonding Curve Data for More Endpoints Bonding curve (launchpad graduation) data is now available on token endpoints: * [Token Data by Token Address](/reference/token-data-contract-address) * [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) ```json Example Payload theme={null} "launchpad_details": { "graduation_percentage": 2.16, "completed": false, "completed_at": null, "migrated_destination_pool_address": null } ``` ### Megafilter: Ascending Sort for Price Change % [Megafilter for Pools](/reference/pools-megafilter) now supports ascending sort options: `m5_price_change_percentage_asc`, `h1_price_change_percentage_asc`, `h6_price_change_percentage_asc`, `h24_price_change_percentage_asc` ### Token OHLCV: Bug Fix Fixed an issue where [Token OHLCV Chart by Token Address](/reference/token-ohlcv-token-address) returned data for the base token of the top pool instead of the requested token. ## SDK Gains Public Treasury Coverage, MCP Adds Exchanges, NFTs, and ISO Support πŸ—“οΈ **September 25, 2025** ### Expanded SDK Coverage for Public Treasuries New functions in the [TypeScript SDK](https://github.com/coingecko/coingecko-typescript): * [`publicTreasury.getCoinID(coinID, { ...params })`](https://github.com/coingecko/coingecko-typescript/blob/main/api.md#publictreasury) β€” query holdings by Coin ID * [`publicTreasury.getEntityID(entityID)`](https://github.com/coingecko/coingecko-typescript/blob/main/api.md#publictreasury) β€” query holdings by Entity ID * [`entities.getList({ ...params })`](https://github.com/coingecko/coingecko-typescript/blob/main/api.md#entities) β€” list all supported entities with ID, name, symbol, and country ### New MCP Tools: Exchanges, NFTs & Multi-Address Queries New tools: * Exchange coverage: [/exchanges/list](/reference/exchanges-list), [/exchanges/\{id}](/reference/exchanges-id), [/exchanges/\{id}/tickers](/reference/exchanges-id-tickers), [/exchanges/\{id}/volume\_chart/range](/reference/exchanges-id-volume-chart-range) * NFT markets: [/nfts/markets](/reference/nfts-markets) * Multi-address queries: [/onchain/networks/\{network}/pools/multi/\{addresses}](/reference/pools-addresses), [/onchain/networks/\{network}/tokens/multi/\{addresses}](/reference/tokens-data-contract-addresses) Retired tools: * Removed [/coins/list](/reference/coins-list), [/onchain/networks/trending\_pools](/reference/trending-pools-network), and single-address pool/token queries in favor of multi-address endpoints ### MCP: ISO Date String Support MCP tools now accept **ISO date strings** (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM`) alongside UNIX timestamps β€” no more manual conversion for time-based queries like [Coin Historical Chart Data within Time Range](/reference/coins-id-market-chart-range). *** ## New Crypto Treasury Endpoints and Improvements πŸ—“οΈ **September 19, 2025** 1. [Crypto Treasury Holdings by Coin ID](/reference/companies-public-treasury) now supports governments and more coins β€” see [coingecko.com/en/treasuries/bitcoin](https://www.coingecko.com/en/treasuries/bitcoin) 2. **New endpoints:** * [Crypto Treasury Holdings by Entity ID](/reference/public-treasury-entity) * [Entities List (ID Map)](/reference/entities-list) 3. [Derivatives Exchange Data by ID](/reference/derivatives-exchanges-id) now supports `coin_id` and `target_coin_id` to identify coins of ticker pairs: ```json Example Payload highlight={6-7} theme={null} "tickers": [ { "symbol": "ASTERUSDT", "base": "ASTER", "target": "USDT", "coin_id": "aster-2", "target_coin_id": "tether" } ] ``` *** ## Multiple Improvements: Bonding Curve Data, Pooled Token Balance, and More πŸ—“οΈ **September 12, 2025** ### Bonding Curve Data Launchpad graduation data is now available on [Specific Pool Data by Pool Address](/reference/pool-address) and [Multiple Pools Data by Pool Addresses](/reference/pools-addresses): ```json Example Payload theme={null} "launchpad_details": { "graduation_percentage": 100, "completed": true, "completed_at": "2024-04-08T16:52:35Z", "migrated_destination_pool_address": "5wNu5QhdpRGrL37ffcd6TMMqZugQgxwafgz477rShtHy" } ``` ### Pooled Token Balance Data Flag `include_composition=true` to get pool token balance breakdowns: * [Specific Pool Data by Pool Address](/reference/pool-address) * [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) * [Token Data by Token Address](/reference/token-data-contract-address) (also requires `include=top_pools`) * [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) (also requires `include=top_pools`) ```json Example Payload theme={null} "base_token_balance": "11700.98", "base_token_liquidity_usd": "29630000", "quote_token_balance": "66384614.21", "quote_token_liquidity_usd": "66330000", ``` ### Other Improvements * [Megafilter for Pools](/reference/pools-megafilter) β€” new `sort` options: `m5_price_change_percentage_desc`, `h1_price_change_percentage_desc`, `h6_price_change_percentage_desc`, `fdv_usd_asc`, `fdv_usd_desc`, `reserve_in_usd_asc`, `reserve_in_usd_desc` * [Top Gainers & Losers](/reference/coins-top-gainers-losers) β€” new `price_change_percentage` parameter with options: `1h`, `24h`, `7d`, `14d`, `30d`, `60d`, `200d`, `1y` ```json Example Payload theme={null} "usd_1y_change": 21740.8866287307, "usd_1h_change": -0.279590756868549, "usd_24h_change": 3.13876587906131, "usd_7d_change": -9.67782096261206, "usd_14d_change": -3.39755498745517, "usd_30d_change": -13.7768698159765, "usd_60d_change": 29.9096824213076, "usd_200d_change": 2282.33681679488 ``` * [Exchange Tickers by ID](/reference/exchanges-id-tickers) β€” new `order` options: `market_cap_desc`, `market_cap_asc` ## Improved Update Frequency for selected Pro-API On-chain Endpoints πŸ—“οΈ **August 18, 2025** > Applicable to all [paid plan](https://www.coingecko.com/en/api/pricing) subscribers. Edge cache durations for the following onchain endpoints have been reduced from 30s to **10s**: | Effective From | Endpoints | | :---------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | September 2, 2025 | [Token Price by Token Addresses](/reference/onchain-simple-price)
[Token Data by Token Address](/reference/token-data-contract-address)
[Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) | | September 3, 2025 | [Specific Pool Data by Pool Address](/reference/pool-address)
[Multiple Pools Data by Pool Addresses](/reference/pools-addresses) | | September 4, 2025 | [Pool OHLCV Chart by Pool Address](/reference/pool-ohlcv-contract-address)
[Token OHLCV Chart by Token Address](/reference/token-ohlcv-token-address)
[Past 24 Hour Trades by Pool Address](/reference/pool-trades-contract-address)
[Past 24 Hour Trades by Token Address](/reference/token-trades-contract-address) | Cached responses incur no extra credits. Requests that bypass the cache and hit the origin server may use additional credits β€” adjust your polling interval accordingly. *** ## Now Supported: Launchpad Data (Pump.fun & More), Granular OHLCV, and Honeypot Info πŸ—“οΈ **August 5, 2025** ### Launchpad Data (Pump.fun & More) Token data from popular launchpad platforms is now available through the API: | Launchpad | Network | DEX ID | | :---------------------------------------------------------------------------------------------- | :------ | :------------------ | | [Meteora DBC](https://www.geckoterminal.com/solana/meteora-dbc/pools) | solana | `meteora-dbc` | | [Pump.fun](https://www.geckoterminal.com/solana/pump-fun/pools) | solana | `pump-fun` | | [Raydium Launchpad](https://www.geckoterminal.com/solana/raydium-launchlab/pools) (LetsBonkFun) | solana | `raydium-launchlab` | | [Boop.fun](https://www.geckoterminal.com/solana/boop-fun/pools) | solana | `boop-fun` | | [Virtuals (Base)](https://www.geckoterminal.com/base/virtuals-base/pools) | base | `virtuals-base` | Improved endpoints: * [Token Data by Token Address](/reference/token-data-contract-address) * [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) * [Specific Pool Data by Pool Address](/reference/pool-address) * [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) **Tip:** Use [Megafilter for Pools](/reference/pools-megafilter) with `sort=pool_created_at_desc` to retrieve the latest launchpad pools. ```bash wrap theme={null} https://pro-api.coingecko.com/api/v3/onchain/pools/megafilter?page=1&networks=solana&dexes=pump-fun&sort=pool_created_at_desc&x_cg_pro_api_key=YOUR_KEY ``` ### Granular OHLCV Data Onchain OHLCV endpoints now support sub-minute intervals down to 1-second granularity: | Timeframe | Aggregates | | :-------- | :------------------ | | day | 1 | | hour | 1, 4, 12 | | minute | 1, 5, 15 | | second | **1, 15, 30** (new) | Improved endpoints: * [Pool OHLCV Chart by Pool Address](/reference/pool-ohlcv-contract-address) * [Token OHLCV Chart by Token Address](/reference/token-ohlcv-token-address) > Paid plan subscribers (Analyst & above) only. ```bash wrap theme={null} https://pro-api.coingecko.com/api/v3/onchain/networks/eth/pools/0x06da0fd433c1a5d7a4faa01111c044910a184553/ohlcv/second?aggregate=1&limit=100&x_cg_pro_api_key=YOUR_KEY ``` ### Honeypot Detection [Token Info by Token Address](/reference/token-info-contract-address) and [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) now include `is_honeypot` (values: `true`, `false`, or `unknown`): ```json Example Payload theme={null} { "mint_authority": null, "freeze_authority": null, "is_honeypot": true } ``` ### Megafilter: Include Unknown Honeypot Tokens [Megafilter for Pools](/reference/pools-megafilter) now supports `include_unknown_honeypot_tokens=true` to include tokens with unknown honeypot status. Only takes effect when `checks=no_honeypot` is also specified. ```bash wrap theme={null} https://pro-api.coingecko.com/api/v3/onchain/pools/megafilter?page=1&sort=h6_trending&checks=no_honeypot&include_unknown_honeypot_tokens=true&x_cg_pro_api_key=YOUR_KEY ``` ### Pool Tokens Info: Expanded Pool Data [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) now supports `include=pool` to retrieve pool context: * Base and quote token addresses * Sentiment vote percentages (positive/negative) * Community suspicious reports count ```json Example Payload expandable theme={null} "included": [ { "id": "eth_0x06da0fd433c1a5d7a4faa01111c044910a184553", "type": "pool", "attributes": { "base_token_address": "0xdac17f958d2ee523a2206206994597c13d831ec7", "quote_token_address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2", "sentiment_vote_positive_percentage": 100, "sentiment_vote_negative_percentage": 0, "community_sus_report": 0 } } ] ``` ## SOL Currency Is Now Supported for CoinGecko Endpoints πŸ—“οΈ **June 19, 2025** Real-time and historical price and market data can now be returned in **SOL** (Solana) currency across the following endpoints: * [Coin Price by IDs](/reference/simple-price) * [Coin Price by Token Addresses](/reference/simple-token-price) * [Supported Currencies List](/reference/simple-supported-currencies) * [Top Gainers & Losers](/reference/coins-top-gainers-losers) * [Coins List with Market Data](/reference/coins-markets) * [Coin Data by ID](/reference/coins-id) * [Coin Historical Data by ID](/reference/coins-id-history) * [Coin Historical Chart Data by ID](/reference/coins-id-market-chart) * [Coin Historical Chart Data within Time Range by ID](/reference/coins-id-market-chart-range) * [Coin OHLC Chart by ID](/reference/coins-id-ohlc) * [Coin OHLC Chart within Time Range by ID](/reference/coins-id-ohlc-range) * [Coin Data by Token Address](/reference/coins-contract-address) * [Coin Historical Chart Data by Token Address](/reference/contract-address-market-chart) * [Coin Historical Chart Data within Time Range by Token Address](/reference/contract-address-market-chart-range) * [Trending Search List](/reference/trending-search) * [Crypto Global Market Data](/reference/crypto-global) > For dates prior to May 2025, SOL historical data is limited to hourly and daily granularity. **Example** β€” price of Bitcoin in SOL: ```json theme={null} { "bitcoin": { "sol": 720.21 } } ``` **Example** β€” historical daily data of Trump in SOL: ```json expandable theme={null} { "prices": [ [1750118400000, 0.0640701365814472], [1750204800000, 0.0644263929356261], [1750291200000, 0.0639713357587322] ], "market_caps": [ [1750118400000, 12843589.584485611], [1750204800000, 12882547.839086628], [1750291200000, 12793790.726102708] ], "total_volumes": [ [1750118400000, 2425793.780846796], [1750204800000, 2055697.9106767387], [1750291200000, 1871087.4334618242] ] } ``` *** ## New Endpoints & Improvements: Historical Token Holders Chart, OHLCV by Token Address, Multi-pool Token Data Support πŸ—“οΈ **June 9, 2025** ### New Endpoint: Historical Token Holders Chart [Historical Token Holders Chart by Token Address](/reference/token-holders-chart-token-address) β€” get the historical token holders chart for a token on a network. **Supported chains:** Solana, EVM (Ethereum, Polygon, BNB, Arbitrum, Optimism, Base), Sui, TON, Ronin > Paid plan subscribers (Analyst & above) only. ### New Endpoint: Token OHLCV by Token Address [Token OHLCV Chart by Token Address](/reference/token-ohlcv-token-address) β€” get OHLCV data for a token based on its most liquid pool. Use [Top Pools by Token Address](/reference/top-pools-contract-address) to check which pool is used. > Paid plan subscribers (Analyst & above) only. ### Multi-pool Token Data Support For pools with 3+ tokens, extra quote tokens are now listed under `relationships.quote_tokens`. If `include=quote_token` is flagged, the extra tokens also appear under `included`. ```json Example Payload expandable highlight={14-25} theme={null} "relationships": { "base_token": { "data": { "id": "eth_0x40d16fc0246ad3160ccc09b8d0d3a2cd28ae6c2f", "type": "token" } }, "quote_token": { "data": { "id": "eth_0x8353157092ed8be69a9df8f95af097bbf33cb2af", "type": "token" } }, "quote_tokens": { "data": [ { "id": "eth_0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", "type": "token" }, { "id": "eth_0xdac17f958d2ee523a2206206994597c13d831ec7", "type": "token" } ] } } ``` Applies to all onchain pool endpoints with `relationships.quote_token`, including: * [Top Pools by Token Address](/reference/top-pools-contract-address) * [Search Pools](/reference/search-pools) * [Megafilter for Pools](/reference/pools-megafilter) * [Trending Pools List](/reference/trending-pools-list) * [Specific Pool Data by Pool Address](/reference/pool-address) * [Top Pools by Network](/reference/top-pools-network) * [New Pools List](/reference/latest-pools-list) ## Upcoming Change Notice: Removal of normalized\_volume\_btc Data πŸ—“οΈ **May 30, 2025** **Effective June 16, 2025** β€” the `trade_volume_24h_btc_normalized` field has been removed from the following endpoints, due to changes in a third-party data source: * [Exchange Data by ID](/reference/exchanges-id) * [Exchanges List with Data](/reference/exchanges) ```json theme={null} { "trade_volume_24h_btc_normalized": 47765.5886637453 } ``` If your application relies on `trade_volume_24h_btc_normalized`, update your code to handle its absence. *** ## New Endpoint & Improvements: On-Chain Trades, Net Buy Volume, and More πŸ—“οΈ **May 29, 2025** ### New Endpoint: Onchain Trades by Token Address [Past 24 Hour Trades by Token Address](/reference/token-trades-contract-address) retrieves the last 300 trades **across different pools** for a token, unlike [Past 24 Hour Trades by Pool Address](/reference/pool-trades-contract-address) which is limited to a single pool. > Paid plan subscribers (Analyst & above) only. ### Net Buy Volume Data [Specific Pool Data by Pool Address](/reference/pool-address) and [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) now support `include_volume_breakdown=true`, returning: * `net_buy_volume_usd` * `buy_volume_usd` * `sell_volume_usd` ```json Example Payload expandable highlight={6-21} theme={null} { "data": { "id": "eth_0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640", "type": "pool", "attributes": { "net_buy_volume_usd": { "m5": "-40796.577553965", "m15": "-69765.771189161", "m30": "-88014.095440243", "h1": "0.000000000000", "h6": "1884879.921855301", "h24": "17555422.243003801" }, "buy_volume_usd": { "m5": "30597.433165473", "h24": "52666266.729011402" }, "sell_volume_usd": { "m5": "71394.010719438", "h24": "35110844.486007601" } } } } ``` ### OHLCV: Empty Interval Padding [Pool OHLCV Chart by Pool Address](/reference/pool-ohlcv-contract-address) now supports `include_empty_intervals=true`. Intervals with no recorded swaps are padded β€” OHLC values follow the previous close, and volume is set to zero. ```json Example Payload expandable theme={null} { "data": { "id": "81da0682-1c4f-445a-9bed-9b5454004df5", "type": "ohlcv_request_response", "attributes": { "ohlcv_list": [ [ 1744712700, 0.000212149802253853, 0.000212173305907688, 0.000212149802253853, 0.000212173305907688, 46.48164903882 ], [ 1744712400, 0.000212149802253853, πŸ‘ˆ O β€” Follow previous Close value 0.000212149802253853, πŸ‘ˆ H β€” Follow previous Close value 0.000212149802253853, πŸ‘ˆ L β€” Follow previous Close value 0.000212149802253853, πŸ‘ˆ C β€” Follow previous Close value 0.0 πŸ‘ˆ V β€” Set to zero ], [ 1744712100, 0.000210532522666822, 0.000212149802253853, 0.000210532522666822, 0.000212149802253853, πŸ‘ˆ Previous Close value 46.4765 ] ] } } } ``` ### Token Info: Large Image Sizes [Token Info by Token Address](/reference/token-info-contract-address) and [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) now include an `image` object with `thumb`, `small`, and `large` URLs: ```json Example Payload highlight={5} theme={null} "image_url": "https://assets.coingecko.com/coins/images/325/small/Tether.png?1696501661", "image": { "thumb": "https://assets.coingecko.com/coins/images/325/thumb/Tether.png?1696501661", "small": "https://assets.coingecko.com/coins/images/325/small/Tether.png?1696501661", "large": "https://assets.coingecko.com/coins/images/325/large/Tether.png?1696501661" }, ``` ### Token Data: Normalized Total Supply [Token Data by Token Address](/reference/token-data-contract-address) and [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) now include `normalized_total_supply`: ```json Example Payload highlight={3} theme={null} "decimals": 6, "total_supply": "49999156520373530.0", "normalized_total_supply": "49999156520.37353", ``` ### Pool Data: Pool Name and Fee [Specific Pool Data by Pool Address](/reference/pool-address) and [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) now include `pool_name` and `pool_fee_percentage`: ```json Example Payload highlight={2-3} theme={null} "name": "WETH / USDC 0.05%", "pool_name": "WETH / USDC", "pool_fee_percentage": "0.05", ``` ### DEX Pair Symbols Flag `dex_pair_format=symbol` to return DEX pair symbols instead of contract addresses on: * [Coin Data by ID](/reference/coins-id) * [Coin Tickers by ID](/reference/coins-id-tickers) * [Exchange Tickers by ID](/reference/exchanges-id-tickers) * [Exchange Data by ID](/reference/exchanges-id) **Before:** ```json theme={null} { "base": "0X8FC8F8269EBCA376D046CE292DC7EAC40C8D358A", "target": "0XA0B86991C6218B36C1D19D4A2E9EB0CE3606EB48" } ``` **After** (`dex_pair_format=symbol`): ```json theme={null} { "base": "DFI", "target": "USDC" } ``` ## New Endpoint & Improvements: On-Chain Trending Data, Enhanced Trending Search, and Improved Token Lookup πŸ—“οΈ **April 25, 2025** ### New Endpoint: Onchain Trending Search Data [Trending Search Pools](/reference/trending-search-pools) returns onchain trending pools and tokens as seen on GeckoTerminal.com. Returns top 4 pools by default β€” set `pools` to retrieve up to 10. **Tip:** Flag `include=base_token` to also retrieve trending token data. > Paid plan subscribers (Analyst & above) only. ### Trending Search List: `show_max` Parameter [Trending Search List](/reference/trending-search) now supports `show_max` to retrieve more trending results for paid plan subscribers: | Trending Data | Demo | Analyst & Above | | :-------------- | :--: | :-------------: | | Coins | 15 | 30 | | NFTs | 7 | 10 | | Coin Categories | 6 | 10 | ### Token Lookup by Symbol and Name [Coin Price by IDs](/reference/simple-price) and [Coins List with Market Data](/reference/coins-markets) now support token lookup by `symbol` and `name`, in addition to API ID. | API ID | Symbol | Name | | :------- | :----- | :------ | | bitcoin | btc | Bitcoin | | tether | usdt | Tether | | usd-coin | usdc | USDC | **Lookup priority:** `id` (highest) > `name` > `symbol` (lowest). **Filtering by symbol with `include_tokens`:** * `include_tokens=top` β€” returns only the top market cap token for the symbol * `include_tokens=all` β€” returns all tokens sharing the symbol ### /coins/markets: Pagination Response Headers [Coins List with Market Data](/reference/coins-markets) now includes `total` and `per-page` values in the response headers, enabling accurate pagination across all active coins. ```text Response Header (Example) theme={null} per-page: 250 total: 16989 ``` *** ## Upcoming Change Notice: Removal of twitter\_followers Data πŸ—“οΈ **April 25, 2025** **Effective May 15, 2025** β€” the `twitter_followers` field within `community_data` has been removed from the following endpoints, due to changes in the X (formerly Twitter) API: * [Coin Data by ID](/reference/coins-id) * [Coin Data by Token Address](/reference/coins-contract-address) * [Coin Historical Data by ID](/reference/coins-id-history) ```json theme={null} "community_data": { "twitter_followers": 7694251 } ``` If your application relies on `twitter_followers`, update your code to handle its absence. ## New Endpoint & Multiple Improvements: On-Chain Top Token Holder Address, Security Data, Historical Supply. πŸ—“οΈ **March 28, 2025** ### New Endpoint: Top Token Holder Address Data Access the top 50 token holder addresses, as seen on GeckoTerminal.com. Returns top 10 by default β€” set `holders` to retrieve up to 50. [Top Token Holders by Token Address β†’](/reference/top-token-holders-token-address) **Supported networks:** Ethereum, Polygon, BNB, Arbitrum, Optimism, Base, Solana, Sui, TON, Ronin > Paid plan subscribers (Analyst & above) only. Holders data is in **Beta** β€” data quality, coverage, and update frequency are being improved. Solana tokens support a maximum of 40 holders. **Tip:** Use [Token Info by Token Address](/reference/token-info-contract-address) or [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) for **holders count** and **top holders distribution percentage**. ### Historical Supply: Support for Inactive Coins Historical total and circulating supply data is now available for inactive coins. Use [Coin List (ID Map)](/reference/coins-list) with `status=inactive` to find inactive coin IDs. > Enterprise plan only. * [Circulating Supply Chart by ID](/reference/coins-id-circulating-supply-chart) * [Circulating Supply Chart within Time Range by ID](/reference/coins-id-circulating-supply-chart-range) * [Total Supply Chart by ID](/reference/coins-id-total-supply-chart) * [Total Supply Chart within Time Range by ID](/reference/coins-id-total-supply-chart-range) ### Onchain Pool Data: Locked Liquidity New `locked_liquidity_percentage` field available on: * [Specific Pool Data by Pool Address](/reference/pool-address) * [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) ```json Example Payload expandable highlight={17} theme={null} { "data": [ { "id": "eth_0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640", "type": "pool", "attributes": { "base_token_price_usd": "3653.12491645176", "base_token_price_native_currency": "1.0", ... "volume_usd": { "m5": "868581.7348314", "h1": "16798158.0138526", "h6": "164054610.850188", "h24": "536545444.904535" }, "reserve_in_usd": "163988541.3812", "locked_liquidity_percentage": "99.82" }, ``` ### Onchain Token Info: GT Score, Mint Authority, Freeze Authority Token Info endpoints now include security-related fields: * **GT Score Details** β€” breakdown by pool, transaction, creation, info, and holders. [Learn more](https://support.coingecko.com/hc/en-us/articles/38381394237593-What-is-GT-Score-How-is-GT-Score-calculated). * **Mint Authority** and **Freeze Authority** Improved endpoints: * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) ```json Example Payload theme={null} "gt_score": 92.6605504587156, "gt_score_details": { "pool": 0, "transaction": 32.2, "creation": 0, "info": 0, "holders": 0 }, "mint_authority": "no", "freeze_authority": "no" ``` ### Onchain Simple Token Price: Market Cap to FDV Fallback [Token Price by Token Addresses](/reference/onchain-simple-price) now supports `mcap_fdv_fallback=true` β€” when a token's market cap is unverified, the `market_cap_usd` field returns the FDV value instead (matching GeckoTerminal.com behavior). * Unverified tokens return `null` for market cap by default, even if GeckoTerminal shows a value (which may equal FDV) * Verified market cap is sourced from CoinGecko and may exceed FDV when it includes tokens on other chains *** ## Update Frequency Improvements for selected Pro-API endpoints (March 2025) πŸ—“οΈ **March 14, 2025** > Applicable to [paid plan](https://www.coingecko.com/en/api/pricing) subscribers (Analyst & above) only. Edge cache durations for the following onchain endpoints have been reduced from 60s to **30s**: | Effective From | Endpoints | | :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | March 25, 2025 | [Trending Pools List](/reference/trending-pools-list)
[Trending Pools by Network](/reference/trending-pools-network)
[Top Pools by Network](/reference/top-pools-network)
[Top Pools by DEX](/reference/top-pools-dex) | | March 26, 2025 | [New Pools by Network](/reference/latest-pools-network)
[New Pools List](/reference/latest-pools-list)
[Megafilter for Pools](/reference/pools-megafilter)
[Search Pools](/reference/search-pools) | | March 27, 2025 | [Top Pools by Token Address](/reference/top-pools-contract-address)
[Most Recently Updated Tokens List](/reference/tokens-info-recent-updated)
[Pools by Category ID](/reference/pools-category) | Cached responses incur no extra credits. Requests that bypass the cache and hit the origin server may use additional credits β€” adjust your polling interval accordingly. *** ## Multiple Improvements: Holders data, Pool Stats, Simple Token Price πŸ—“οΈ **March 14, 2025** ### Onchain Token Info: Holders Data (Beta) New holder fields available: * `holders.count` β€” total holder count * `holders.distribution_percentage` β€” top 10, 11–20, 21–40, and rest breakdown Improved endpoints: * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) ```json Example Payload theme={null} "holders": { "count": 1432761, "distribution_percentage": { "top_10": "1.3019", "11_20": "0.1024", "21_40": "0.095", "rest": "98.5007" }, "last_updated": "2025-03-06T01:21:18Z" ``` ### Onchain Pool Data: New Intervals New time intervals for `price_change_percentage`, `volume_usd`, and `transactions`: * `price_change_percentage`: added `m15`, `m30` * `volume_usd`: added `m15`, `m30` * `transactions`: added `h6` Improved endpoints: * [Specific Pool Data by Pool Address](/reference/pool-address) * [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) ```json Example Payload expandable highlight={3-4,34-39,49-50} theme={null} "price_change_percentage": { "m5": "0.06", "m15": "0.06", "m30": "0.89", "h1": "-4.31", "h6": "-1.02", "h24": "3.32" }, "transactions": { "m5": { "buys": 0, "sells": 2, "buyers": 0, "sellers": 2 }, "m15": { "buys": 0, "sells": 2, "buyers": 0, "sellers": 2 }, "m30": { "buys": 0, "sells": 3, "buyers": 0, "sellers": 3 }, "h1": { "buys": 1, "sells": 23, "buyers": 1, "sellers": 7 }, "h6": { "buys": 60, "sells": 38, "buyers": 23, "sellers": 18 }, "h24": { "buys": 206, "sells": 138, "buyers": 96, "sellers": 77 } }, "volume_usd": { "m5": "130.5119858698", "m15": "130.5119858698", "m30": "177.109036156", "h1": "4942.2463835639", "h6": "28362.2127269542", "h24": "112426.585893123" } ``` ### Onchain Simple Token Price: Liquidity & Price Change [Token Price by Token Addresses](/reference/onchain-simple-price) now supports two new optional parameters: * `include_24hr_price_change` β€” 24h price change percentage * `include_total_reserve_in_usd` β€” total liquidity attributable to a token across all pools ```json Example Payload expandable highlight={18-25} theme={null} { "data": { "id": "e58258f7-8368-4968-bbe1-b5343540cd71", "type": "simple_token_price", "attributes": { "token_prices": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "1.00276143983565", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "3175.22870146126" }, "market_cap_usd": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "25000000000", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "500000000000" }, "h24_volume_usd": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "50000000", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "10000000000" }, "h24_price_change_percentage": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "-0.15", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "1.15" }, "total_reserve_in_usd": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "417994486.4342195821530162288", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "417994486.4342195821530162288" } } } } ``` ## New Megafilter Endpoint, 200+ Chains Supported: Hyperliquid, Abstract, Berachain & MOAR! πŸ—“οΈ **February 27, 2025** The CoinGecko API now supports onchain data across **200+ blockchain networks**, including Hyperliquid, HyperEVM, Abstract, Berachain, Story, Monad, Unichain, and Soneium. A new endpoint for slicing and dicing onchain pool data with full flexibility. [Megafilter for Pools β†’](/reference/pools-megafilter) * Filter across 200+ networks, 1,400+ DEXes, 6M+ pools, and 5M+ tokens * Advanced filters by liquidity, FDV, volume, transactions, buy/sell trends, and time range * Custom sorting β€” trending pools (5m), newest pools, liquidity growth, and more * Fraud detection β€” exclude honeypots, check GT Score, verify CG listings, track social metrics **Examples:** * Track fresh pools on Uniswap V4 & Aerodrome with liquidity above \$1,000 * Discover trending DEX pools across Solana, Base, and other chains with a high GT Score * Filter out risky pools with built-in honeypot protection and fraud checks > Paid plan subscribers (Analyst & above) only. *** ## Update Frequency Improvements for selected Pro-API endpoints πŸ—“οΈ **February 14, 2025** > Applicable to [paid plan](https://www.coingecko.com/en/api/pricing) subscribers (Analyst & above) only. Edge cache durations for the following onchain endpoints have been reduced from 60s to **30s**: | Effective From | Endpoints | | :------------------- | :------------------------------------------------------------------------------------------------------------------------------------------ | | February 24, 2025 | [/networks/../tokens/](/reference/token-data-contract-address)
[/networks/../tokens/multi/](/reference/tokens-data-contract-addresses) | | February 25–26, 2025 | [/networks/../pools/../ohlcv](/reference/pool-ohlcv-contract-address) | Cached responses incur no extra credits. Requests that bypass the cache and hit the origin server may use additional credits β€” adjust your polling interval accordingly. *** ## Enhanced Onchain Metadata, Increased Max Address Limit for Multi Endpoints, Improved Exchange Tickers Sorting πŸ—“οΈ **February 9, 2025** ### Onchain Metadata: Improved Coverage Metadata coverage (images, websites, description, socials) is now improved for tokens on Solana, TON, Base, and Sui. Tokens without image data now return `null` for `image_url` instead of `missing.png`. **Endpoints with improved image data:** * [Trending Pools List](/reference/trending-pools-list) * [Trending Pools by Network](/reference/trending-pools-network) * [Specific Pool Data by Pool Address](/reference/pool-address) * [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) * [Top Pools by Network](/reference/top-pools-network) * [Top Pools by DEX](/reference/top-pools-dex) * [New Pools by Network](/reference/latest-pools-network) * [New Pools List](/reference/latest-pools-list) * [Search Pools](/reference/search-pools) * [Top Pools by Token Address](/reference/top-pools-contract-address) * [Token Data by Token Address](/reference/token-data-contract-address) * [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) * [Most Recently Updated Tokens List](/reference/tokens-info-recent-updated) **Endpoints with improved full metadata** (images, websites, description, socials): * [Token Info by Token Address](/reference/token-info-contract-address) * [Pool Tokens Info by Pool Address](/reference/pool-token-info-contract-address) * [Most Recently Updated Tokens List](/reference/tokens-info-recent-updated) > Onchain metadata may be sourced on-chain and is not vetted by CoinGecko. For reviewed metadata, use [Coin Data by ID](/reference/coins-id) or [Coin Data by Token Address](/reference/coins-contract-address). ### Max Address Limit Increased for /multi Endpoints Onchain `/multi` endpoints now support up to **50** token or pool addresses per request (previously 30): * [Tokens Data by Token Addresses](/reference/tokens-data-contract-addresses) * [Multiple Pools Data by Pool Addresses](/reference/pools-addresses) > Paid plan subscribers (Analyst & above) only. ### Exchange Tickers: New `base_target` Sort Order [Exchange Tickers by ID](/reference/exchanges-id-tickers) now supports `order=base_target`, which sorts tickers by base symbol then target symbol in lexicographical order. This ensures **stable pagination** β€” the default `trust_score_desc` sort can cause duplicates or missing tickers when ranks shift between paginated requests. ```bash theme={null} pro-api.coingecko.com/api/v3/exchanges/binance/tickers?order=base_target ``` ## Multiple Improvements: Onchain Pools Page Limit, Trades Token Filter πŸ—“οΈ **January 27, 2025** ### Onchain Pools: Pagination Beyond 10 Pages Paid plan subscribers (Analyst & above) can now access more than 10 pages of pools data on the following endpoints: * [Search Pools](/reference/search-pools) * [Top Pools by Token Address](/reference/top-pools-contract-address) * [Trending Pools List](/reference/trending-pools-list) * [Trending Pools by Network](/reference/trending-pools-network) * [New Pools by Network](/reference/latest-pools-network) * [New Pools List](/reference/latest-pools-list) * [Top Pools by Network](/reference/top-pools-network) * [Top Pools by DEX](/reference/top-pools-dex) ### Onchain Trades: Token Filter [Past 24 Hour Trades by Pool Address](/reference/pool-trades-contract-address) now supports a `token` parameter to filter trades by base or quote token: * `?token=base` β€” base token trades only * `?token=quote` β€” quote token trades only * `?token={token_address}` β€” trades for a specific token address *** ## Multiple Improvements: Onchain Token Price, NFT Market Cap πŸ—“οΈ **January 24, 2025** ### Onchain Simple Token Price: Market Cap and 24h Volume [Token Price by Token Addresses](/reference/onchain-simple-price) now supports `include_market_cap=true` and `include_24hr_vol=true`: ```json Example Payload expandable theme={null} { "data": { "id": "e1979db1-5c3e-4ba8-b103-cb0258af4a7c", "type": "simple_token_price", "attributes": { "token_prices": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "0.999365729816931", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "3399.24368371279" }, "market_cap_usd": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "51963214441.24363", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "10005535878.50094" }, "h24_volume_usd": { "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48": "2095689865.85327", "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2": "2544539948.02599" } } } } ``` ### NFT Data: Market Cap Rank `market_cap_rank` is now available for NFT collections via: * [NFTs Collection Data by ID](/reference/nfts-id) * [NFTs Collection Data by Contract Address](/reference/nfts-contract-address) ```json Example Payload theme={null} "market_cap_rank": 75, ``` *** ## Removal of Unsupported Categories πŸ—“οΈ **January 23, 2025** The following categories have been removed from CoinGecko and the API, effective **February 12, 2025**: | Category Name | Category ID | | :--------------------- | :-------------------- | | US Election 2020 | `us-election-2020` | | Governance | `governance` | | Cryptocurrency | `cryptocurrency` | | Technology and Science | `technology-science` | | Presale Meme | `presale-meme-coins` | | Business Platform | `business-platform` | | Number | `number` | | Structured Product | `structured-products` | | Investment | `investment` | | Niftex Shards | `niftex-shards` | | Ethereum POW IOU | `ethereum-pow-iou` | | Mirrored Assets | `mirrored-assets` | | Remittance | `remittance` | | Protocol | `protocol` | | Unicly Ecosystem | `utokens` | | Finance and Banking | `finance-banking` | | Eth 2.0 Staking | `eth-2-0-staking` | These categories were either empty (no associated coins) or outdated. Requests to [/coins/markets](/reference/coins-markets) specifying any of these categories will return an error. *** ## Extended Historical Data for Onchain OHLCV Endpoint πŸ—“οΈ **January 15, 2025** The [Pool OHLCV Chart by Pool Address](/reference/pool-ohlcv-contract-address) endpoint now supports historical data going back to **September 2021**, depending on when the pool was first tracked on GeckoTerminal. * **Before:** Limited to the past 6 months from today * **After:** Data available from September 2021 to present * Each request is still limited to a **6-month date range** β€” use the `before_timestamp` parameter to page through older data > Access to data beyond the past 6 months requires a [paid plan](https://www.coingecko.com/en/api/pricing) (Analyst & above). No changes required for existing integrations. *** ## Update to Total Supply of POW Coins πŸ—“οΈ **January 15, 2025** Total Supply for PoW (Proof-of-Work) coins now reflects the actual number of mined coins, rather than the maximum supply. This also applies to historical Total Supply data. * **Before:** Maximum possible supply (e.g., Bitcoin: 21,000,000) * **After:** Actual mined coins (e.g., Bitcoin: \~19,500,000 as of January 2025) **Affected endpoints** with `total_supply` data: * [Coin Data by ID](/reference/coins-id) * [Coins List with Market Data](/reference/coins-markets) * [Total Supply Chart by ID](/reference/coins-id-total-supply-chart) * [Total Supply Chart within Time Range by ID](/reference/coins-id-total-supply-chart-range) **Timeline:** * **Bitcoin:** Updated January 14, 2025 * **Other PoW coins:** Updated January 22, 2025 β€” including Bitcoin Cash, Litecoin, Ethereum Classic, Bitcoin SV, Zcash, eCash, Dash, Kadena, Decred, Flux, DigiByte, Ravencoin, Groestlcoin, Firo, Vertcoin, Handshake, and more *** ## Improved Update Frequency for selected Pro-API endpoints πŸ—“οΈ **January 13, 2025** > Applicable to [paid plan](https://www.coingecko.com/en/api/pricing) subscribers (Analyst & above) only. Edge cache durations for the following endpoints have been reduced to 20–30s: | Endpoint | Previous | New | | :---------------------------------------------------------------------- | :------: | :-: | | [/simple/price](/reference/simple-price) | 30s | 20s | | [/simple/token\_price](/reference/simple-token-price) | 30s | 20s | | [/simple/networks/../token\_price](/reference/onchain-simple-price) | 60s | 30s | | [/networks/../pools/../trades](/reference/pool-trades-contract-address) | 60s | 30s | | [/networks/../pools/..](/reference/pool-address) | 60s | 30s | | [/networks/../pools/multi/..](/reference/pools-addresses) | 60s | 30s | Cached responses incur no extra credits. Requests that bypass the cache and hit the origin server may use additional credits β€” adjust your polling interval accordingly. *** ## Improved 5-minutely data for Historical Chart Data endpoints πŸ—“οΈ **January 9, 2025** The last 48 hours of data is no longer excluded from the following historical chart endpoints: * [Coin Historical Chart Data by ID](/reference/coins-id-market-chart) * [Coin Historical Chart Data within Time Range by ID](/reference/coins-id-market-chart-range) * [Coin Historical Chart Data by Token Address](/reference/contract-address-market-chart) * [Coin Historical Chart Data within Time Range by Token Address](/reference/contract-address-market-chart-range) **Note:** The `interval=5m` and `interval=hourly` params are exclusive to Enterprise plan subscribers, bypassing auto-granularity: * `interval=5m` β€” 5-minutely data, up to any 10-day range per request. Available from 9 February 2018 onwards. * `interval=hourly` β€” hourly data, up to any 100-day range per request. Available from 30 January 2018 onwards. For non-Enterprise subscribers, leave `interval` empty for auto-granularity: * 1 day from current time = 5-minutely data * 1 day from any time (except current time) = hourly data * 2–90 days from any time = hourly data * Above 90 days from any time = daily data (00:00 UTC)