Meteora API for DLMM, DAMM and DBC pools on Solana

Meteora gets talked about as one product. That undersells it. Meteora is five programs on Solana: DLMM for concentrated liquidity, DAMM v1 and DAMM v2 for standard pools, a dynamic bonding curve for new token launches, and a yield vault underneath most of them. Most of them ship their own public API: I counted five, one each for DLMM, DAMM v1, DAMM v2, the vault and Stake2Earn, and I called all five today.

Meteora API endpoints, product by product

Five products, five hosts, no shared schema between them. Every one is keyless, no header and no signup:

DLMM and DAMM v2 are the two that matter for market data, and they work the same way. /pools/{address}/ohlcv takes a timeframe from 5 minutes to 24 hours and returns open, high, low, close and volume. /pools/{address}/volume/history gives daily volume and fees going back over the pool's life. Both answered 200 with no key, against Meteora's busiest DLMM pool, SOL-USDC at 5rCf1DM8LjKTw4YqhnoLcngyZYeNnQqztScTogYHAS6:

That is a real candle, on Meteora's own infrastructure, for a Meteora pool. DAMM v1, the older constant-product pools, does not have this. /pools-metrics gives you today's TVL and volume, /pools/search gives you current pool state, and that is where DAMM v1's own API stops. Ask it what a pool did three days ago and there is nothing to answer with.

No swap feed, and no documented bonding curve API

I read all 46 documented paths across the five specs (19 DLMM, 7 DAMM v2, 10 DAMM v1, 6 Dynamic Vault, 4 Stake2Earn) for the words trade, swap, transaction and tx. None of the five has one. The closest is DLMM's endpoint for a position's historical events, and that is deposits and withdrawals against your own liquidity position, not a record of who swapped against the pool and at what price.

The Dynamic Bonding Curve, the product behind most new token launches on Meteora, is not in the documented set at all: no Data API overview page, no OpenAPI spec, no /docs. There is a live endpoint on the same infrastructure pattern, dbc.datapi.meteora.ag/pools, and it answered 200 with 1,684,749 pool records when I called it. But the object it returns carries only identity fields (the pool address, the two token mints and their vaults, the creator and the pool config), no price, no volume, no TVL, and asking that same host for OHLCV on a pool address returns a 404. Whatever is behind that endpoint, it has not shipped a market-data surface yet.

Meteora was 15.7% of Solana's indexed DEX volume on 23 September 2026

DexPaprika indexes Meteora as three separate DEXes on Solana: "Meteora" for DLMM pools, "Meteora DAAM v2" for DAMM v2, and "Meteora DBC" for the bonding curve. Here is every DEX DexPaprika counted on Solana that day, by 24 hour volume:

Meteora's three rows add up to $679,550,659, which is 15.7% of the day. PumpSwap alone was 67.5%. Note that DexPaprika's bare "Meteora" row is DLMM only, not the whole brand: reading it as "all of Meteora" leaves $426.7 million of DAAM v2 and DBC volume uncounted.

Fifteen point seven percent is a real share, second only to PumpSwap and about double Orca's. If you are building for MET holders or for liquidity providers on DLMM specifically, Meteora's own API is the right, first place to look, and on the evidence above it is a good one. If the question is "what happened on Solana DEXes today," a Meteora-only integration still misses about five dollars out of every six traded.

Swaps, and one schema across Meteora's products

The two things Meteora's own APIs do not give you together: a per-trade swap feed, and a schema that also covers Orca, PumpSwap and the rest of the chain without changing shape. I ran both calls below on 23 September 2026 against the same DLMM pool used above. The candles work without a key; since 30 September 2026 the swap feed needs a Dev or Pro plan.

Hourly candles for that pool, this time from DexPaprika rather than Meteora's own host, same shape it would return for any pool on any Solana DEX:

Individual swaps, which are not in any of Meteora's five APIs, on api-pro.dexpaprika.com with your key on its own in the Authorization header:

Each row carries sender and recipient, token_0_symbol and token_1_symbol, both amounts, price_0_usd, and factory_id. For this pool factory_id reads LBUZKhRxPF3XUpBCjp4YzTKgLccjZhTSDM9YuVaPwxo, which is the DLMM program's own on-chain address, listed as such on Meteora's own program page. The same field distinguishes a DLMM trade from a DAMM v2 or DBC one without you having to know which host to ask.

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 live 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 Meteora have an API?

Yes, five of them. DLMM, DAMM v1, DAMM v2, Dynamic Vault and Stake2Earn each publish a separate public REST API with its own host and its own OpenAPI spec, all documented at docs.meteora.ag under each product's developer guide.

Do you need an API key for Meteora's APIs?

No. Every endpoint I called across all five products on 23 September 2026 answered 200 with no key and no authentication header.

Does the Meteora API give historical prices or OHLCV?

For DLMM and DAMM v2, yes: both have an /ohlcv endpoint with timeframes from 5 minutes to 24 hours, plus a separate daily volume history endpoint. DAMM v1, the older pools, has neither and only returns current state.

Can I get Meteora swap history from the API?

Not from Meteora's own APIs. None of the five documented products exposes individual trades, only pool state, candles and (for DLMM) your own position and portfolio history. Per-trade data means reading it from an index that already parses the DLMM, DAMM and DBC programs.

Does Meteora's Dynamic Bonding Curve have a public API?

Not a documented one. DLMM, DAMM v1, DAMM v2, Dynamic Vault and Stake2Earn each have a published Data API. DBC does not appear in Meteora's own API index, though an undocumented endpoint on the same infrastructure answers pool-list queries with identity fields only, no price or volume.

What is Meteora's share of Solana DEX volume?

On 23 September 2026, DexPaprika's indexed DLMM, DAMM v2 and DBC pools together carried 15.7% of Solana's DEX volume across the nine DEXes it tracks on the network, behind PumpSwap's 67.5%.

How these numbers were measured

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

The endpoint counts and groupings come from each product's own OpenAPI document at docs.meteora.ag: 19 paths for DLMM, 7 for DAMM v2, 10 for DAMM v1, 6 for Dynamic Vault, 4 for Stake2Earn. The absence of a trade or swap endpoint is a search across all 46 paths for four terms, listed above so you can repeat it. The DBC finding is a direct call to dbc.datapi.meteora.ag/pools, which returned 200, and to the OHLCV path on the same host and a sample pool address, which returned 404.

The Solana DEX table is one call to DexPaprika's DEX list for Solana (GET /networks/solana/dexes), which returns all nine DEXes in one response. Meteora's share is its three rows divided by the sum of all nine rows on that page, not by any chain-wide total, so it is Meteora's share of DexPaprika-indexed Solana DEX volume specifically. The OHLCV and transaction calls, both from Meteora's own DLMM host and from DexPaprika, are quoted verbatim and all returned 200. MET's ticker and market data were confirmed against CoinPaprika.

Every volume figure is a 24 hour window closing at measurement time, so expect movement, especially on the DBC and DAAM v2 rows, where pool counts run into the tens of thousands and turn over fast.

Full REST reference at docs.dexpaprika.com. DexPaprika's own page for Meteora's indexed pools is at dexpaprika.com/api/solana/meteora. Meteora's own API documentation sits under each product's developer guide at docs.meteora.ag.

The same question for another Solana DEX: what the Raydium API covers, and what a Solana DEX API adds. And if candles are the specific gap you are working around: how to get OHLCV candles for any DEX token.