Skip to main content
WS channel: token-updates Live refresh of the mutable Token Details fields - price, market cap, liquidity, bonding progress, 24h stats. Pushed as they change, at the pace you choose (updatePeriod, 100 ms by default), for one token or a list of up to 50 (100 on a raised limit); fields you already parse from /v1/token.
string
Public chain id - evm:<id> or solana. Required with address. Example: solana
string
Token address. Required unless you give tokens. tokenAddress is accepted as the same parameter (give one of the two). Example: CBZq5ycLcr6mnYvjFTPuYSuhgS3ujsiTrT4sqatBpump
object[]
A list of 1 to 100 { "chain", "address" } entries (or { "chain", "tokenAddress" }), instead of chain and address. One subscription, one message per period carrying every token that changed, as "data": [state, ...]. Each token of the list counts as one subscription in your limits, and token-updates holds at most 50 subscriptions per account by default (ask us to raise it, up to 100 per list): a list that does not fit is refused as a whole (RATE_LIMITED, the message says how many fit). since is not available on a list.
integer | string
Milliseconds, 0 to 60000, or "block"; default 100. Each period delivers the latest state of each token that changed ("block": one message per chain and per block); the ack carries the value applied (snapped up to 0, 100, 200, 250, 500, 1000, 2000, 5000, 10000, 30000, 60000). See Choosing your pace.
string[]
Extra sliding windows, among 1m, 5m, 15m, 30m, 1h, 4h, 6h, 12h, 24h (a list or a comma-separated string). Each state then ends with a windows object carrying one block per window you asked, with the same fields as stats24h. Absent unless you ask. On a tokens list, give windows once, next to the list: it applies to every token. Example: ["5m", "1h"]
Each state starts with chain and address, then tokenAddress (the same token) and poolAddress, the token’s main market whose price the state carries: the pool of /v1/token (for a native coin, its main USD market; null when unknown).
The refresh runs server-side through the same engine as /v1/token, so stats24h carries the identical fields and numbers as the REST snapshot - re-parse events with the code you already wrote. liquidityNative and liquidityUsd are the token’s liquidity, the figure of /v1/token: its most traded markets summed, each counted on its smaller side. pooledBase, pooledQuote, pooledBaseNative and pooledQuoteNative are what sits in the token’s main pool (poolAddress), the pool block of /v1/token with the same values (see /v1/pool for their rules): null while the token is on its launch curve, on majors, stablecoins, wrapped natives and native coins, and when the pool’s indexed reserves are not reliable. They never send a message on their own, periodic states included: they are refreshed with the token’s next message. stats24h.uniqueBuyers and stats24h.uniqueSellers are the distinct wallets whose last buy or last sale falls in the window, across the token’s pools, counted live and refreshed on every event. stats24h.traders is the number of unique wallets that bought or sold in the window, each wallet counted once across the token’s pools, the figure of /v1/token: it is refreshed with every trade of the token and with each periodic state, and it is null when unknown (on majors, stablecoins, wrapped natives and native coins). stats24h.feesNative and stats24h.feesUsd are the fees paid by traders in the window, summed over the token’s pools, in the chain’s native unit and in USD at the same rate as volumeUsd, the figures of /v1/token (null on majors, stablecoins, wrapped natives and native coins). The stream adds three counts the REST snapshot does not carry: stats24h.snipers, stats24h.proTraders and stats24h.smartTraders, the wallets flagged as snipers of the token, as pro traders and as smart traders that traded in the window. Every state carries its chain and address, then the token’s holders and label stats, with the names of /v1/token and /v1/token/security: holdersCount, top10HoldersPct, top25HoldersPct, top50HoldersPct, devHoldingsPct, snipersHoldingsPct, bundlersHoldingsPct, insidersHoldingsPct and proTradersAllTimeCount (defined on the Pulse card), and right after each of the three label shares the number of those wallets still holding the token: snipersCount, bundlersCount and insidersCount, the figures of /v1/token. On Solana all twelve are served, each null when unknown. On EVM chains holdersCount, top10HoldersPct, top25HoldersPct and devHoldingsPct are served, each null when unknown, and top50HoldersPct and the seven label fields are null; these EVM holder figures never send a message on their own, periodic states included: they are refreshed with the token’s next message. A state moved only by these figures is free; on Solana the three counts are refreshed when the token’s holders or label shares move, and with each periodic state. Your first message is the current state ("reason": "subscribe", 1 credit); every 60 s, if anything moved, the full state is sent again for free ("reason": "periodic"), as it is after a hiccup ("reason": "resync"). A change costs 1 credit per token that traded, or had another on-chain event, since your previous message; a token moved only by the native coin’s USD price is free, and a native coin (ETH, BNB, SOL…) costs 1 when its price changed (Billing). windows carries the same sliding windows as the Pulse views, with the fields of stats24h; stats24h is the same whether you ask windows or not, and a window we cannot fill yet is null, never a partial number. A token that /v1/token does not know yet (not indexed yet, or a Solana address with the wrong letter case) is acknowledged and sends nothing until it exists: check the address against /v1/token if no first message comes.

Close codes

Resume

Events carry a cursor. After a reconnect, a subscribe with "since": "<cursor>" is accepted and starts with the current state: every event is the full state, so nothing needs to be replayed. On a tokens list, subscribe again without since: the first message carries the current state of every token.
Ack
type:object

Server acknowledgement: the subscription is live.

Update
type:object

Server push frame (Update).

Subscribe
type:object

Client frame opening the subscription (additive, ack is explicit).