Skip to main content
GET
Token - Wallet Tags Tracker Details

One row per wallet, per bucket. The response is a list of time buckets (items); each bucket has a unix_time (bucket open time) and a wallets array of the tagged wallets that traded in it.

  • Each wallet row carries its own volume_buy / volume_sell (token amounts) and volume_buy_usd / volume_sell_usd, plus tx_buy_count / tx_sell_count.
  • tags lists the wallet’s tags for this token (dev, sniper, smart_trader, kol). A wallet can carry several.
  • is_top_10_holder appears only when top_10_holder=true, flagging wallets that are among the token’s top 10 holders.

Reading the numbers. Volumes are gross and leg-based — a transaction that both buys and sells counts on both sides, with no netting. tx_buy_count / tx_sell_count count that wallet’s buy/sell transactions in the bucket. Wallets are ordered by USD volume descending and capped per bucket by limit_wallet; buckets with no activity are omitted. At most limit_bucket buckets are returned — while has_more is true, pass next_time_from back as time_from to page forward.

  • This endpoint consumes 30 CU per request.
  • Drill into a single candle to see exactly which developers, snipers, and smart-money wallets bought or sold.
  • Turn a volume spike from the summary endpoint into the actual wallet addresses behind it — ready to label, follow, or alert on.
  • Track a known set of wallets over time by passing wallets=, watching how specific actors accumulate or exit bucket by bucket.
  • Build wallet-level launch forensics and post-mortems that name who drove each phase, not just how much volume moved.
  • Provide a token_address, a required time_from unix timestamp in seconds, and a required time_frame. Omit time_to to read activity up to now.
  • Pick time_frame by the question you’re asking: 1s30s for launch forensics, 1m30m for intraday rotation, 1h1M for trend.
  • Use tags=dev,sniper,smart_trader,kol to narrow the cohorts, or wallets=addr1,addr2 (up to 50) to restrict to specific addresses.
  • Set min_volume_usd to drop dust wallets, and top_10_holder=true to flag top holders via is_top_10_holder.
  • Tune limit_wallet (wallets per bucket, up to 50) and limit_bucket (buckets returned, up to 300). While has_more is true, pass next_time_from back as time_from to page forward.
  • Use the Wallet Tags Tracker (summary) to spot the interesting buckets first, then drill into those windows here for the wallet-level detail.
  • Raise min_volume_usd to focus on wallets that actually moved the market and keep noise out of dashboards.
  • Pass wallets= to follow a known cohort — insiders, a dev’s set, or flagged smart money — across every bucket in the range.
  • Keep limit_wallet tight for UI tables and page buckets with next_time_from rather than requesting an oversized range at once.
  • Solana only.
  • Supported tags are dev, sniper, smart_trader, and kol.
  • Maximum range per time_frame — seconds: 30 days, minutes: 60 days, hours: 90 days, 1D/1W/1M: 365 days. Exceeding it returns 400.
  • Some highly held or high-cost tokens (wSOL, USDC, USDT, BONK) are not supported for this endpoint.

Authorizations

X-API-KEY
string
header
required

API key for authentication

Headers

x-chain
enum<string>
default:solana

Solana network only.

Available options:
solana

Query Parameters

token_address
string
required

Token mint address

Example:

"9cRCn9rGT8V2imeM2BaKs13yhMEais3ruM3rPvTGpump"

time_from
integer
required

Start of the range, as a unix timestamp in seconds.

Example:

1782864000

time_to
integer

End of the range, as a unix timestamp in seconds. Defaults to now. Must be greater than time_from, and within the time_frame's maximum range.

Example:

1785369600

time_frame
enum<string>
required

Size of each time bucket. Must match the bucket the drilldown is read against.

Available options:
1s,
5s,
15s,
30s,
1m,
3m,
5m,
15m,
30m,
1h,
2h,
4h,
1D,
1W,
1M
Example:

"1D"

tags
enum<string>[]

Comma-separated wallet tags to restrict the response to. Defaults to all supported tags.

Available options:
dev,
sniper,
smart_trader,
kol
Example:
wallets
string[]

Comma-separated wallet addresses to restrict the response to. Up to 50 addresses.

min_volume_usd
number
default:0

Only include wallets whose USD volume in a bucket is at least this value.

Required range: x >= 0
top_10_holder
boolean
default:false

Set to true to flag wallets that are among the token's top 10 holders (is_top_10_holder).

limit_wallet
integer
default:10

Max wallets returned per bucket, ordered by USD volume descending. 1-50.

Required range: 1 <= x <= 50
limit_bucket
integer
default:300

Max time buckets returned. 1-300. Use next_time_from to page beyond this.

Required range: 1 <= x <= 300

Response

JSON object containing the per-bucket wallet drilldown for tagged wallets: each time bucket lists the wallets that traded in it with their buy/sell volume and transaction counts

success
boolean
required

Whether the request succeeded.

data
object
required