← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · TOKEN OHLCV TIMING

GeckoTerminal Token OHLCV: Event Time vs Retrieval Time

CoinGecko's token OHLCV takes candles from the token's most liquid pool. Which pool that is can change, and the response is cached — two timing issues in one endpoint.

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

Short answer

CoinGecko's token OHLCV endpoint builds candles from the token's most liquid pool, returns [timestamp, open, high, low, close, volume] and is cached for about 10 seconds. If the most liquid pool changes (after a migration, say), the series source changes too. Store your retrieval time and, separately, check which pool was most liquid at that time via the top-pools endpoint. Empty intervals are skipped unless include_empty_intervals is set.

Which times the data carries

TimePresent?Meaning
Candle timestampYesInterval time (verify start/end)
Source poolNot in candleMost liquid pool at the time
Retrieval timeNoRecord it
Cache≈ 10 sLatest candle may lag

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

Open markets in ChartsPod

What to record yourself

Field to storeWhy
retrieved_atCache awareness
source pool (from top pools)Which pool fed the candles
timeframe + aggregateCandle size
include_empty_intervalsGap semantics
include_inactive_sourceInactive-pool handling
Token Ohlcv: a stored recordToken Ohlcv: a stored record: retrieved_at — Cache awareness; source pool (from top pools) — Which pool fed the candles; timeframe + aggregate — Candle size; include_empty_intervals — Gap semantics; include_inactive_source — Inactive-pool handling.retrieved_atCache awarenesssource pool (from top pools)Which pool fed the candlestimeframe + aggregateCandle sizeinclude_empty_intervalsGap semanticsinclude_inactive_sourceInactive-pool handling
Every token ohlcv row carries its own clock. Original ChartsPod editorial graphic.

Example

Token Ohlcv: event vs retrieval (illustrative)Token Ohlcv: event vs retrieval (illustrative): DAY 1: Pool A most liquid; DAY 2 03:00: Liquidity migrates to pool B; DAY 2: Token candles now from B; SERIES: Source switch inside history.DAY 1Pool A most liquidDAY 2 03:00Liquidity migrates to pool BDAY 2Token candles now from BSERIESSource switch inside history
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: a token's candle series shows a sudden 4% gap at 03:00 with no trading reason. The most liquid pool changed, and the two pools were priced slightly differently.

Related: GeckoTerminal Pool OHLCV: Event Time vs Retrieval Time, GeckoTerminal Top-Pool Data: Event Time vs Retrieval Time.

Empty intervals are skipped unless include_empty_intervals is set.

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

Try it in ChartsPod

Questions readers ask

Which pool does token OHLCV use?

The most liquid pool.

How fresh is it?

Cached about every 10 seconds.

Why a sudden gap?

The source pool may have changed.

Sources and methodology

Field definitions come from DEX Screener's API reference and CoinGecko's onchain API documentation, read 17 October 2026. Where a schema doesn't document a timestamp, this guide says so and recommends recording retrieval time yourself.

  1. CoinGecko API: Token OHLCV by token address — most liquid pool; cache 10 s; include_inactive_source; Analyst plan and above.
  2. CoinGecko API: Top pools by token address — pool_created_at; cache 30 s paid / 60 s demo; 20 pools per page; sort options.

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.