Curve API: pools, candles, trades, and one missing chain

Curve API gets lumped in with the "does it even have one" question that follows Raydium and PancakeSwap around, and it shouldn't. api.curve.fi, the address in most old tutorials, now answers with a 301 to api.curve.finance. Behind that redirect sits a full pool-and-registry API, plus a second, separate service built specifically for prices and trade history.

On Ethereum, Curve's two DexPaprika ids, the plain AMM and Curve TwoCrypto, carried 4.8% of indexed DEX volume the same day. That's Curve's second-largest share of the seven chains DexPaprika indexes it on. The largest is Plasma, and that's exactly where Curve's own API hasn't caught up.

Inside api.curve.finance: pools, registries and DAO rewards

api.curve.finance publishes an OpenAPI document at api.curve.finance/v1/openapi.json listing 44 GET paths, with a browsable copy at api.curve.finance/v1/documentation. Grouped by what they're for:

No key, no header, nothing to register for:

Every pool comes back with its coin balances, prices, virtual price and links to the Curve UI. For "what pools does Curve run, and what's in them right now", this is the source: it's the protocol's own account of itself, across 21 chains by its own count, covered below.

The Prices API: candles and trade history on a second host

This is the part that separates Curve from Raydium and PancakeSwap. A second, independent service, prices.curve.finance, documented at prices.curve.finance/feeds-docs, ships its own 138-path OpenAPI document. Buried in it are /v1/ohlc/{chain}/{address} and /v1/trades/{chain}/{address}, and both work.

Hourly candles for Curve's own USDC/USDT pool on Ethereum:

And a trade-by-trade feed for the same pool, across every pair it holds, no token addresses required this time:

Two things worth planning around. The OHLC endpoint needs the exact main_token and reference_token addresses for the pair, not only the pool address, and each request is capped to a window 300 times the aggregation size, so a year of hourly candles takes several calls. The trades endpoint caps each page at 100 rows. Both are parameters to design for.

What neither Curve API covers

Both services only know about Curve. Ask either one what Uniswap or Aerodrome is doing on the same chain and you get nothing, because that isn't the question they answer. Building something that needs to compare a token's price or liquidity across every DEX on a chain, not only Curve's own pools, means reaching for an index that covers more than one protocol.

The second gap is narrower, and looks more like it hasn't been updated yet than a deliberate choice. api.curve.finance/v1/getPlatforms lists the chains Curve considers itself deployed on: 21 of them, from Ethereum and Arbitrum down to newer additions like Sonic and Mantle. Plasma isn't on that list, and neither api.curve.finance's pool endpoints nor prices.curve.finance's /v1/chains/ recognize it as a valid chain id. Asking for Plasma returns a parameter error from one and "This chain is not supported" from the other.

DexPaprika's index disagrees with that list. Curve's StableSwap, TriCrypto and TwoCrypto pools on Plasma carried $1,781,229 of the chain's $11,662,934 in DexPaprika-indexed DEX volume on 23 September 2026, a 15.3% share, the largest Curve holds on any of the seven chains measured here. The busiest of those pools has been trading since 22 September 2025 and currently holds $685,343 in liquidity. Curve is live on Plasma. Its own API's coverage list hasn't caught up.

Curve's share of DexPaprika-indexed DEX volume, seven chains

Every DexPaprika network where Curve is indexed, 23 September 2026:

On five of these seven networks, DexPaprika lists Curve under one id, curve, plus curve_twocrypto on Ethereum specifically. On HyperEVM and Plasma the same pool families come split into curve_stableswap, curve_tricrypto and curve_twocrypto with no combined id, which is why those two rows sum three dex_id values each.

The same two calls, from a chain-level index

DexPaprika's OHLCV and transaction endpoints work the same way for a Curve pool as for any other DEX on the chain: a pool address, no token-pair parameters needed. I ran them on 23 September 2026 against the same USDC/USDT Curve pool on Ethereum used above, which did $30.3m of the day's volume. Candles work without a key:

Each candle carries time_open, time_close, open, high, low, close and volume.

Individual trades come from the transactions endpoint. Since 30 September 2026 it needs a Dev or Pro plan and runs on api-pro.dexpaprika.com, with the key on its own in the Authorization header:

Each row carries sender, recipient, both token symbols and amounts, price_0_usd, price_1_usd, created_at and factory_id, the contract behind the trade. The same shape works against Uniswap, Aerodrome or any other DEX on the same chain, which is the whole case for reaching for a chain-level index once a question stops being Curve-only.

The candles need no key to try. A free key from console.dexpaprika.com raises the rate and the quota, and current numbers for every tier are on the pricing page rather than in this article, because they move. Free-tier data can be up to 60 seconds behind; real-time is the paid tier.

Common questions

Does Curve have an API?

Yes, two. api.curve.finance covers pools, registries, APYs and lending vaults. prices.curve.finance covers OHLC candles, per-trade history and pool snapshots. api.curve.fi still works; it just redirects.

Do you need an API key for Curve?

No. Every endpoint called for this piece on 23 September 2026 answered with no key and no authentication header of any kind.

Does the Curve API give historical prices or OHLCV?

Yes, through prices.curve.finance/v1/ohlc/{chain}/{address}. It needs the exact token addresses for the pair, and each call is limited to a window 300 times the chosen aggregation size.

Can I get Curve swap history from the API?

Yes. prices.curve.finance/v1/trades/{chain}/{address} covers one pair at a time; /v1/trades/all/{chain}/{address} covers every pair in the pool, paginated at 100 rows per page.

What are the Curve API rate limits?

Neither service publishes one, and their responses carry no ratelimit-* headers to read a budget from. Both sit behind Cloudflare, so treat the limit as real and undisclosed: pace calls and back off on anything that isn't a 200.

Which chains does the Curve API cover?

getPlatforms lists 21, and prices.curve.finance/v1/chains/ reports pricing data for 10 of those. Neither list includes Plasma, where DexPaprika measured $1.78m of Curve volume on 23 September 2026.

How these numbers were measured

Everything above was read off a live source on 23 September 2026.

The 44 and 138 endpoint counts come from Curve's own OpenAPI documents at api.curve.finance/v1/openapi.json and prices.curve.finance/feeds-docs/openapi.json, parsed directly rather than read off the rendered Swagger pages. The 21-chain platform list is api.curve.finance/v1/getPlatforms; the 10-chain pricing coverage list is prices.curve.finance/v1/chains/. The Plasma gap was confirmed by calling both APIs' pool and chain endpoints with plasma as the chain id and reading the parameter error back.

Every DexPaprika figure comes from one call per network to DexPaprika's DEX list (GET /networks/{network}/dexes), which returns every DEX on the chain in one response. Curve's share is its listed dex_id volumes divided by the sum of every DEX's volume in that same response. The Curve OHLC and trades calls are quoted verbatim and returned 200. The DexPaprika candle and transaction calls also returned 200 on 23 September; the candle call is shown with a relative start, which works without a key, and the transaction call on api-pro, where it has needed a Dev or Pro plan since 30 September. Every volume figure is a 24 hour window closing on the measurement, so expect it to move, especially on Plasma, where a single day's number leans on a handful of pools.

Full REST reference at docs.dexpaprika.com. Curve's own docs are at docs.curve.finance, with the pool API at api.curve.finance/v1/documentation and the prices API at prices.curve.finance/feeds-docs. DexPaprika's live Curve page for Ethereum is at dexpaprika.com/api/ethereum/curve.

The same question for two other DEXes: what the Raydium API covers on Solana, and what the Uniswap API returns.