← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · TOKEN PROFILES TIMING

DEX Screener Token Profiles: Event Time vs Retrieval Time

DEX Screener's token-profile endpoints list the latest profiles and recent updates, without a timestamp per profile in the documented schema.

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

Short answer

The token-profiles endpoints (latest and recent-updates) return url, chainId, tokenAddress, icon, header, description and links; the documented schema has no time field. So you can't tell from the response when a profile was created or changed. Poll at a known interval, store retrieved_at, and detect changes by comparing fields between snapshots. Header, description and links can be null.

Which times the data carries

TimePresent?Meaning
Profile creation timeNot in schemaInfer from first seen
Update timeNot in schemaInfer from changes
Retrieval timeNoRecord it
Community takeover claimDateYes (separate endpoint)Takeover date

Check DEX Screener Token Profiles against a live market before relying on it.

Try it in ChartsPod

What to record yourself

Field to storeWhy
retrieved_atFirst-seen dating
tokenAddress + chainIdIdentity
linksChange detection (nullable)
descriptionChange detection (nullable)
poll intervalDating precision
Token Profiles: a stored recordToken Profiles: a stored record: retrieved_at — First-seen dating; tokenAddress + chainId — Identity; links — Change detection (nullable); description — Change detection (nullable); poll interval — Dating precision.retrieved_atFirst-seen datingtokenAddress + chainIdIdentitylinksChange detection (nullable)descriptionChange detection (nullable)poll intervalDating precision
Every token profiles row carries its own clock. Original ChartsPod editorial graphic.

Example

Token Profiles: event vs retrieval (illustrative)Token Profiles: event vs retrieval (illustrative): 10:00: Poll: profile absent; 10:05: Poll: profile present; DATE: First seen ≤ 10:05; PRECISION: ± poll interval.10:00Poll: profile absent10:05Poll: profile presentDATEFirst seen ≤ 10:05PRECISION± poll interval
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: polling every 5 minutes, a profile first appears at 10:05, so it was published between 10:00 and 10:05 — the best dating available without a timestamp field.

Related: DEX Token Social Links: How to Read the Number Before a Swap, DEX Screener Boost Data: Event Time vs Retrieval Time.

Header, description and links can be null.

Compare DEX Screener Token Profiles across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

Questions readers ask

Do token profiles have timestamps?

Not in the documented schema.

How can I date a profile?

First-seen time from regular polling.

Which endpoint has a date?

Community takeovers include claimDate.

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.