GET /networks returns every blockchain DexPaprika indexes in one response, with the chain’s 24h DEX volume, transaction count and number of active pools. The id of each network is the value every other endpoint takes as {network}. No key is needed:
GET /stats totals, and a short script that ranks chains by activity.
Which plan you need
Both endpoints work on every plan, with the same data. A key changes the limits and the host, not the response.
The key goes in
Authorization on its own. Get one in console.dexpaprika.com and compare limits on pricing.
What each network carries
Use
id in code and display_name on screen. Ids are lowercase slugs and do not always match the chain’s marketing name, so look them up here rather than guessing: Binance Smart Chain is bsc.
Coverage totals with /stats
GET /stats returns four totals for the whole database:
pools here counts every pool ever indexed, while pools_count on /networks counts the pools on a chain with recent activity. Both are correct, they answer different questions, so do not add up pools_count and expect the /stats figure.
Rank chains by activity in Python
/networks comes back in no particular order. This script sorts it by 24h volume and prints the five busiest chains, two requests in total:
Things to know
Sort it yourself. The order of/networks is not by name or by volume, and it can change between calls.
Cache it. The list changes when a chain is added or retired, which is rare. Responses carry cache-control: max-age=60, and fetching it once per process start is plenty. Every call costs one credit, see credit usage.
Volume is DEX volume only. volume_usd_24h sums swaps on the DEXes DexPaprika indexes on that chain. It is not the chain’s total on-chain value transferred.
Where to go next
- List DEXes on a network: the exchanges behind each chain’s volume
- Networks reference and stats reference
- Coverage checker: look up a token or pool without code
- Pricing, console.dexpaprika.com and docs home