Skip to main content
GET
Token - Trade Data (Multiple)

Batch trading-activity stats for multiple tokens.

  • Pass token addresses as a comma-separated list in list_address.
  • Maximum batch size is 20 token addresses per request.
  • Use frames to request the same set of timeframes for every token in the batch.
  • Returns trade, wallet, buy/sell, volume, and change metrics for indexed tokens across the same requested time windows.
  • On Solana only, pass includes=money_flow to include money flow data for each token. The include adds 3 CU to the batch base before the batch multiplier is applied.
  • On Solana, each token also includes unique buyer and seller counts by interval, with matching history and change-percent fields.
  • Each token’s money_flow entries include buyer/seller trader counts, buy/sell amounts, USD values, transaction counts, wallet tags, frames, and timestamps.
  • Batch CU is calculated as ceil(12 * count^0.8); with includes=money_flow, use ceil(15 * count^0.8).
  • Compare trading activity across a watchlist or screener result set.
  • Detect volume spikes and buy/sell pressure across many tokens with fewer API calls.
  • Compare which tokens are attracting fresh participation or losing activity across the same recent windows.
  • Rank tokens by recent participation, trade count, and volume momentum.
  • Feed batch trade metrics into bots, alerting systems, and analytics pipelines.
  • Set x-chain for the target network.
  • Pass list_address as comma-separated token addresses.
  • Use the same frames across the batch so every token is comparable.
  • Use includes=money_flow on Solana to add buy/sell flow context to every token returned in the batch.
  • Compare unique_buyer_* and unique_seller_* across tokens to measure participation breadth consistently within the batch.
  • Use this endpoint when you want multi-token activity windows, not just current price or valuation snapshots.
  • Use the single endpoint for drill-down views after a user selects one token.
  • Use batch trade data for screeners and alerts where every token should be scored on the same timeframe set.
  • Deduplicate addresses and keep the requested frame list consistent.
  • Join with batch market data to rank both market quality and current activity.

Authorizations

​
X-API-KEY
string
header
required

API key for authentication

Headers

​
x-chain
enum<string>
default:solana

A chain name listed in supported networks.

Available options:
solana,
ethereum,
bsc,
base,
robinhood,
arc,
sui,
mantle,
hyperevm,
arbitrum,
avalanche,
optimism,
polygon,
zksync,
monad,
aptos,
fogo,
megaeth

Query Parameters

​
list_address
string
required

A list of token addresses in string separated by commas (,)

​
frames
string

A list of custom time intervals separated by comma (,). Users can pass up to 8 intervals. Rules:

  • Minute intervals: from 1m up to 1440m (e.g. 1m,15m,16m,17m,89m,90m,92m,1440m ...).
  • Second intervals: must be multiples of 5s, from 5s up to 3600s (e.g. 5s,10s,15s,90s,3600s ...).
  • Hours intervals: only support (1h 2h 4h 8h 24h)
​
ui_amount_mode
enum<string>
default:scaled

Indicate whether to use the scaled amount for scaled ui amount tokens. Only support solana

Available options:
raw,
scaled
​
includes
enum<string>

Specify additional information to include in the response. money_flow is supported only on Solana. Use includes=money_flow to include money flow data.

Available options:
money_flow

Response

JSON object containing trade data of multiple tokens

​
success
boolean
required

Whether the request completed successfully.

​
data
object
required

Map keyed by token address. Each value is the token trade-data object for that token, or null when trade data is unavailable.