← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · TOKEN-POOL DATA TIMING

DEX Screener Token-Pool Data: Event Time vs Retrieval Time

Token-pool lists change as pools are created and liquidity moves. Without your own retrieval timestamp, you can't tell which list was true when.

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

Short answer

DEX Screener's token-pairs data returns the pools for a token at request time; each pool has pairCreatedAt (nullable) but no retrieval time. Pool rankings by liquidity change as liquidity moves, so a stored list without retrieved_at can't be compared over time. Record the retrieval time, keep each pool's pairAddress and liquidity, and treat new pools appearing between fetches as events dated by pairCreatedAt when present.

Which times the data carries

TimePresent?Meaning
pairCreatedAtYes (nullable)Pool creation
Retrieval timeNoRecord it
Liquidity as ofImplicitResponse time
Pool removalNot signalledAbsence in a later fetch

Put DEX Screener Token-Pool Data next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

What to record yourself

Field to storeWhy
retrieved_atOrders snapshots
pairAddressPool identity
liquidity.usdRanking input (nullable)
pairCreatedAtNew-pool dating
dexIdVenue
Token-Pool Data: a stored recordToken-Pool Data: a stored record: retrieved_at — Orders snapshots; pairAddress — Pool identity; liquidity.usd — Ranking input (nullable); pairCreatedAt — New-pool dating; dexId — Venue.retrieved_atOrders snapshotspairAddressPool identityliquidity.usdRanking input (nullable)pairCreatedAtNew-pool datingdexIdVenue
Every token-pool data row carries its own clock. Original ChartsPod editorial graphic.

Example

Token-Pool Data: event vs retrieval (illustrative)Token-Pool Data: event vs retrieval (illustrative): DAY 1 10:00: 3 pools; A largest; DAY 2 10:00: 4 pools; D new, largest; D created: pairCreatedAt: Day 1 21:14; READ: Migration overnight.DAY 1 10:003 pools; A largestDAY 2 10:004 pools; D new, largestD createdpairCreatedAt: Day 1 21:14READMigration overnight
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: a new pool D appears in the second fetch with the most liquidity; its pairCreatedAt dates the migration to 21:14 the previous evening.

Related: DEX Screener Pair Data: Event Time vs Retrieval Time, DEX Pool Migration: How to Read the Number Before a Swap.

Record the retrieval time, keep each pool's pairAddress and liquidity, and treat new pools appearing between fetches as events dated by pairCreatedAt when present.

Review DEX Screener Token-Pool Data with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

How do I date a new pool?

pairCreatedAt, when present.

Does the response say when it was fetched?

No; store retrieval time.

How do I detect removed pools?

They're absent from a later fetch.

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. DEX Screener API reference — documented schemas: pairCreatedAt nullable; no updatedAt or retrieval-time field; 60 requests/min on several endpoints.

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.