Skip to main content
Track high-value Solana trades and KOL activity without maintaining your own wallet-labeling or trade-indexing pipeline.
The REST API returns the latest indexed trades. Datastream delivers new trades in real time over WebSocket. Both use your Solana Tracker Data API key.

What you can build

  • Whale watch: alert when a trade exceeds a 1k,1k, 2.5k, 5k,or5k, or 10k threshold.
  • Whale tracker: build a live feed of high-volume wallets, tokens, protocols, and buy/sell direction.
  • KOL tracker: monitor the shared KOL roster and display identity metadata when available.
  • KOL token page: show KOL activity for one token with hideArb=true.
  • Copy-trading trigger: use a KOL or whale trade as a signal, then apply your own risk and execution rules.
KOL tier rooms and REST filters use cumulative minimum thresholds.

REST API

Latest whale trades

Fetch the newest high-volume trades:
minVolume accepts 1000, 2500, 5000, or 10000. Results are sorted newest first.

Latest KOL trades

Fetch trades from wallets on the shared KOL roster:
For all eligible KOL trades, use minVolume=0 or omit minVolume entirely:
When identity data is available, each trade includes:

KOL trades for one token

Use a mint-scoped feed for a token detail page or token-specific alert:
The token-scoped KOL endpoint also defaults to minVolume=0; pass minVolume=0 explicitly when you want to make that behavior clear. With hideArb=true, the response keeps only rows where the requested mint is one side of the trade.

Paginate through history

Responses include nextCursor and hasNextPage. Pass the opaque cursor back unchanged:
Use showMeta=true when your UI needs token names, symbols, images, decimals, or historical prices for the from and to sides.
Treat nextCursor as opaque. Do not decode, modify, or construct cursors in application code.

Real-time Datastream

Connect to:

Whale watch

Join a tier room to receive new qualifying trades:
Available whale rooms:
Rooms are cumulative. A $12,000 trade is delivered to the 1000, 2500, 5000, and 10000 rooms. Join only the tiers your application needs.

KOL tracker

transaction:kol receives every eligible KOL trade, including trades below the $1,000 tier threshold:
For high-value KOL alerts, use cumulative tier rooms:

KOL signal pipeline

Use a small event pipeline to turn KOL trades into alerts or review queues:
Use signals for research, notifications, or a human review queue. Do not mirror trades blindly: check liquidity, slippage, token safety, wallet exposure, and whether the trade is part of an arbitrage route before executing anything.

Message shape

Whale and KOL Datastream messages contain one enriched trade in a one-item data array:
identity is present when the trading wallet is on the shared KOL roster. time is a Unix timestamp in milliseconds. volume is absolute USD volume; use type to determine buy or sell direction.

Production checklist

  1. Deduplicate by transaction signature plus wallet, token, and side if your consumer reconnects.
  2. Persist the last REST nextCursor when backfilling.
  3. Reconnect WebSocket clients with exponential backoff.
  4. Join only the required rooms to avoid duplicate cumulative events.
  5. Store the raw trade and your derived alert separately.
  6. Apply your own risk and execution checks before copy trading.

Whale & KOL REST API

Browse endpoint parameters, response schemas, and pagination.

Whale & KOL Datastream

Browse rooms, join messages, and live trade payloads.

Live Transactions

Subscribe to every swap for a token.

KOL Tracking

Analyze wallet performance and KOL activity.