Raydium API: what it covers, and what a Solana DEX API adds
Raydium runs a real public API and it needs no key at all. It also has no price candles and no swap feed, and it covers a protocol that was 5% of Solana DEX volume on the day I measured it.
The short answer. Raydium runs a real public API at api-v3.raydium.io. It needs no key, no signup and no headers, it has 27 endpoints, and it will tell you about pools, token prices, farms and protocol config.
Two things are not in it. There are no price candles and there is no swap history. And it covers Raydium, which on 22 September 2026 was a minority of Solana DEX volume.
Raydium gets written about as though it has no API, usually by people selling one. That is not true and it is worth saying early: the Raydium API works, it is free to call, and for a lot of jobs it is the right thing to use.
What follows is the whole endpoint list read off Raydium's own OpenAPI document, the two categories of data that are genuinely absent from it, and what the rest of Solana looked like on 22 September 2026. Method at the end, including one number where our data and Raydium's disagree and I have not resolved which is right.
What the Raydium API actually gives you
Raydium API v3 publishes a Swagger page at api-v3.raydium.io/docs. Behind it sits an OpenAPI document with exactly 27 paths, every one of them a GET. Grouped by what they are for:
It really is keyless. Nothing to register for, no header to send:
curl "https://api-v3.raydium.io/main/info"
{"id":"...","success":true,"data":{"volume24":576515471.6,"tvl":1660290641.9}}
Responses come back shaped {id, success, data}, which is tidy and easy to handle. If what you need is "describe this Raydium pool" or "what does Raydium think this token is worth right now", stop reading and go use it. It is free, it is fast, and it is the protocol's own account of itself.
The two things that are not in it
I searched all 27 paths for the words you would expect if either feature existed. Nothing matched ohlc, candle, kline, chart, trade, swap, tx or history.
There are no price candles. /mint/price gives you the price now. Ask it again in an hour and you get the price then. Nothing in the API hands you an open, high, low and close for a period, so a chart has to be something you build and store yourself, one sample at a time, starting from the day you begin polling. Backfill is not an option because the history was never exposed.
There is no swap feed. The closest thing is /pools/line/liquidity, which draws liquidity over time. That is a different question from who traded, in what size and at what price. If you want per-trade data out of Raydium's own API, it is not there, and the fallback is parsing Solana transactions yourself against the AMM, CLMM and CPMM programs.
Neither absence is a criticism. Raydium built an API that serves the Raydium interface, and both gaps sit outside what that interface needs.
Raydium was 5% of Solana DEX volume on 22 September 2026
This is the part that decides whether a Raydium-only API is the right shape for what you are building. Here is every DEX indexed on Solana that day, by 24 hour volume:
Raydium's two entries add up to $238,316,633, which is 5.1% of the day. PumpSwap on its own was 66.7%.
Put that next to what people actually ask a Solana DEX API for. The usual question is "what is this token worth and where is it trading", and for a token that launched this month the answer is very often PumpSwap or Pump.fun, not Raydium. A Raydium-only integration answers that question correctly for the pools Raydium holds and returns nothing at all for the rest of the chain, with no error to tell you which case you are in.
Where our number and Raydium's disagree
Raydium's own /main/info reported $576,515,472 of 24 hour volume that same day. We measured $238,316,633 across the two Raydium entries we index. That is a gap of about $338m and I am not going to pretend it away.
What I can show is that Raydium runs three on-chain programs, not two. AMM v4 and CLMM are both in our index. CPMM is a separate program with its own configuration endpoint, /main/cpmm-config, sitting alongside /main/clmm-config, and it does not appear in our DEX list under any id. So at least part of the gap is a program we are not carrying, and it is now filed as a coverage bug on our side rather than a footnote in an article.
The rest may be counting rules. Protocols and indexers routinely disagree about routed volume and about which of a protocol's own products belong in a headline figure, and Raydium is entitled to count its own activity its own way.
Take the share both ways. At our figure Raydium is 5.1% of Solana DEX volume. Substituting Raydium's own number and adjusting the chain total gives 11.4%. The point of this section survives either arithmetic: Raydium is a minority of the chain, and a Raydium-shaped API is the wrong shape for a Solana-wide question.
Candles and swaps for a Raydium pool
The two things missing from Raydium's API are the two things a DEX data API exists to provide. Both calls below ran against DexPaprika on 22 September 2026, against a Raydium CLMM pool doing $49.5m a day. The candles need no key; since 30 September 2026 the swap feed needs a Dev or Pro plan.
Hourly candles, which Raydium's API cannot give you at any price:
curl "https://api.dexpaprika.com/networks/solana/pools/3ucNos4NbumPLZNWztqGHNFFgkHeRMBQAVemeeomsUxv/ohlcv?start=-24h&interval=1h&limit=5"
That returns an array of candles, each carrying time_open, time_close, open, high, low, close and volume. Swap 1h for a shorter interval and the shape does not change.
Individual swaps, which are not in Raydium's API either, on api-pro.dexpaprika.com with your key on its own in the Authorization header:
curl -H "Authorization: YOUR_API_KEY" "https://api-pro.dexpaprika.com/networks/solana/pools/3ucNos4NbumPLZNWztqGHNFFgkHeRMBQAVemeeomsUxv/transactions?limit=3"
Each row carries sender and recipient, token_0_symbol and token_1_symbol, the two amounts, price_0_usd and price_1_usd, plus created_at, created_at_block_number, log_index and factory_id. That last one tells you which program the trade went through, which matters on a chain where one protocol runs three of them.
The same two calls work against Orca, Meteora, PumpSwap and the rest of the list above without changing shape, which is the whole argument for a chain-level index over a protocol-level one.
Keyless is enough to try the candles. 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. Worth knowing before you build: free-tier data can be up to 60 seconds behind, and real-time is the paid tier.
Common questions
Does Raydium have an API?
Yes. Raydium API v3 at api-v3.raydium.io, 27 GET endpoints, documented at api-v3.raydium.io/docs and in Raydium's own docs under API reference.
Do you need an API key for Raydium?
No. Every endpoint I called on 22 September 2026 answered 200 with no key and no authentication header of any kind.
What are the Raydium API rate limits?
Raydium does not publish one, and the responses do not carry ratelimit-* headers to read a budget from. The service sits behind Cloudflare, so treat it as a limit that exists and is not disclosed: pace your calls and back off on anything that is not a 200.
Does the Raydium API give historical prices or OHLCV?
No. There is no candle, OHLCV or kline endpoint in the specification. /mint/price returns the current price only, and /pools/line/liquidity is liquidity over time rather than price.
Can I get Raydium swap history from the API?
Not from Raydium's own API. Per-trade data means either parsing Solana transactions against the AMM, CLMM and CPMM programs yourself, or reading it from an index that already does.
Which Solana DEX should I index first?
On 22 September 2026, PumpSwap carried two thirds of the chain's DEX volume and Pump.fun held 46,537 pools, more than any other venue on the list. If you are covering new tokens, that is where they are. If you are covering established pairs, Orca and Raydium CLMM matter more. Covering one venue only will misprice something eventually.
How these numbers were measured
Everything above was read off a live source on 22 September 2026.
The endpoint count and the groupings come from Raydium's own OpenAPI document, which its Swagger page loads at api-v3.raydium.io/docs/swagger-ui-init.js. I parsed the document rather than reading the rendered page, so the count of 27 is the specification's own, not mine. The absence of candle and trade endpoints is a search across all 27 paths for eight terms, listed above so you can repeat it.
The Raydium volume and TVL figures are one keyless GET /main/info. The Solana table is one keyless GET /networks/solana/dexes against api.dexpaprika.com, with every figure from the same response so the rows and the total agree. The OHLCV and transaction calls are quoted verbatim and both returned 200.
The $338m disagreement is unresolved and is tracked on our side as a coverage issue rather than left as an article footnote. Where a claim in this piece depends on it, I have given the share both ways.
Every volume figure is a 24 hour window closing on the measurement, so expect movement. Solana's composition is the part most likely to look different in a month: the leader board here is driven by token launches, which is exactly the kind of activity that moves venues quickly.
Full REST reference at docs.dexpaprika.com. There are per-DEX pages with a live swap feed for Raydium, Orca, Meteora, PumpSwap and Pump.fun.
The same question for two other DEXes: what the Uniswap API returns, and what PancakeSwap documents for BNB Smart Chain.
Původní průvodce CoinPaprika.