← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · GECKOTERMINAL POOL TRADES HISTORY

GeckoTerminal Pool Trade Data: History Limits - Avoid Silent Gaps

The pool-trades endpoint returns the last 300 trades in 24 hours by default. On busy pools that's minutes, not a day — and earlier trades are simply absent.

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

Short answer

CoinGecko's trades-by-pool endpoint returns, by default, the last 300 trades from the past 24 hours; higher plans can set trading_period (1d, 7d, 30d), per_page up to 300 and page with a cursor. It's cacheless. On active pools, 300 trades may span a few minutes, so analyses of 'the last day' are silently truncated. Poll frequently, deduplicate by tx_hash, check the time span covered and use cursor paging where available.

Documented limits

LimitValueEffect
DefaultLast 300 trades, 24 hTruncation
trading_period1d / 7d / 30d (Analyst+)Longer windows
Cursor pagingAnalyst+Full coverage
CacheNoneReal time

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

Open a ChartsPod workspace

Where silent gaps come from

  • 300-trade cap on busy pools
  • Overlapping polls not deduplicated
  • Span not checked
  • Plan features assumed
Geckoterminal Pool Trades: gap-safe collectionGeckoterminal Pool Trades: gap-safe collection. Steps: 1. Poll — Frequently; 2. Dedupe — tx_hash; 3. Check span — Oldest vs newest; 4. Page — Cursor if available; 5. Log — Truncation1PollFrequently2Dedupetx_hash3Check spanOldest vs newest4PageCursor if available5LogTruncation
Make every gap explicit. Original ChartsPod editorial graphic.

Example

Geckoterminal Pool Trades: a silent gap (illustrative)Geckoterminal Pool Trades: a silent gap (illustrative): REQUEST: Default; RETURNED: 300 trades; SPAN: 11 minutes; ANALYSIS: '24h buy volume'.REQUESTDefaultRETURNED300 tradesSPAN11 minutesANALYSIS'24h buy volume'
Nothing in the data said it was missing. Original ChartsPod editorial graphic.

Illustrative: a '24-hour buy volume' figure came from 300 trades spanning 11 minutes on an active pool.

Related: GeckoTerminal Pool Trade Data: Event Time vs Retrieval Time, GeckoTerminal for Large-Trade Analysis: What It Can and Cannot Cover.

Poll frequently, deduplicate by tx_hash, check the time span covered and use cursor paging where available.

Review GeckoTerminal Pool Trade Data with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

How many trades does the endpoint return?

By default the last 300 in 24 hours.

Can I get more?

With trading_period and cursor on higher plans.

How do I detect truncation?

Check the time span covered.

Sources and methodology

Limits come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a limit isn't documented, this guide says so. Examples are illustrative.

  1. CoinGecko API: Trades by pool — last 300 trades in 24 h by default; trading_period and cursor on Analyst plan+.

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.