Changelog

​

Changed

• GET /networks/{network}/pools/{pool_address}/transactions answers only Dev, Pro and Enterprise keys, on https://api-pro.dexpaprika.com. Keyless requests and free keys get 403 with "error":"plan_required" and "required_tier":"dev".
• /sse/transactions (GET and POST) needs the same plans, on https://streaming-pro.dexpaprika.com. Keyless callers and free keys get the same 403 before a stream opens.
• /sse/ohlcv refusals now carry the same body, with "error":"plan_required". The gate itself is unchanged: Dev, Pro and Enterprise keys pass it, as before.
• REST error bodies carry an error code next to message, and a field naming what failed where there is one: invalid_param with param, not_found with resource, unsupported_network, plan_required with required_tier. message is still there, so code that reads it keeps working; branch on error from now on, since message text can change. Examples on error handling.
• Unchanged: prices stream keyless on the showcase assets and with any key on any token, and reserves stream with any key, free ones included.

curl -H "Authorization: $DEXPAPRIKA_API_KEY" \
  "https://api-pro.dexpaprika.com/networks/ethereum/pools/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/transactions?limit=20"

​

Added

• GET /networks/{network}/tokens/{token_address}/ohlcv returns OHLCV candles for a token instead of a pool. Prices are a volume-weighted USD price across every pool the token trades in on the network, and volume is the USD traded across all of them. You no longer have to pick a pool or convert a pair price to dollars to chart a token.
• Same parameters as pool OHLCV: start (relative offsets such as -24h work), end, interval from 1m to 24h, and up to 1000 candles per request.
• The candles come from the same series as the /sse/ohlcv stream, so history from REST and live candles from the stream line up.

curl -H "Authorization: $DEXPAPRIKA_API_KEY" \
  "https://api-pro.dexpaprika.com/networks/ethereum/tokens/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2/ohlcv?start=-24h&interval=1h&limit=24"

​

Added

• from and to on GET /networks/{network}/pools/{pool_address}/transactions accept a relative offset from now (-1h, -24h, -7d), RFC3339 or YYYY-MM-DD, next to unix seconds. from=-1h returns the last hour of transactions.
• created_after and created_before on the four search endpoints (/pools/search, /networks/{network}/pools/search, /tokens/search, /networks/{network}/tokens/search) accept the same shapes. created_after=-24h returns what was created in the last day.
• Unix seconds keep working unchanged. The query block of a search response shows the resolved unix timestamp.

​

Changed

​

Fixed

​

Migration

• Upgrading is optional. start is passed through as a string in every SDK, so -24h works on older releases too. Two exceptions: the CLI before 0.7.0 refuses -24h, and the Go SDK before 1.9.0 lowers any Limit above 366 to 366.
• Relative times on transactions and search need the CLI 0.8.0 or later and the MCP server 2.6.0 or later; older releases refuse them. On the PHP SDK before 1.10.0, from and to set through $client->pools never reach the API. The search filters created_after and created_before already passed strings through in every SDK, so they work on older releases.
• A 403 from OHLCV is a plan limit, not a transient failure, so do not retry it unchanged. See OHLCV limits by plan, or register a free key for 7 days at 10m and longer.

​

Changed

• GET /networks/{network}/pools/{pool_address}/ohlcv is limited per plan. How far back you can query and how fine the candles can be now depends on the plan behind the request:

  Plan	Candle intervals	History depth
  Free (no key)	1h, 6h, 12h, 24h	last 24 hours
  Free (registered key)	10m and longer	last 7 days
  Dev	all	last 30 days
  Pro / Enterprise	all	unlimited

• start, end and count_back are all checked against the window. A range that starts inside the window but reaches before it is trimmed to the window; a range that lies entirely before it is rejected.
• A request outside the plan’s limits returns 403 with {"message": "..."}. The message names the plan that lifts the limit, for example OHLCV history beyond the last 7 days requires a Dev plan (30 days) or a Pro plan (unlimited). The interval check runs before the history check.

​

Added

• start and end on GET /networks/{network}/pools/{pool_address}/ohlcv accept a relative offset from now: -24h, -7d, -90m, -30s. start=-24h always selects the last 24 hours, which every plan may query. start stays required.
• limit defaults to 10 candles (was 1).

​

Fixed

