← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · GECKOTERMINAL OHLCV TIMING

GeckoTerminal Pool OHLCV: Event Time vs Retrieval Time

Pool OHLCV candles carry their own timestamps, but the API caches responses and skips empty intervals by default. Both affect what 'latest' means.

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

Short answer

CoinGecko's pool OHLCV endpoint returns candles as [timestamp, open, high, low, close, volume] with timeframes from second to day and aggregates (e.g. 1/5/15 minutes). Intervals with no swaps are skipped unless include_empty_intervals is true, in which case OHLC repeat the previous close and volume is 0. Responses are cached (10 seconds on paid plans, 60 on demo). The docs don't state whether the timestamp is the interval start or end — verify against known trades — and store your retrieval time.

Which times the data carries

TimePresent?Meaning
Candle timestampYesInterval start or end: verify
Retrieval timeNoRecord it
Cache ageUp to 10 s / 60 sPlan-dependent
Empty intervalsSkipped by defaultOption fills with volume 0

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

Open a ChartsPod workspace

What to record yourself

Field to storeWhy
retrieved_atCache-age awareness
timeframe + aggregateCandle size
include_empty_intervalsGap semantics
currency / tokenPrice orientation
before_timestampPagination point
Geckoterminal Ohlcv: a stored recordGeckoterminal Ohlcv: a stored record: retrieved_at — Cache-age awareness; timeframe + aggregate — Candle size; include_empty_intervals — Gap semantics; currency / token — Price orientation; before_timestamp — Pagination point.retrieved_atCache-age awarenesstimeframe + aggregateCandle sizeinclude_empty_intervalsGap semanticscurrency / tokenPrice orientationbefore_timestampPagination point
Every geckoterminal ohlcv row carries its own clock. Original ChartsPod editorial graphic.

Example

Geckoterminal Ohlcv: event vs retrieval (illustrative)Geckoterminal Ohlcv: event vs retrieval (illustrative): 12:00:00: Last swap; 12:00:40: Request returns cached data; CACHE: Up to 60 s old (demo); 12:01:10: Next request: new candle.12:00:00Last swap12:00:40Request returns cached dataCACHEUp to 60 s old (demo)12:01:10Next request: new candle
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: on a demo key, a 'latest' 1-minute candle can be up to a minute stale. With include_empty_intervals off, a quiet pool's series also has holes that look like missing data.

Related: GeckoTerminal for Intraday Historical Data: What It Can and Cannot Cover, DEX Candle Gaps: How to Read the Number Before a Swap.

The docs don't state whether the timestamp is the interval start or end — verify against known trades — and store your retrieval time.

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

Open ChartsPod replay

Questions readers ask

What does the OHLCV timestamp mark?

The docs don't say start or end; verify it.

How fresh are responses?

Cached 10 s on paid plans, 60 s on demo.

What about intervals with no swaps?

Skipped unless include_empty_intervals is true.

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: Pool OHLCV by pool address — timeframe/aggregate, before_timestamp, limit ≤ 1000, include_empty_intervals, cache 10 s paid / 60 s demo.

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.