← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · DEX SCREENER PROFILES

DEX Screener Token Profiles: Null vs Zero - Handle Missing Fields Correctly

Token profiles carry descriptions, headers and links supplied by projects. In the API, several of those are nullable, and a missing link is not evidence of anything.

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

Short answer

DEX Screener's token-profile endpoints return TokenProfile objects with url, chainId, tokenAddress and icon, plus header, description and links, which the reference marks as nullable (links items also have nullable type and label). A null description or empty links list means the project supplied none, not that the token is inactive or unsafe; a present description is a claim, not verification. Community-takeover objects add a claimDate. Store nulls as null and never score tokens on profile completeness alone.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
headerNo header image supplied—
descriptionNo description suppliedEmpty string: supplied but blank
linksNo links suppliedEmpty array: none listed
links[].type / labelUnlabelled link—
claimDate (takeovers)Should be present—
Dex Screener Profiles: how to read each fieldDex Screener Profiles: how to read each field: header — No header image supplied; description — No description supplied; links — No links supplied; links[].type / label — Unlabelled link; claimDate (takeovers) — Should be present.headerNo header image supplieddescriptionNo description suppliedlinksNo links suppliedlinks[].type / labelUnlabelled linkclaimDate (takeovers)Should be present
Dex Screener Profiles: missing vs zero, field by field. Original ChartsPod editorial graphic.

Review DEX Screener Token Profiles with bar replay before using it live.

Open ChartsPod replay

Handling policy

Policy for this sourcePolicy for this source: Null profile fields = not supplied; Never treat completeness as safety; Verify links on official channels; Keep chainId + tokenAddress as key; Refresh profiles slowly (cache).POLICY FOR THIS SOURCENull profile fields = not suppliedNever treat completeness as safetyVerify links on official channelsKeep chainId + tokenAddress as keyRefresh profiles slowly (cache)
Apply this policy to every dex screener profiles request. Original ChartsPod editorial graphic.

Illustrative: a scoring script gave +1 point per non-null profile field. Impostor tokens with copied descriptions and links scored higher than a legitimate token with a minimal profile. Profile fields are claims; identity checks must use the address.

Conclusion

Related: DEX Screener Token Listings: First Pool, First Trade and Metadata, DEX API Rate Limits: Separate Pair Requests From Profile Requests.

Store nulls as null and never score tokens on profile completeness alone.

Put DEX Screener Token Profiles next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Questions readers ask

What does a null description mean?

The project didn't supply one.

Do complete profiles mean safety?

No; they're claims.

Which fields are nullable?

header, description, links and link type/label, per the reference.

Sources and methodology

Field definitions come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a schema was not visible in the documentation, this guide says so and describes defensive handling rather than asserting field behaviour.

  1. DEX Screener: API reference — token and pair endpoints, nullable fields, rate limits.
  2. DEX Screener: Token listing — listing after first liquidity and trade; supply inputs.

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.