← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · NEW POOLS TIMING

GeckoTerminal New-Pool Data: Event Time vs Retrieval Time

The new-pools endpoint lists pools created in the past 48 hours. Each has a creation timestamp; the list itself is a cached snapshot.

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, cached every 30 seconds (paid) or 60 seconds (demo). pool_created_at is the event time; your retrieval time is not included. Pools drop off after 48 hours, so to track them longer, store them. Time-based metrics (m5 to h24 volume and transactions) are rolling windows ending at the cache time.

Which times the data carries

TimePresent?Meaning
pool_created_atYesEvent time (UTC)
Retrieval timeNoRecord it
Window metrics (m5–h24)Implicit endCache time
Inclusion window48 hoursThen drops off

See GeckoTerminal New-Pool Data on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

What to record yourself

Field to storeWhy
retrieved_atWindow end reference
pool_created_atPool age
addressIdentity
transactions.h1Early activity
first_seenYour detection time
New Pools: a stored recordNew Pools: a stored record: retrieved_at — Window end reference; pool_created_at — Pool age; address — Identity; transactions.h1 — Early activity; first_seen — Your detection time.retrieved_atWindow end referencepool_created_atPool ageaddressIdentitytransactions.h1Early activityfirst_seenYour detection time
Every new pools row carries its own clock. Original ChartsPod editorial graphic.

Example

New Pools: event vs retrieval (illustrative)New Pools: event vs retrieval (illustrative): 12:00: Pool created; 12:00:40: Appears in cache; 12:01: Your poll detects it; +48h: Drops from endpoint.12:00Pool created12:00:40Appears in cache12:01Your poll detects it+48hDrops from endpoint
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: a pool created at 12:00:00 appears in your 12:01 poll; its h1 transaction count covers only one minute of history, not an hour.

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

Time-based metrics (m5 to h24 volume and transactions) are rolling windows ending at the cache time.

Test GeckoTerminal New-Pool Data on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Questions readers ask

What counts as a new pool?

Created within the past 48 hours.

Is pool_created_at the event time?

Yes.

Why do pools disappear?

They age out after 48 hours.

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: New pools by network — pools created within past 48 hours; pool_created_at; cache 30 s / 60 s.

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.