DATA · GECKOTERMINAL POOL OHLCV

GeckoTerminal Pool OHLCV: Null vs Zero - Handle Missing Fields Correctly

Pool candles exist only when the pool trades. A missing candle, a null field and a zero-volume candle can all appear, and they mean different things.

Short answer

CoinGecko's onchain pool OHLCV returns candles for one pool and token side. CoinGecko notes some OHLCV fields can be null. Treat a missing interval (no candle returned) as 'no swaps in that interval', a null field within a candle as 'value unavailable', and a zero volume as a measured zero. Never forward-fill missing intervals for backtests; record them as no-trade periods, and keep the pool address, token side and interval with the series.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Missing intervalNo candle: no swaps—
Null OHLC fieldValue unavailable—
VolumeUnavailableZero: no volume
Pool / side metadataMust be stored by you—
Geckoterminal Pool Ohlcv: how to read each fieldGeckoterminal Pool Ohlcv: how to read each field: Missing interval — No candle: no swaps; Null OHLC field — Value unavailable; Volume — Unavailable; Pool / side metadata — Must be stored by you.Missing intervalNo candle: no swapsNull OHLC fieldValue unavailableVolumeUnavailablePool / side metadataMust be stored by you
Geckoterminal Pool Ohlcv: missing vs zero, field by field. Original ChartsPod editorial graphic.

Put GeckoTerminal Pool OHLCV next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Handling policy

Policy for this sourcePolicy for this source: Missing interval = no-trade period; Null field = unknown, exclude; No forward-fill in backtests; Store pool, side, interval; Compare with explorer when gaps matter.POLICY FOR THIS SOURCEMissing interval = no-trade periodNull field = unknown, excludeNo forward-fill in backtestsStore pool, side, intervalCompare with explorer when gaps matter
Apply this policy to every geckoterminal pool ohlcv request. Original ChartsPod editorial graphic.

Illustrative: a pool returns 1,440 one-minute candles for a day minus 310 missing intervals. Forward-filling those creates 310 flat candles that look tradable; in reality nobody traded, and an order would have moved price.

Conclusion

Related: Why a DEX Token Chart Has Gaps: No Trades vs Missing Data, GeckoTerminal OHLCV: Choose Pool, Token Side and Candle Interval.

Never forward-fill missing intervals for backtests; record them as no-trade periods, and keep the pool address, token side and interval with the series.

Review GeckoTerminal Pool OHLCV with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

Why are candles missing from pool OHLCV?

Usually no swaps in those intervals.

Can OHLCV fields be null?

CoinGecko notes some can be.

Should I forward-fill?

Not for backtests.

Sources and methodology

Field definitions come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a schema was not visible in the documentation, this guide says so and describes defensive handling rather than asserting field behaviour.

  1. CoinGecko onchain API: Pool OHLCV by pool address — pool candles.
  2. CoinGecko API: Onchain OHLCV WebSocket — pool candles, base/quote selection, nullable fields.

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.