Skip to main content
Confirmed vs. unconfirmed events: Use the commitmentLevel argument to choose which events you receive.
  • confirmed — receive events only after they’re confirmed on-chain. This is the default if commitmentLevel is not specified.
  • processed — receive events as soon as they’re observed on-chain (unconfirmed; may be reorged out). You must explicitly set commitmentLevel: processed to opt in. Currently available on Solana only.
This endpoint requires a Growth or Enterprise plan. Learn more.

​
Returns

​
AddTokenEventsOutput
AddTokenEventsOutput!
See AddTokenEventsOutput

​
Arguments

​
input
OnTokenEventsCreatedInput!
required
See OnTokenEventsCreatedInput
​
commitmentLevel
[EventCommitmentLevel!]
The commitment levels to subscribe to. When multiple commitment levels are subscribed to, events are emitted at most once per increasing commitment stage per subscriber. If a stronger commitment level is observed first, later weaker updates for the same event are suppressed for a short in-memory window. Preprocessed is supported only for Solana event subscriptions. Preprocessed evaluates pre-execution events and can differ significantly from processed or confirmed output. In particular, preprocessed swaps may use aggregator swaps before it is known how execution will route the underlying swaps, and many preprocessed events may error and never be processed. See EventCommitmentLevel
subscription {
  onTokenEventsCreated(
    input: {
      tokenAddress: "So11111111111111111111111111111111111111112"
      networkId: 1399811149
    }
  ) {
    id
    events {
      eventType
      eventDisplayType
      timestamp
      blockNumber
      transactionHash
      maker
      address
      token0Address
      token1Address
      token0SwapValueUsd
      token1SwapValueUsd
      token0ValueBase
      token1ValueBase
      walletAge
      walletLabels
      labels {
        sandwich {
          label
          sandwichType
          token0DrainedAmount
          token1DrainedAmount
        }
      }
    }
  }
}
Example Response
{
  "data": {
    "onTokenEventsCreated": {
      "id": "D9TvhCRcD9JAkA4nfbYH9sUfhcJVzwrhCCj7jgwtD85s:1399811149",
      "events": [
        {
          "eventType": "Swap",
          "eventDisplayType": "Buy",
          "timestamp": 1769561435,
          "blockNumber": 396376317,
          "transactionHash": "4pAiF26PJSxj4qnWGjaFL5tFgV9zGa38sxzcXyzA8MAM7KiviTS4pdqTPoUusPccH3k7VbXWqfoEsqLkkLMzSrkm",
          "maker": "9Fke4xFjBZfUxe54TFbfZyUiWoGF91NB87gbgAqhVrZh",
          "address": "D9TvhCRcD9JAkA4nfbYH9sUfhcJVzwrhCCj7jgwtD85s",
          "token0Address": "FGerXseLVoEsbFtbMAN41V9kc68vJCZxVf1g7NzHBAGS",
          "token1Address": "So11111111111111111111111111111111111111112",
          "token0SwapValueUsd": "0.000055871173472466600153642132795497",
          "token1SwapValueUsd": "126.8383173428749235655594956278139469319",
          "token0ValueBase": "4.4042949909665e-7",
          "token1ValueBase": "1",
          "walletAge": 14513261,
          "walletLabels": null,
          "labels": {
            "sandwich": null
          }
        }
      ]
    }
  }
}

​
Usage Guidelines

  • Pass tokenAddress and networkId to stream events for a token across all its liquidity pools
  • Unlike onEventsCreated (which subscribes to a single pair), this aggregates swaps from every pool the token trades in
  • Each event includes address — the pair contract where the swap occurred — so you can identify which pool it came from
  • The events array may contain multiple events per message
  • Use eventDisplayType for human-readable buy/sell labels and token0SwapValueUsd / token1SwapValueUsd for USD values

​
Troubleshooting Tips

Use onTokenEventsCreated when you want to monitor all trading activity for a token regardless of which pool it happens in. Use onEventsCreated when you only care about a specific pair (e.g., SOL/USDC on a particular DEX).
Each event includes an address field — this is the pair contract address where the swap occurred. You can use this to group or filter events by pool.
Yes. Omit tokenAddress and pass only networkId to receive all events across the entire network. This requires an enterprise plan with EventFeed features and is extremely high-volume.
Events include Swap, Mint, and Burn types. eventDisplayType translates these into user-friendly labels like Buy, Sell, Add Liquidity, and Remove Liquidity.
  • Detailed Token Page: Build a comprehensive token detail page with price, holders, trades, and real-time updates
  • Events: Build a token swap list with filtering, pagination, and real-time updates