← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · GECKOTERMINAL POOL TRADES

GeckoTerminal Pool Trade Data: Null vs Zero - Handle Missing Fields Correctly

Pool trade lists show recent swaps. An empty list, a missing field and a zero amount are three different answers.

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

Short answer

CoinGecko's trades-by-pool-address endpoint returns recent swaps for a pool (and a time-range variant exists). An empty list for a window means no swaps were recorded in it; a null field within a trade means that value is unavailable; a zero amount should be treated as suspicious data rather than a real trade. Store trades with transaction hash and timestamp as keys, deduplicate across pages, and don't infer volume from a truncated list.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
Trade list—Empty: no swaps in window
USD value of a tradeUnavailableZero: suspicious; check
Tx hashRequired as key—
TimestampRequired—
Geckoterminal Pool Trades: how to read each fieldGeckoterminal Pool Trades: how to read each field: Trade list — Empty: no swaps in window; USD value of a trade — Unavailable; Tx hash — Required as key; Timestamp — Required.Trade listEmpty: no swaps in windowUSD value of a tradeUnavailableTx hashRequired as keyTimestampRequired
Geckoterminal Pool Trades: missing vs zero, field by field. Original ChartsPod editorial graphic.

Review GeckoTerminal Pool Trade Data with bar replay before using it live.

Open ChartsPod replay

Handling policy

Policy for this sourcePolicy for this source: Key by tx hash + timestamp; Deduplicate across pages; Empty list = no swaps; Zero amounts: verify on explorer; Don't sum truncated lists as volume.POLICY FOR THIS SOURCEKey by tx hash + timestampDeduplicate across pagesEmpty list = no swapsZero amounts: verify on explorerDon't sum truncated lists as volume
Apply this policy to every geckoterminal pool trades request. Original ChartsPod editorial graphic.

Illustrative: summing the last 300 trades as '24h volume' underestimated volume on a busy pool where 300 trades covered only 40 minutes. Use the pool's volume fields for totals and trades for detail.

Conclusion

Related: High DEX Volume With Few Makers: Questions to Ask Before Trading, DEX Screener Transactions: Buy Counts, Sell Counts and Unique Makers.

Store trades with transaction hash and timestamp as keys, deduplicate across pages, and don't infer volume from a truncated list.

Put GeckoTerminal Pool Trade Data next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Questions readers ask

What does an empty trade list mean?

No swaps recorded in that window.

Can I compute volume from trades?

Only if you have every trade for the period.

What key should I use?

Transaction hash plus timestamp.

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. CoinGecko onchain API: Trades by pool address — recent swaps for a pool.

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.