get
https://public-api.birdeye.so/defi/v3/ohlcv/pair
Retrieve candlestick data in OHLCV format of a specified pair. Maximum 5000 records. Compared to v1: Added 1s, 15s, and 30s intervals and no candle padding
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Extended pair OHLCV with finer intervals and count mode.
- V3 pair candles support
1s,15s, and30sintervals in addition to the legacy set. - Empty candles are not returned unless
padding=true. - When
mode=count, provide eithertime_fromortime_to, but not both;count_limitcan go up to5000. - Data retention for the newest intervals is shorter:
1sup to 2 weeks,15sand30sup to 3 months. - Use pair-scoped candles when you need one venue's precise market behavior instead of token-level aggregation.
- Standard
- Lite
- Starter
- Premium
- Business
- Enterprise
All chains ⛓️ ✨
Compute Unit ⚙️
- CU is dynamic:
60 CUfor up to1000candles,90 CUfor up to2000, and120 CUfor up to5000.
Use Cases 💡
- Inspect launch-time candles for a single pair with second-level precision.
- Compare venues for the same asset and detect price fragmentation or temporary dislocations.
- Backtest pool-specific execution logic, routing, or market-making behavior.
- Build pair-native charts for traders who care about one exact market, not blended token pricing.
How to Use 🛠️
- Set
x-chainto one of the supported V3 networks. - Pass the pair address plus
type. - Use
mode=rangefor bounded chart windows, ormode=countfor a rolling candle count. - Enable
paddingonly when your chart explicitly requires contiguous empty buckets.
Best Practices ✅
- Use pair V3 for launch forensics and short-window analysis where venue specificity matters.
- Keep your venue labeling explicit in UI so users do not confuse pair candles with aggregate token candles.
- Pair these candles with liquidity data when diagnosing sudden wick behavior or temporary price distortions.
