DATA · GECKOTERMINAL TOKEN OHLCV

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

Token OHLCV summarises a token rather than one pool. Missing data there can mean no trading in the pools used, or no pools included at all.

Short answer

CoinGecko's onchain API offers token OHLCV by token address as well as pool OHLCV. A token-level series depends on which pools feed it, so gaps can come from no trading in those pools or from the token's pools changing over time (for example after a migration). Check the documentation for how pools are selected, treat missing intervals as no data, nulls as unknown and zero volume as measured, and prefer pool OHLCV when you need to know exactly which market produced a candle.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Missing intervalNo data from included pools—
Null fieldsUnavailable—
VolumeUnavailableZero: no volume in included pools
Included poolsCheck docs—
Geckoterminal Token Ohlcv: how to read each fieldGeckoterminal Token Ohlcv: how to read each field: Missing interval — No data from included pools; Null fields — Unavailable; Volume — Unavailable; Included pools — Check docs.Missing intervalNo data from included poolsNull fieldsUnavailableVolumeUnavailableIncluded poolsCheck docs
Geckoterminal Token Ohlcv: missing vs zero, field by field. Original ChartsPod editorial graphic.

Test GeckoTerminal Token OHLCV on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Handling policy

Policy for this sourcePolicy for this source: Know how pools are selected; Missing = no data, not flat price; Use pool OHLCV for exact markets; Note migrations in the token's history; Store fetch time and parameters.POLICY FOR THIS SOURCEKnow how pools are selectedMissing = no data, not flat priceUse pool OHLCV for exact marketsNote migrations in the token's historyStore fetch time and parameters
Apply this policy to every geckoterminal token ohlcv request. Original ChartsPod editorial graphic.

Illustrative: after a token migrates to a new pool, a token-level series shows a gap and then resumes at a different level. Pool OHLCV for old and new pools makes clear where trading moved; the token series alone hides it.

Conclusion

Related: Solana Token Migration: Find the Active Pool and Preserve Context, GeckoTerminal OHLCV: Choose Pool, Token Side and Candle Interval.

Check the documentation for how pools are selected, treat missing intervals as no data, nulls as unknown and zero volume as measured, and prefer pool OHLCV when you need to know exactly which market produced a candle.

See GeckoTerminal Token OHLCV on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

Questions readers ask

Token OHLCV vs pool OHLCV?

Token-level summarises the token; pool-level is one market.

Why might token OHLCV have gaps?

No trading in included pools, or pool changes.

Which should I backtest on?

The pool you would trade.

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: Token OHLCV by token address — token-level candles.
  2. CoinGecko onchain API: Pool OHLCV by pool address — pool candles.

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.