• A missing or malformed start or end returns 400 again instead of 403 on the free tiers.

​

Migration

• Keyless integrations that pull sub-hour candles or more than 24 hours of history: register a free key for 10m+ candles over 7 days, or move to Dev / Pro for 1m and 5m candles and deeper history.
• Treat 403 on this endpoint as a parameter error, not a transient failure: do not retry it with backoff. Full details on the rate limits page.

​

Changed

• Keyless requests get 10,000 credits per IP per rolling 30 days, down from 30,000. The per-minute rate (15) and everything else about the keyless tier are unchanged. Both REST and streaming draw from the same per-IP budget.

​

Migration

• Anything that ran keyless above 10,000 credits a month should register a free key: 100,000 credits per rolling 30 days at 30 requests a minute, no card. See rate limits.

​

Added

• Dev plan, $30 a month: 120 requests per minute, 500,000 credits per billing period, 30 concurrent streams, real-time data. Same hosts and key format as Pro: https://api-pro.dexpaprika.com for REST and https://streaming-pro.dexpaprika.com for SSE.

​

Changed

• Free key: 30 requests per minute and 100,000 credits, down from 50 and 300,000. Keyless: 15 requests per minute per IP and 30,000 credits per IP, down from 50,000.
• Keyless and free keys now count usage over a rolling 30-day window instead of a calendar month. There is no reset date, and their 402 bodies carry no resets_at. Dev and Pro reset with the billing period.
• Pro: 500 requests per minute, up from 300. Credits stay at 5,000,000 per billing period.
• Overage on Dev and Pro: $20 per additional 1,000,000 records, capped by the limit you set in the console.
• Bulk credit packs are no longer sold. Packs already purchased keep draining.

​

Migration

• An integration sized against the old free-key limits will start seeing 429. Read ratelimit-limit and x-credits-remaining on every response, or move to Dev. Current figures are always on pricing; limits by tier are on rate limits.

​

Added

• GET /sse/ohlcv on https://streaming-pro.dexpaprika.com streams sealed token candles for any indexed token on every chain we index, at 1s, 5s or 60s. The event type is token_ohlcv.
• Resume a dropped connection with Last-Event-ID, or backfill the last 15 minutes with since. Each candle, backfilled ones included, is one credit; pings are free.
• Available on Dev, Pro and Enterprise keys. Keyless and free keys get 403. Full guide in OHLCV streaming, parameters at GET /sse/ohlcv.

​

Added

• Pro and Enterprise now authenticate against https://api-pro.dexpaprika.com, and https://streaming-pro.dexpaprika.com for SSE, with the API key sent as the entire Authorization header value.
• Keys, usage and billing live in console.dexpaprika.com. Each account has one active key.

​

Unchanged

• Keyless and free registered keys keep calling api.dexpaprika.com and streaming.dexpaprika.com. Endpoints, paths, parameters and response shapes are identical on every host.

​

Migration

• Only the base URL changes, plus the Authorization header. A key sent to the host that does not match its plan returns 403 with "error": "wrong_host", and the body names the host to use. Full steps in upgrading to Pro, plans on pricing.

​

Removed

• GET /networks/{network}/dexes/{dex}/pools has been removed and now returns 410 Gone. Use GET /networks/{network}/pools/search with the dex_name query parameter instead. The whole route is gone, so an unknown DEX slug returns the same 410 rather than a 404.

​

Migration

• The DEX moves out of the path and into a query parameter: /networks/ethereum/dexes/curve/pools becomes /networks/ethereum/pools/search?dex_name=curve.
• dex_name takes the DEX id, the dex_id field from GET /networks/{network}/dexes, matched case-insensitively. Passing that response’s dex_name field instead, a display name like Uniswap V3, returns an empty results array rather than an error.
• Pagination is cursor-based. Read has_next_page and next_cursor from the response and pass next_cursor back as cursor, instead of using page. There is no page_info object on the replacement.
• Rows arrive in a results array rather than pools.
• The 24h volume field is volume_usd_24h. There is no bare volume_usd, and order_by=volume_usd is rejected with a 400, so sort with order_by=volume_usd_24h.
• dex_name also applies on the cross-network GET /pools/search, which the removed endpoint had no equivalent for. Combine it with chains to scope the result, for example ?dex_name=uniswap_v3&chains=base.

