Changed
GET /networks/{network}/multi/prices: requests are now limited to a maximum of 10tokensper call.- Parameter encoding updated to a single comma-separated
tokenslist (explode=false).
Error handling
- Requests with more than 10 tokens return
400 Bad Request. - Requests with zero tokens still return
400 Bad Request(unchanged).
Docs
- Updated API reference, tutorial, and MCP notes to reflect the cap, edge-case behavior, and comma-separated encoding.
Added
- New endpoint:
GET /networks/{network}/multi/pricesfor batch token price retrieval on a network.- Request: repeatable
tokensquery parameter (e.g.,?tokens=0x...&tokens=0x...). - Response: array of
{ id, chain, price_usd }objects for tokens with available prices; unknown/unpriced tokens are omitted.
- Request: repeatable
Changed
AssetPriceschema added and documented in OpenAPI.- Internals: performance optimization to fetch token summaries conditionally.
Compatibility
- Certain price-related fields now use
omitemptysemantics in responses. If you previously relied on nulls for absent values, note these keys may now be omitted when data is unavailable.
Docs
- New API page: Get batched token prices on a network.
- Updated tutorials and references to include batch pricing guidance.
Enhanced
- Transaction Schema:
- Added
token_0_symbolandtoken_1_symbolfields to transaction objects for explicit token symbol tracking. - Added
price_0,price_1,price_0_usd, andprice_1_usdfields to transaction objects for detailed price reporting. - Added
created_atfield to transaction objects for precise transaction timestamping.
- Added
Migration/Compatibility
- No breaking changes to existing endpoints, but clients parsing transaction objects should update their models to support the new fields for full compatibility.
FAQs
How often is the API updated?
How often is the API updated?
We ship changes continuously. Breaking changes are called out explicitly with migration guidance.
Where do I find migration paths?
Where do I find migration paths?
Each breaking change section includes steps and replacement endpoints when applicable.
How can I stay notified?
How can I stay notified?
Watch this changelog and our Discord announcements; major updates are posted there.
Deprecated
- BREAKING: The
/poolsendpoint has been permanently deprecated and now returns410 Gone - Users should migrate to
/networks/{network}/poolsto get top pools for each specific network
Changed
- Enhanced deprecation messaging with clear migration paths for affected endpoints
Migration guide
Instead of using the deprecated global pools endpoint:Added
- Introduced the optional
reorderquery parameter to the/networks/{network}/tokens/{token_address}/poolsendpoint. This allows clients to reorder pool data so the specified token becomes the primary token for all metrics and calculations.
Added
- Added operation IDs to all endpoints for better client code generation
- Added fully diluted valuation (
fdv) field to token responses - Added detailed license information and contact details in API specification
- Added
buy_usdandsell_usdfields to provide monetary values for trades - Added
last_price_usd_changefield to all time intervals (24h, 6h, 1h, 30m, 15m, 5m, 1m) - Added organized API tags with descriptions for better navigation
Changed
- Updated OpenAPI specification from 3.0.3 to 3.1.0 for improved documentation
- Changed OHLCV endpoint response format from wrapped object to direct array of records (Breaking Change)
- Renamed
buy/sellfields tobuys/sellsfor consistency (Breaking Change) - Changed network response format from object to array for cleaner consumption
- Updated network schema with improved field naming (
display_nameinstead of justname) - Standardized ID field in Network schema to use string identifiers instead of numeric IDs
- Enhanced token schema with additional fields: chain, total_supply, added_at, last_updated
- Improved parameter documentation with examples and clearer descriptions
Fixed
- Improved consistency in representing null values in responses
- Updated example responses to more accurately reflect actual API behavior
- Fixed formatting inconsistencies in API documentation
Improved
- Enhanced OHLCV schema with time_open and time_close fields to clearly define candlestick periods
- Improved validation for time intervals and limits in OHLCV endpoint
- Added explicit error response documentation for the /stats endpoint
- Enhanced descriptions for all endpoints and parameters
Added
- Support for buy/sell volume metrics across all time intervals
- Added transaction counts to pool details
- Added initial support for price tracking
Changed
- Improved error messaging with more specific error codes
- Enhanced documentation with more descriptive examples
Fixed
- Corrected timestamp format inconsistencies across endpoints
- Fixed incorrect price calculations in some edge cases