← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · GECKOTERMINAL NEW POOLS HISTORY

GeckoTerminal New-Pool Data: History Limits - Avoid Silent Gaps

The new-pools endpoint only covers pools created in the past 48 hours. Pools older than that drop off — so any longer study needs your own records.

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

Short answer

CoinGecko's new-pools-by-network endpoint includes pools created within the past 48 hours, 20 per page (beyond 10 pages needs a higher plan), cached 30–60 seconds. On busy networks, more than 200 pools can be created in 48 hours, so lower-tier paging can miss some. Poll often enough to catch every pool, store first-seen time with pool_created_at, and log pages that hit the limit.

Documented limits

LimitValueEffect
WindowPast 48 hoursOlder pools drop off
Pools per page20Pagination
Pages without Analyst≤ 10≤ 200 visible
Cache30 s / 60 sDetection delay

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

Open a ChartsPod workspace

Where silent gaps come from

  • Pools aging out before you saw them
  • Paging limit on busy networks
  • Missing first-seen times
  • Failed polls
Geckoterminal New Pools: gap-safe collectionGeckoterminal New Pools: gap-safe collection. Steps: 1. Poll — Frequently; 2. Page — Until empty or limit; 3. Store — pool_created_at + first seen; 4. Log — Limit hits / failures; 5. Archive — Beyond 48 h1PollFrequently2PageUntil empty orlimit3Storepool_created_at +first seen4LogLimit hits /failures5ArchiveBeyond 48 h
Make every gap explicit. Original ChartsPod editorial graphic.

Example

Geckoterminal New Pools: a silent gap (illustrative)Geckoterminal New Pools: a silent gap (illustrative): NETWORK: 350 pools in 48 h; VISIBLE: 200 (paging limit); POLLING: Every 6 h; RESULT: Some pools never seen.NETWORK350 pools in 48 hVISIBLE200 (paging limit)POLLINGEvery 6 hRESULTSome pools never seen
Nothing in the data said it was missing. Original ChartsPod editorial graphic.

Illustrative: on a busy network, a study of new pools missed about 40% because of the paging limit and infrequent polling.

Related: GeckoTerminal New-Pool Data: Event Time vs Retrieval Time, DEX New-Pool Filters: How to Read the Number Before a Swap.

Poll often enough to catch every pool, store first-seen time with pool_created_at, and log pages that hit the limit.

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

Open ChartsPod replay

Questions readers ask

How far back does the new-pools endpoint go?

Pools created in the past 48 hours.

Can I miss pools?

Yes, with paging limits or slow polling.

How do I keep history?

Store your own records.

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: New pools by network — pools created within 48 h; 20 per page.

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.