← THE CHARTSPOD LEDGEROPEN TERMINAL →
API · GECKOTERMINAL OHLCV

GeckoTerminal OHLCV: Choose Pool, Token Side and Candle Interval

A pool OHLCV request has three choices that change the result: which pool, which token side and which interval.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

To request GeckoTerminal (CoinGecko onchain) OHLCV, first choose the pool, normally the deepest pool for the token in a suitable quote; then choose the token side, because candles can be built for the base or quote token of the pool; then choose the interval and limit. CoinGecko documents that some OHLCV fields can be null and that pool candles depend on swaps occurring. Record pool address, side and interval with the data.

Three choices

ChoiceOptionsEffect
PoolAny pool for the tokenDifferent liquidity, gaps, prices
Token sideBase or quoteWhich token's price the candle shows
IntervalMinute, hour, day (per docs)Resolution vs history length
OHLCV request planOHLCV request plan. Steps: 1. Find pools — Top pools by token address; 2. Pick pool — Liquidity, quote; 3. Pick side — Base or quote token; 4. Pick interval — And limit; 5. Store metadata — Pool, side, interval1Find poolsTop pools by tokenaddress2Pick poolLiquidity, quote3Pick sideBase or quote token4Pick intervalAnd limit5Store metadataPool, side,interval
Without metadata the candles are ambiguous. Original ChartsPod editorial graphic.

Compare GeckoTerminal OHLCV across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

Getting the side right

If your token is the quote token in the pool (e.g. a USDC/TOKEN pool listed with USDC as base), requesting base-side candles returns USDC's price in TOKEN terms, the inverse of what you want. Check which side your token is on before requesting.

Base vs quote sideBase vs quote side. Left, Base side: Price of the pool's base token; In quote terms or USD; Default in many tools. Right, Quote side: Price of the quote token; Use when your token is quote; Avoids inverted charts.BASE SIDEPrice of the pool's base tokenIn quote terms or USDDefault in many toolsQUOTE SIDEPrice of the quote tokenUse when your token is quoteAvoids inverted charts
Pick the side that matches your token. Original ChartsPod editorial graphic.

Mistakes

Requesting a thin secondary pool because it appeared first; mixing intervals across pools in one dataset; forward-filling null candles. Each produces a dataset that does not represent the market.

OHLCV dataset rulesOHLCV dataset rules: One pool per series, recorded; Side recorded; Interval recorded; Nulls kept as gaps; Fetch time recorded.OHLCV DATASET RULESOne pool per series, recordedSide recordedInterval recordedNulls kept as gapsFetch time recorded
Metadata makes data reproducible. Original ChartsPod editorial graphic.

Example: an inverted series

Illustrative: a developer requests base-side candles for a USDC/TOKEN pool where USDC is listed as the base. The series shows USDC's price in TOKEN, falling whenever TOKEN rises. Switching to the quote side returns TOKEN's price as expected. Storing the side with the series makes the mistake obvious the next time anyone reads the data.

Conclusion

Related: GeckoTerminal OHLCV Charts: Base Token vs Quote Token Explained, Crypto OHLCV Timestamps: Candle Open Time vs Close Time, Missing Crypto API Data: Null, Zero and Empty Arrays Mean Different Things.

Choose pool, token side and interval deliberately, and store them with every OHLCV series.

Check GeckoTerminal OHLCV against a live market before relying on it.

Try it in ChartsPod

Questions readers ask

Which pool should I request candles for?

Usually the deepest pool for the token in your preferred quote.

What is the token side?

Whether candles describe the pool's base or quote token.

Why are some candles null?

No swaps occurred in that interval, or data is unavailable.

Sources and methodology

API behaviour comes from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's USD-M market data documentation as read on 17 October 2026. Code-level details are described conceptually; check current endpoint versions before building. Examples use illustrative values.

  1. CoinGecko API: Onchain OHLCV WebSocket — pool candles, base/quote selection, nullable fields.
  2. CoinGecko API: Top pools by token address — multiple pools per token.
  3. CoinGecko API changelog — onchain endpoint changes.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.