← THE CHARTSPOD LEDGEROPEN TERMINAL →
API · DEX SCREENER FIELDS

DEX Screener Pair Data: Null vs Zero - Handle Missing Fields Correctly

DEX Screener's pair data marks some fields as nullable and others as always present. Your code should know which is which.

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

Short answer

In DEX Screener's published Pair schema, txns (buys and sells per window), volume and priceNative are not nullable, while priceUsd, priceChange, liquidity (and liquidity.usd), fdv, marketCap and pairCreatedAt can be null. A zero in txns or volume is a measured zero; a null in liquidity.usd or fdv means the value is unavailable. Keep nulls as nulls, never coerce to zero, and decide per field whether to exclude, flag or retry.

Field nullability

FieldNullable (per schema)Zero means
txns.buys / sellsNoNo trades in window
volumeNoNo volume in window
priceNativeNo—
priceUsdYes—
priceChangeYesNo change
liquidity / liquidity.usdYes—
fdv / marketCapYes—
pairCreatedAtYes—
Handling in codeHandling in code. Left, Wrong: liquidity = data.liquidity?.usd || 0; Ranks unknown pools last; Averages biased down. Right, Right: Keep null; Flag 'liquidity unknown'; Exclude from averages or retry.WRONGliquidity = data.liquidity?.usd || 0Ranks unknown pools lastAverages biased downRIGHTKeep nullFlag 'liquidity unknown'Exclude from averages or retry
Coercing null to zero is the most common bug. Original ChartsPod editorial graphic.

Test DEX Screener Pair Data on a perpetual chart; no account is needed to chart.

Launch ChartsPod

A field policy

DEX Screener field policyDEX Screener field policy: priceUsd null → use priceNative + quote USD, or flag; liquidity.usd null → flag, exclude from depth ranking; fdv/marketCap null → don't rank by valuation; pairCreatedAt null → age unknown; Log null counts per run.DEX SCREENER FIELD POLICYpriceUsd null → use priceNative + quote USD, or flagliquidity.usd null → flag, exclude from depth rankingfdv/marketCap null → don't rank by valuationpairCreatedAt null → age unknownLog null counts per run
Write it once, apply everywhere. Original ChartsPod editorial graphic.

General principles: Missing Crypto API Data: Null, Zero and Empty Arrays Mean Different Things. Endpoint usage: DEX Screener API: Find Token Pools by Chain and Contract Address.

Example: a biased average

Illustrative: a dashboard averages liquidity across 50 new pairs. Twelve have liquidity.usd null. Coercing to zero shows an average of $76,000; excluding nulls gives $100,000 for the 38 known pairs, and the dashboard notes '12 unknown'. The second version is honest about what it knows.

Conclusion

Follow DEX Screener's schema: keep nullable fields as null, treat zeros as measured, and apply a per-field policy.

See DEX Screener Pair Data on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

Questions readers ask

Which DEX Screener fields can be null?

Per the Pair schema: priceUsd, priceChange, liquidity (and usd), fdv, marketCap, pairCreatedAt, among others.

Is zero volume possible?

Yes; it means no volume in that window.

Should I convert null liquidity to zero?

No; flag it as unknown.

Sources and methodology

Field nullability comes from DEX Screener's published Pair schema as read on 17 October 2026; other endpoints may differ.

  1. DEX Screener: API reference — token and pair endpoints, nullable fields, rate limits.

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.