​

Removed

• GET /networks/{network}/tokens/{token_address}/pools has been removed and now returns 410 Gone. Use GET /networks/{network}/pools/search with the new token_address query parameter instead.

​

Added

• token_address filter on pool search. GET /networks/{network}/pools/search now accepts token_address to restrict results to pools that contain the token on the given network. It combines with all existing search filters and sorting (order_by, default volume_usd_24h).

​

Migration

• The filter is network-scoped only. The cross-network GET /pools/search accepts token_address but silently ignores it, so use the per-network path when filtering by token.
• token_address takes a single token. Repeating the parameter does not act as a pair filter; the API uses only one of the values (not guaranteed by order). The old address (second-token pair filter) and reorder (pair-perspective flip) parameters have no equivalent on pool search.
• Pagination is cursor-based (has_next_page + next_cursor), rows are in a results array, and sorting uses order_by=volume_usd_24h instead of the old order_by=volume_usd.
• An unknown token_address returns HTTP 200 with an empty results array, not an error.

​

Removed

• GET /networks/{network}/pools and GET /networks/{network}/pools/filter are replaced by GET /networks/{network}/pools/search
• GET /pools is replaced by GET /pools/search
• GET /networks/{network}/tokens/filter and GET /networks/{network}/tokens/top are replaced by GET /networks/{network}/tokens/search
• Need results across several networks in one call? Use GET /pools/search and GET /tokens/search with a chains filter (for example chains=ethereum,base,solana).

​

Added

• Richer filtering on the search endpoints. Min/max ranges for volume_usd_24h, volume_usd_7d, volume_usd_30d, liquidity_usd, txns_24h, price_usd, and price_change_percentage_24h; created_after / created_before; dex_name (pools); fdv_usd_min / fdv_usd_max (tokens). The volume_7d, volume_30d, and liquidity_usd filters now work, which they did not on the old filter endpoint.

​

Migration

• Parameter renames: volume_24h_min becomes volume_usd_24h_min, sort_by becomes order_by, sort_dir becomes sort.
• Pagination is now cursor-based. Read has_next_page and next_cursor from the response and pass next_cursor back as cursor, instead of using page.
• Response rows are in a results array. Each pool row uses id (the pool address) and transactions_24h.

​

Deprecated

• The legacy /stream price endpoint is deprecated and scheduled for removal in 2027. Migrate to /sse/prices. The t_p event is replaced by token_price.

​

Changed

• Reserves stream restructure. The /sse/reserves feed no longer emits a single shared reserve_update event. Each subscription method now has its own event name, so you match on the method you asked for:
  • method=pool_reserves emits a pool_reserves event with the full pool snapshot. That means the tokens array with per-token reserve and delta, plus two new fields: timestamp and block_timestamp.
  • method=token_reserves emits a token_reserves event flattened to the subscribed token’s reserve state in the affected pool, plus two new fields: updated_at and timestamp.
  • If you were matching on reserve_update, stop. Switch your handler to the method-named event or you will receive nothing.

​

Added

• request_id correlation on streams. Every SSE endpoint (/sse/prices and /sse/reserves, both GET and POST) now takes an optional request_id query parameter, and the POST body accepts it per asset. The server echoes it back on data events as an SSE request_id: line, which is what you want when several subscriptions share one multiplexed POST connection. It is omitted from ping, warning, and error events. The value has to be a non-negative integer (0 to 4294967295); send anything non-numeric and the request is rejected with {"message": "invalid query parameters: request_id (must be a number)"}. On the POST body the default is the asset’s array index.

​

Notes

• Stream error events always carry a single {"message": "..."} payload. That is now stated explicitly in the streaming reference.

​

Breaking changes

• getTokenMultiPrices response shape. Previously returned a bare array of price entries; now returns an object { prices: [...], missing_tokens: [...] }. Tokens that upstream cannot price (invalid address, no liquidity, unknown contract) are surfaced in missing_tokens rather than silently dropped.
  • Migration: replace response.map(...) with response.prices.map(...). Check response.missing_tokens.length > 0 to detect partial failures.
