SushiSwap API: six endpoints and the only DEX on Katana
Sushi runs a public API for prices, quotes and swap transactions, with no key needed to read. On 16 November 2026 SushiSwap (SUSHI) was Katana's core DEX, the only one DexPaprika indexed there, and live on six more chains.

SushiSwap API access starts at api.sushi.com: no key needed for prices or quotes. According to DexPaprika data, SushiSwap was the only DEX indexed on Katana on 16 November 2026, Katana's core exchange, and it runs on six more chains in the index. The API documents six endpoints and will tell you a token's live price, quote a specific trade, and build the swap transaction for you to sign.
For price history and past trades, Sushi points to its subgraphs, and a DEX data index serves both over REST, shown below.
SushiSwap gets treated as a name from 2020's DeFi summer, an AMM long since overtaken by newer designs. That undersells the API and misses where the project still matters. Sushi ships a working, keyless price and quote API, and on one chain it is not a legacy anything: it is the chain's designated spot exchange.
This piece covers what api.sushi.com returns, the one thing that changes once you look past Ethereum, and what SushiSwap's volume looked like across the seven chains DexPaprika indexes it on, on 16 November 2026.
The SushiSwap API's six endpoints, one call each
Sushi's OpenAPI document lists six GET endpoints at api.sushi.com, with worked examples for price, quote and swap at docs.sushi.com. All six answered live, and reading data needs no key.
Calling it needs nothing but the URL:
curl "https://api.sushi.com/price/v1/1/0x6b3595068778dd592e39a122f4f5a5cf09c90fe2"
0.15341884011002566
That is SUSHI's own price, in USD, read straight off Sushi's infrastructure. No key, no signup, no header.
Price history and trades: Sushi's subgraphs
/price/v1 returns the price now, and /quote prices a trade you are about to make. Both are built for the moment of trading.
For anything historical, Sushi's docs point to its subgraphs, five of them by name: blocks, clAMM for V3 pools, cpAMM for V2 pools, xSUSHI and Blade. Candles and past swaps for a pool come from those, or from a DEX index over REST, covered further down.
SushiSwap was Katana's only indexed DEX on 16 November 2026
DexPaprika indexes SushiSwap on seven networks: Ethereum, Arbitrum, Base, Optimism, Polygon, Katana and Scroll. Here is its 24 hour volume on each, measured 16 November 2026, next to every DEX DexPaprika carries for that chain:
On Ethereum, Arbitrum, Base and Polygon, SushiSwap shares deep markets with much larger venues, up to 0.26% of the DEX volume DexPaprika indexes there. On Optimism it held 3.07%, $131,107 in a day, up from 0.54% at our first measurement on 23 September.
Katana is where Sushi leads. DexPaprika's DEX list for Katana has exactly two rows, SushiSwap's V2 and V3 deployments, and nothing else. Katana's own docs explain why: "Sushi (SushiSwap) is Katana's core decentralized exchange (DEX)." It is one of the chain's core apps, with 400 million KAT of liquidity-mining incentives set aside for it. On Katana, Sushi is the chain's designated spot exchange.
Candles and swaps for a SushiSwap pool
Candles and per-swap rows for any SushiSwap pool also come from a DEX data index over REST. I ran this on 16 November 2026 against SushiSwap V3's busiest pool on Katana: vbETH paired with vbUSDC, $327,191 of liquidity, $142,808 traded that day.
Hourly candles work without a key for the last 24 hours. A relative start keeps the call valid whenever you run it:
curl "https://api.dexpaprika.com/networks/katana/pools/0x2a2c512beaa8eb15495726c235472d82effb7a6b/ohlcv?start=-12h&interval=1h&limit=5"
That returns an array of candles, each carrying time_open, time_close, open, high, low, close and volume. Swap the pool address for any other SushiSwap pool, or for Uniswap, Aerodrome or Orca elsewhere on DexPaprika, and the response keeps the same shape.
Individual swaps come from the pool's /transactions endpoint, one row per swap. That endpoint needs a Dev or Pro plan; without a key it answered HTTP 403 on 16 November.
Candles need no key. A free key from console.dexpaprika.com raises the rate and the quota and reaches further back in candle history, and current numbers for every tier are on the pricing page rather than in this article, because they move. Worth knowing before you build: free tier data can be up to 60 seconds delayed, and real time is the paid tier.
Common questions
Does SushiSwap have an API?
Yes. Sushi's own API at api.sushi.com documents six endpoints, covering token prices, token metadata, trade quotes, swap transactions and the router's liquidity sources. For historical data, Sushi points to its subgraphs.
Do you need an API key for SushiSwap?
Not to read price or quote data; both endpoints answered every call in this piece with no key and no authentication header. The swap endpoint accepts an optional key from sushi.com/portal, useful at higher volume but not required for a working transaction back.
What are the SushiSwap API rate limits?
Sushi's docs describe a rate limit, with a dedicated error page for exceeding it. Pace your calls and back off on anything other than a 200.
Does the SushiSwap API give historical prices or OHLCV?
No. /price/v1 returns the current price only. For history, Sushi's docs point at its subgraphs rather than a REST endpoint.
Is SushiSwap the biggest DEX on any chain?
On the seven chains DexPaprika indexes it on, yes, on exactly one: Katana, where it was the only DEX in the index on 16 November 2026, matching Katana's own description of Sushi as its core DEX.
Which SushiSwap version should I index?
Both. V2 and V3 carry volume on different chains, and neither is a subset of the other. V3 (sushiswap_v3) carries effectively all of the volume on Optimism, Katana and Scroll, while V2 (sushiswap) is the only version DexPaprika lists on Polygon. Index one and you miss real volume somewhere on this list.
How these numbers were measured
Everything above was read off a live source on 16 November 2026, except the 23 September figures, which come from our first measurement with the same calls.
The Sushi endpoint list comes from Sushi's OpenAPI document (docs.sushi.com/openapi.yaml), six paths, each called live. The subgraph list comes from Sushi's docs, read in full by sitemap, 109 pages.
The volume table is seven calls to DexPaprika's DEX list, one per network, summing every row returned for SushiSwap against the total of every row returned for that network, so the rows and the share agree by construction. The Katana quote is read off the Sushi page in Katana's docs directly.
The OHLCV call is quoted as it ran and returned HTTP 200 without a key, against SushiSwap V3's top pool on Katana by 24 hour volume; the transactions call returned HTTP 403.
Every volume figure is a 24 hour window closing on the measurement, so expect it to have moved. Katana is the smallest chain in this table, so its composition is also the one most likely to add a second indexed DEX first.
Full REST reference at docs.dexpaprika.com.
The same question for three other DEXes: what the Uniswap API returns, what the Raydium API covers on Solana, and what PancakeSwap documents for BNB Smart Chain.
Original CoinPaprika guide.