get deprecated
https://public-api.birdeye.so/defi/ohlcv/pair
Retrieve candlestick data in OHLCV format of a specified pair. Maximum 1000 records.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Legacy OHLCV candles scoped to one pair.
- Pass a pair address when you want market-specific candles from one liquidity venue rather than token-level aggregation.
- Use
time_from,time_to, andtypeto define the candle window and resolution. - Pair candles are useful when DEX-specific pricing matters, especially for fragmented liquidity or venue analysis.
- Choose the V3 pair endpoint when you need second-level intervals or count-based retrieval.
- Standard
- Lite
- Starter
- Premium
- Business
- Enterprise
All chains ⛓️ ✨
Compute Unit ⚙️
- This endpoint consumes
35 CUper request.
Use Cases 💡
- Chart a specific pool or pair instead of blended token pricing.
- Compare price action across different pools for the same asset.
- Monitor venue-specific dislocations, slippage risk, or routing quality.
- Build analytics for LPs, market makers, and DEX-specific trading workflows.
How to Use 🛠️
- Set
x-chainfor the target network. - Pass the pair address in
address. - Define the time window with
time_fromandtime_to. - Choose a legacy candle interval in
type.
Best Practices ✅
- Use pair candles when the token trades across many venues and you need one market's exact behavior.
- Keep pair identity stable in your app so users know which venue they are looking at.
- Join pair OHLCV with pair-overview or liquidity data when execution conditions matter as much as price.