Skip to main content

​
Returns

​
Arguments

​
Usage Guidelines

  • Query using tokenAddress and networkId — this aggregates stats across all pairs for the token
  • Use durations array to request specific time windows: min5, min15, hour1, hour4, hour12, day1, week1, day30
  • Stats are returned in separate fields like stats_hour1, stats_day1, etc. based on requested durations
  • statsUsd contains USD-denominated metrics: volume, buyVolume, sellVolume, open, highest, lowest, close, liquidity
  • statsNonCurrency contains count metrics: transactions, buys, sells, traders, buyers, sellers
  • Each metric includes currentValue, previousValue, and change (percent change in decimal format, e.g. -0.52 = -52%)
  • Use buckets array within each metric for granular time-series data within the duration window
  • Use timestamps array to map bucket indices to their corresponding time ranges

​
Troubleshooting Tips

getDetailedTokenStats aggregates stats across all pairs for a given token, giving you a holistic view of the token’s activity. getDetailedPairStats returns stats for a specific pair, which is useful when you care about a token’s activity within a single liquidity pool.
FILTERED stats exclude suspected bot and MEV activity to show organic trading. UNFILTERED (the default) includes all transactions. Use the statsType parameter to choose which type you want.
Each metric includes a buckets array with values for sub-intervals within the duration. For example, stats_hour1 might contain 12 buckets of 5 minutes each. Use the timestamps array at the same level to map each bucket index to its start/end time range, which gives you the x-axis for your chart.
The change field requires both currentValue and previousValue to calculate. For very new tokens or time windows with no previous data, change may be null.
Use the timestamp parameter to query stats as of a specific point in time. By default, stats are returned for the current time.
The bucketCount parameter controls how many sub-intervals the duration is divided into. For example, requesting stats_hour1 with bucketCount: 12 gives you twelve 5-minute buckets. This affects the length of the buckets array within each metric.