← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · MULTI-EXCHANGE PRICES

Multi-Exchange Price Data: Null vs Zero - Handle Missing Fields Correctly

Combining prices from several exchanges multiplies missing-data cases: one venue down, one symbol delisted, one candle late. Each needs a rule.

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

Short answer

A multi-exchange price table should distinguish a venue that returned no price (unknown) from a venue whose market had no trades (last price unchanged, volume 0) and from a venue that doesn't list the pair (not applicable). Averages and spreads should use only venues with fresh data, with a staleness limit. Record each venue's timestamp; a price 30 seconds old is not comparable with a live one during volatility.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Venue request failedUnknown—
Pair not listedNot applicable—
No trades in bar—Volume 0, price carried
Stale timestampExclude beyond limit—
DelistedNot applicable from date—
Multi-Exchange Prices: how to read each fieldMulti-Exchange Prices: how to read each field: Venue request failed — Unknown; Pair not listed — Not applicable; No trades in bar — Volume 0, price carried; Stale timestamp — Exclude beyond limit; Delisted — Not applicable from date.Venue request failedUnknownPair not listedNot applicableNo trades in barVolume 0, price carriedStale timestampExclude beyond limitDelistedNot applicable from date
Multi-Exchange Prices: missing vs zero, field by field. Original ChartsPod editorial graphic.

Put Multi-Exchange Price Data next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Handling policy

Policy for this sourcePolicy for this source: Per-venue timestamps; Staleness limit; Separate not-listed from failed; Average fresh venues only; Report venue count.POLICY FOR THIS SOURCEPer-venue timestampsStaleness limitSeparate not-listed from failedAverage fresh venues onlyReport venue count
Apply this policy to every multi-exchange prices request. Original ChartsPod editorial graphic.

Illustrative: an 'average price' across five venues drops 2% when one venue's feed fails and is counted as 0. With a null-aware average of four venues, nothing moved.

Conclusion

Related: GeckoTerminal for Cross-Exchange Price Comparison: What It Can and Cannot Cover, Crypto Screener Snapshots: Null vs Zero - Handle Missing Fields Correctly.

Record each venue's timestamp; a price 30 seconds old is not comparable with a live one during volatility.

Review Multi-Exchange Price Data with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

How should failed venues be handled?

As unknown, excluded from averages.

Is a pair not listed the same as missing?

No; it's not applicable.

Why timestamps?

Stale prices distort comparisons.

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. Binance: USD-M Futures market data API — trades, depth, funding and open interest.
  2. ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.

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.