• search response pools[].dex_id renamed to factory_id. In search.pools[], upstream emits the DEX factory contract address under dex_id, while getNetworkPools emits the slug under the same key. The MCP layer now renames this to factory_id in search responses, matching getPoolDetails and getPoolTransactions which already use factory_id for this concept.
  • Migration: if you read search.pools[].dex_id expecting a slug, read dex_name (human-readable) or look up factory_id against getNetworkDexes.

​

Added

• Network synonym resolution. Common alternate names (eth, matic, avax, bnb, sol, arb, op, pol, cro, mnt, ftm, trx, etc.) now resolve to their canonical network IDs at the wire layer. getCapabilities.network_synonyms advertised these previously; now the upstream actually honors them on every endpoint that takes a network parameter.
• search optional limit parameter. Caps items returned per category (tokens, pools, dexes). Applies independently to each category: limit=3 returns up to 3 hits in each of the 5 categories.
• getCapabilities.tools_count field exposing the canonical 17-tool count.
• getTokenMultiPrices.missing_tokens array surfacing tokens upstream could not price.
• getPoolOHLCV.interval now accepts 1m and 10m (in addition to existing 5m/15m/30m/1h/6h/12h/24h).
• Canonical alias parameters added alongside legacy names. Both accepted; canonical is recommended for new code:
  • sort_dir (canonical) / sort (legacy alias): sort direction
  • sort_by (canonical) / order_by (legacy alias): sort field
  • paired_token_address (canonical) / address (legacy alias): second-token filter on getTokenPools
  • inversed (canonical) / reorder (legacy alias): pair-perspective flip on getTokenPools and getPoolDetails
• outputSchema declared on every tool. Strict-validating MCP clients (Cursor, Claude Desktop) now validate responses against documented shapes.
• structuredContent emitted on every tool result (MCP spec 2025-06-18+). Agents can consume parsed objects directly instead of re-parsing content[0].text.
• Tool annotations (readOnlyHint, idempotentHint, destructiveHint, openWorldHint) on every tool so hosts stop safe-prompting reads.
• Server-level instructions field in the MCP initialize response, a curated onboarding doc for agents.

​

Fixed

• getNetworkDexes limit parameter. Upstream /networks/{network}/dexes silently ignored limit and always reported page_info.total_items=0, total_pages=0. The MCP layer now slices client-side to the requested limit and patches page_info to reflect the real total count.
• getTokenDetails strict-validation rejection. Previously failed on strict-validating MCP clients with -32602 "data must NOT have additional properties" when upstream returned fields beyond the declared schema. Outer outputSchema is now permissive (additionalProperties: true) while declared fields remain typed. Same fix applied across all single-item-object tools (getTokenDetails, getPoolDetails, etc.).

​

Changed

• server.version bumped from 1.4.0 to 2.0.0.
• JSON Schema dialect on /json-rpc transport upgraded from draft-07 to 2020-12, aligning with the underlying OpenAPI 3.1 contract. SDK-managed /sse and /streamable-http transports still emit draft-07 (Zod v3 limitation); full 2020-12 alignment pending a future Zod v4 Mini migration.
• Rationale boilerplate in tool descriptions shortened from 506 to 249 characters to reduce input-token cost on every tool registration.
• submitFeedback field descriptions now document the 500-character caps on expected and observed (exceeding triggers -32602 input validation).

​

Known limitations

• liquidity_usd values returned by getNetworkPoolsFilter, getTopTokens, and getTokenDetails.summary are currently unreliable upstream: filter results may be empty and reported values may be incorrect. Upstream fix pending.
• total_supply decimal handling differs across endpoints (raw units in pool listings, decimal-adjusted in getTokenDetails). Upstream consistency pending.
• getTopTokens reports fdv: 0 for some major stablecoins (USDT, DAI). Upstream data quality fix pending.
• Field naming varies across endpoints (id vs address for token references; fdv vs fdv_usd; response wrappers pools/results/tokens). Naming alignment is on the roadmap.

​

Added

• GET /networks/{network}/pools/{pool_address}/transactions: new optional from and to query parameters (UNIX timestamps, int64) to filter transactions by time range.
  • from is inclusive, to is exclusive. Results are always capped to the last 7 days.
• Token schema: new telegram and twitter string fields for official social links.

​

Added

