Skip to main content
WS channel: pool-updates Live refresh of a market’s mutable fields - price, market cap, liquidity, bonding progress, windowed stats. The price moves on every trade of the pool. Events are pushed as soon as something changes, grouped by your updatePeriod (100 ms by default: a burst of trades inside one period arrives as one event carrying the latest values), and deduplicated - you only receive an event when something actually changed. Every 60 s, if anything moved, the full state is sent again for free.
string
Public chain id - evm:<id> or solana. Required with pool. Example: solana
string
Pool (market) address. Required unless you give pools. poolAddress is accepted as the same parameter (give one of the two). Example: BqnpCdDLPV2pFdAaLnVidmn3G93RP2p5oRdGEY2sJGez
object[]
A list of 1 to 100 { "chain", "pool" } entries (or { "chain", "poolAddress" }), instead of chain and pool. One subscription, one message per period carrying every pool that changed, as "data": [state, ...]. Each pool of the list counts as one subscription in your limits, and pool-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 pool 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 a window of stats. Absent unless you ask. On a pools list, give windows once, next to the list: it applies to every pool. Example: ["1m", "15m"]
Each state starts with chain and pool, then tokenAddress (the pool’s token, the token.address of /v1/pool/data; null when unknown) and poolAddress (the same pool as pool).
bondingProgress and migrated are the market’s launchpad state, the same values as on /v1/pool/data: the progress of a bonding curve, or the progress toward the liquidity or market cap goal of a launchpad with no bonding curve (Clanker, Bankr, Zora…) on the pool it launched its token into, null on any other pool, and migrated: true once a launchpad pool graduated. On a launchpad whose goal is a market cap in USD, both follow the price of the native coin.
pooledBase, pooledQuote, pooledBaseNative and pooledQuoteNative are what sits in the pool, the same fields and values as on /v1/pool/data (see /v1/pool for their rules): null on a launch curve, on a concentrated-liquidity pool whose indexed reserves are not reliable, and before the pool ever held anything. They never send a message on their own, periodic states included: a state moved only by them is not sent, and the pool’s next message carries their latest values.
migratedTo and migratedFrom link the two pools of a launchpad migration, the same values as on /v1/pool/data: on a bonding curve that migrated, the address of the pool it migrated to; on the pool a migration landed in, the address of its bonding curve. Both are null on every other pool. A bonding curve’s frame carries migratedTo as soon as the curve migrates: subscribe to that pool to keep following the market.
The refresh runs server-side through the same engine as /v1/pool/data, so stats carries the identical 5m/1h/24h windows and field names as the REST snapshot - re-parse events with the code you already wrote. In each window, uniqueBuyers, uniqueSellers and traders are the distinct wallets whose last buy, last sale or last trade falls in the window, counted live and refreshed on every event of the pool. feesNative and feesUsd are the fees paid by the pool’s traders in the window, in the chain’s native unit and in USD at the same rate as volumeUsd, the figures of /v1/pool/data; Solana pools add poolFeesNative, the fees collected by the pool itself. The stream adds three counts per window the REST snapshot does not carry: snipers, proTraders and 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 pool. Your first message is the current state ("reason": "subscribe", 1 credit); the full states sent again on our own ("reason": "periodic" every 60 s, "reason": "resync" after a hiccup) are free; a change costs 1 credit per pool that traded, or had another on-chain event, since your previous message, and is free otherwise (Billing). windows carries the same sliding windows as the Pulse views, with the fields of a stats window; stats itself always keeps 5m, 1h and 24h, and a window we cannot fill yet is null, never a partial number. A pool that /v1/pool/data 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/pool/data 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 pools list, subscribe again without since: the first message carries the current state of every pool.
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).