Solana wallet tracking API

Show me

Watch a wallet, read its events

Add an address once; every swap and SOL transfer it makes becomes an event. Values are illustrative, keys are what the API returns.

1. 1 · Watch

   Add the address with an optional label. The label comes back on every event.

   Add a wallet to the watchlist

   POST /api/v1/wallet-tracker/watchlist
   Authorization: Bearer msk_...
   Content-Type: application/json
   
   { "wallet_address": "7xKX...3bPq", "label": "watch #1" }

2. 2 · Read

   Swaps carry the token and side; transfers name the counterparty. The first page is in slot order.

   Read the events

   // GET /api/v1/wallet-tracker/trades?limit=2
   {
     "events": [
       {
         "wallet_address": "7xKX...3bPq",
         "label": "whale #1",
         "event_type": "swap",
         "action": "buy",
         "token_mint": "8vdc...pump",
         "token_symbol": null,
         "token_name": null,
         "sol_amount": 2.5,
         "token_amount": 1000000,
         "tx_signature": "5Hyj...kMnP",
         "block_time": 1790157600,
         "slot": 449476673,
         "replayed": false,
         "ingested_at": "2026-09-23T10:00:00.000Z",
         "timestamp": "2026-09-23T10:00:00.000Z"
       },
       {
         "wallet_address": "7xKX...3bPq",
         "label": "whale #1",
         "event_type": "transfer",
         "action": null,
         "token_mint": null,
         "token_symbol": null,
         "token_name": null,
         "sol_amount": 40,
         "token_amount": null,
         "counterparty": "9WzD...AWWM",
         "tx_signature": "2mLq...Xw9e",
         "block_time": 1790157540,
         "slot": 449476520,
         "replayed": false,
         "ingested_at": "2026-09-23T09:59:00.000Z",
         "timestamp": "2026-09-23T09:59:00.000Z"
       }
     ],
     "count": 2,
     "ordered_by": "slot",
     "next_cursor": 1790157540,
     "next_cursor_slot": 449476520
   }

3. 3 · Enrich

   KOL, early-buyer wallet and bot flags come from the Universal Wallet API, a separate endpoint that answers for any address.

   Enrich an address (Universal Wallet API, abridged)

   // GET /api/v1/wallet/7xKX...3bPq  (a separate endpoint, any address)
   {
     "address": "7xKX...3bPq",
     "flags": {
       "is_kol": false,
       "kol_name": null,
       "is_alpha_tracked": true,
       "bot_confidence": "low",
       "is_deployer": false,
       "is_sniper": false,
       "is_bundler": false
     }
   }

Enriched events

Enriched events, not raw events

What you would otherwise decode yourself, and the field that carries it. Coverage windows in the data dictionary

• Raw: Balance changes spread over pre- and post-token accounts

  One swap event with buy or sell, the token and the SOL amount, on any venue

  • event_type
  • action
  • token_mint
  • sol_amount

• Raw: A lamport delta with no token movement

  A transfer event naming the other side

  • event_type
  • counterparty

• Raw: Arrival order, which a reconnect can scramble

  Chain position, and a flag for events recovered after a reconnect

  • slot
  • replayed
  • ordered_by

• Raw: An address with no context

  Your label, plus KOL, early-buyer wallet and bot flags from the Universal Wallet API

  • label
  • is_kol
  • is_alpha_tracked
  • bot_confidence

Architecture

From watched addresses to your users

1. 1 · Source

   Chain activity

   Transactions and program events

3. 2 · MadeOnSol

   Data and intelligence layer

   • Swap and transfer events
   • KOL and early-buyer wallet labels
   • Token and deployer context

5. 3 · Delivery

   • REST API/api/v1 request-response
   • Webhookssigned HTTPS push
   • WebSocket streamswallet_tracker:events channel

7. 4 · Yours

   Your watchlists and alert rules

   Keys and business logic stay server-side

9. 5 · Users

   Your wallet product

• Wallet alerts
• Portfolio monitoring
• Rule-based trade alerts
• Large-wallet trackers
• Trader research dashboards

Displaying MadeOnSol data to your own users requires a Business plan. See pricing