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

Focused trading-activity stats for one token.

  • Returns buy/sell counts, trade counts, unique wallets, volume, and change metrics across requested timeframes.
  • Use frames to request one or more custom timeframes.
  • Use this endpoint when you need timeframe-based market activity around the current price, not just the current market snapshot.
  • Use ui_amount_mode=scaled for Solana Token-2022 scaled UI amounts when the token supports scaled UI amount extension.
  • On Solana only, pass includes=money_flow to include token money flow data. This adds 3 CU to the request cost.
  • On Solana, the response also includes unique buyer and seller counts by interval, including the matching history and change-percent fields.
  • The money_flow entries include trader buy/sell counts plus buy/sell token amounts, USD values, transaction counts, wallet tag, frame, and timestamps.

Reading the numbers. Buy/sell counts and volumes describe activity inside each timeframe. Change-percent fields compare the current timeframe window with the previous matching window, which makes this endpoint useful for reading recent momentum and participation around price moves.

  • This endpoint consumes 12 CU per request, plus 3 CU when includes=money_flow is used.
  • Analyze buy/sell pressure and trading activity for a single token.
  • Build momentum indicators using trade counts, unique wallets, and volume over selected frames.
  • Study how participation and turnover changed across recent windows before or after a price move.
  • Trigger alerts when trading activity, volume, or buy/sell imbalance changes quickly.
  • Combine with market data to explain whether valuation changes are backed by real activity.
  • Provide address as the token address and set x-chain.
  • Use frames=5m,1h,24h style requests for the horizons your product displays.
  • Use shorter frames when you care about recent momentum and reaction, and longer frames when you care about broader context.
  • Use includes=money_flow on Solana when buy/sell flow and trader participation context is needed alongside trade statistics.
  • Use the interval-specific unique_buyer_* and unique_seller_* fields to distinguish broad buyer/seller participation from repeated trades by the same wallets.
  • Set ui_amount_mode=raw or scaled consistently with your Token-2022 amount handling.
  • Use Token Overview when you need both market fundamentals and trade activity in one payload.
  • Pair trade counts with unique-wallet counts to separate broad market participation from repeated activity by a smaller wallet set.
  • Compare buy and sell volume together instead of reading total volume alone.
  • Use shorter frames for alerts and longer frames for ranking or trend summaries.

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

​
address
string
required

The address of the token contract.

​
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 a specific token

​
success
boolean
required

Whether the request completed successfully.

​
data
object
required