← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · DEX SCREENER SEARCH

DEX Screener Search Results: Null vs Zero - Handle Missing Fields Correctly

Search results mix exact matches with loose ones and can return partial pair data. Missing fields in search results need different handling from missing results.

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

Short answer

DEX Screener's search endpoint (/latest/dex/search) takes free text and returns matching pairs. Its response schema is defined in the external OpenAPI spec rather than shown on the reference page, so code defensively: an empty result set means no matches (try the token address instead of a name), while null fields within a returned pair follow the Pair schema's nullability (priceUsd, liquidity, fdv, marketCap, pairCreatedAt). Never infer a token's identity from a search hit without checking its address.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Result list—Empty: no text matches
Pair priceUsd / liquidityUnknown for that pair—
Pair txns / volume—No activity
baseToken.addressShould be present; if missing, discard—
Dex Screener Search: how to read each fieldDex Screener Search: how to read each field: Result list — Empty: no text matches; Pair priceUsd / liquidity — Unknown for that pair; Pair txns / volume — No activity; baseToken.address — Should be present; if missing, discard.Result listEmpty: no text matchesPair priceUsd / liquidityUnknown for that pairPair txns / volumeNo activitybaseToken.addressShould be present; if missing, discard
Dex Screener Search: missing vs zero, field by field. Original ChartsPod editorial graphic.

Test DEX Screener Search Results on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Handling policy

Policy for this sourcePolicy for this source: Empty results: retry with token address; Discard results without an address; Apply Pair-schema null rules; Never pick a token from search alone; Log query text with results.POLICY FOR THIS SOURCEEmpty results: retry with token addressDiscard results without an addressApply Pair-schema null rulesNever pick a token from search aloneLog query text with results
Apply this policy to every dex screener search request. Original ChartsPod editorial graphic.

Illustrative: searching a ticker returns 30 pairs, 8 with null liquidity. Sorting by liquidity with nulls as zero pushes those 8 down, including one that is the real token's newest pool. Filtering by the official token address first avoids the problem entirely.

Conclusion

Related: DEX Token Search by Ticker: Why Contract Addresses Are Safer, DEX Screener Search: Token Address vs Pair Address Explained.

Never infer a token's identity from a search hit without checking its address.

See DEX Screener Search Results on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

Questions readers ask

What does an empty search result mean?

No matches for the text; try an address.

Can search results have null prices?

Yes, per pair-level nullability.

Is search safe for identification?

No; verify addresses.

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.