• New endpoint: GET /networks/{network}/tokens/filter for advanced token filtering. Removed since; use GET /networks/{network}/tokens/search.
  • Filter tokens by volume (volume_24h, volume_7d, volume_30d), liquidity (liquidity_usd), FDV (fdv_min, fdv_max), transaction count (txns_24h_min), and creation date (created_after, created_before).
  • Sort by volume_24h, volume_7d, volume_30d, liquidity_usd, txns_24h, created_at, or fdv.
  • Paginated response with page_info.
• New endpoint: GET /networks/{network}/tokens/top for top tokens on a network. Removed since; use GET /networks/{network}/tokens/search.
  • Ranked token list with enriched metadata and multi-timeframe metrics (24h, 1h, 5m).
  • Order by volume_24h, price_usd, liquidity_usd, txns, or price_change.
  • Each token includes buy/sell counts, volume, and price change per interval.
• New schemas: TokenFilterResponse, TokenSearchResult, TopTokenResponse, TopTokenItem, TopTokenTimeData.

​

Changed

• GET /networks response schema updated from Network to NetworkMetrics with new fields: volume_usd_24h, txns_24h, pools_count.
• GET /networks/{network}/dexes response enriched with dex_id, volume_usd_24h, txns_24h, pools_count per DEX.
• GET /networks/{network}/pools/filter: PoolSearchResult now extends PoolWithPrices via allOf, adding volume_usd_7d and liquidity_usd.
• Pool filter parameters volume_7d_min, liquidity_usd_min, and liquidity_usd_max are now functional.
• New pool filter parameters: volume_7d_max, volume_30d_max.

​

Known limitations

• volume_30d_min and volume_30d_max parameters on pool and token filter endpoints are documented but not yet functional.

​

Added

• New endpoint: GET /networks/{network}/pools/filter for advanced pool filtering.
  • Filter pools by 24h volume range (volume_24h_min, volume_24h_max), transaction count (txns_24h_min), and creation date (created_after, created_before).
  • Sort by volume_24h, volume_7d, volume_30d, liquidity, txns_24h, or created_at with asc/desc direction.
  • Paginated response with page_info including total_items and total_pages.
• New schemas: PoolFilterResponse and PoolSearchResult.

​

Known limitations

• volume_7d_min, volume_30d_min, liquidity_usd_min, and liquidity_usd_max parameters are documented but not yet functional. These will be enabled in a future update.

​

Changed

• GET /networks/{network}/multi/prices: requests are now limited to a maximum of 10 tokens per call.
• Parameter encoding updated to a single comma-separated tokens list (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/prices for batch token price retrieval on a network.
  • Request: repeatable tokens query 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.

​

Changed

• AssetPrice schema added and documented in OpenAPI.
• Internals: performance optimization to fetch token summaries conditionally.

​

Compatibility

• Certain price-related fields now use omitempty semantics 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_symbol and token_1_symbol fields to transaction objects for explicit token symbol tracking.
  • Added price_0, price_1, price_0_usd, and price_1_usd fields to transaction objects for detailed price reporting.
  • Added created_at field to transaction objects for precise transaction timestamping.

​

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.

​

Deprecated

• BREAKING: The /pools endpoint has been permanently deprecated and now returns 410 Gone
• Users should migrate to /networks/{network}/pools to get top pools for each specific network

​

Changed

• Enhanced deprecation messaging with clear migration paths for affected endpoints

​

Migration guide

GET /pools

GET /networks/ethereum/pools
GET /networks/solana/pools
GET /networks/fantom/pools

​

Added

• Introduced the optional reorder query parameter to the /networks/{network}/tokens/{token_address}/pools endpoint. 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_usd and sell_usd fields to provide monetary values for trades
• Added last_price_usd_change field 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/sell fields to buys/sells for consistency (Breaking Change)
• Changed network response format from object to array for cleaner consumption
• Updated network schema with improved field naming (display_name instead of just name)
• 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

​

Added

• Initial public beta release
• Support for Solana network
• Basic endpoints for networks, DEXes, pools, and tokens
• Search functionality across tokens, pools, and DEXes
• OHLCV data for historical price tracking
• Transaction history for pools

​

Added

• Pool and token details endpoints
• Initial version of search functionality

​

Changed

• Improved error handling and response formats
• Enhanced documentation with examples

​

Added

• Initial development release
• Preliminary endpoints for pools and DEXes