Enhanced Onchain Metadata, Increased Max Address Limit for Multi Endpoints, Improved Exchange Tickers Sorting

Onchain Metadata: Improved Coverage

Previously: Payload may return 'missing.png' for image_url for tokens that do not have image data.

Now: Coverage of metadata (images, websites, description, socials) is now improved for tokens on Solana, Ton, Base, and Sui networks. For tokens that do not contain image data, 'null' value will be returned for image_url.

Improved endpoints with image data:

1. Trending Pools List
2. Trending Pools by Network
3. Specific Pool Data by Pool Address
4. Multiple Pools Data by Pool Addresses
5. Top Pools by Network
6. Top Pools by Dex
7. New Pools by Network
8. New Pools List
9. Search Pools
10. Top Pools by Token Address
11. Token Data by Token Address
12. Tokens Data by Token Addresses
13. Token Info by Token Address
14. Pool Tokens Info by Pool Address
15. Most Recently Updated Tokens List

Improved endpoints with metadata (images, websites, description, socials):

1. Token Info by Token Address
2. Pool Tokens Info by Pool Address
3. Most Recently Updated Tokens List

Note: Metadata may be sourced on-chain and is not vetted by the CoinGecko team. If you wish to get metadata reviewed by CoinGecko team, you may use the following endpoints:

• Coin Data by ID
• Coin Data by Token Address

Improved Max Address Limit for onchain /multi endpoints

Previously: Onchain /multi endpoints support up to 30 token or pool contract addresses per request.

Now: Onchain /multi endpoints support up to 50 token or pool contract addresses per request.

Improved endpoints:

1. Tokens Data by Token Addresses
2. Multiple Pools Data by Pool Addresses

Note: this new max address input limit is exclusive for paid plan subscribers (Analyst plan & above) only.

Improved Data Consistency for Exchange Tickers by ID

For Exchange Tickers by ID endpoint, the order is sorted by trust_score_desc by default.

• Sometimes duplicate or missing data may occur due to paginated cached response, especially when a ticker's rank changes between 2 paginated requests, e.g. it might shift from Page 2 to Page 1, vice versa.
• We've added a new order option: base_target, which will sort the tickers by base symbol, then target symbol, in lexicographical order, i.e. 0->9, then a->Z.

Example: flagging ?order=base_target

pro-api.coingecko.com/api/v3/exchanges/binance/tickers?order=base_target

This sorting method ensures stable pagination, reducing issues where cached responses may cause duplicate or missing tickers across pages.