id (WebSocket only), the channel, the channel’s parameters, a type and, for data frames, data. The parameters come back in their canonical form: chain as its id (sol, eth, bsc, base, robinhood), an EVM address in lowercase. Examples below are real frames, shortened.
trades
Parameters:chain, token.
trade. On Solana, two wallets that sign one transaction are two trades, and a trade the server reads again after a gap in its feed is not sent a second time when it also arrives live. On EVM chains there is one trade per swap log, so one wallet can have several in one transaction.
Key rows on id: it is the same on REST pages, the snapshot, trade, retract and tags frames. One wallet can have several rows in one transaction (see Trades), so never deduplicate on signature or on signature + wallet. On EVM chains the snapshot is the REST first page, and the second leg of a routed swap arrives as its own trade.
When the history cannot be read for a moment, the first snapshot holds only the trades the server has live (it can be empty), and a full snapshot follows within seconds. After any later snapshot, the trades sent live meanwhile that it does not hold come again as trade, so appending stays right.
retract
On Solana a block can lose its fork after its trades went out live: they never happened there. Thetrades channel can then send one retract frame per lost slot, after the trades it names, usually 10 to 40 s after them:
- Remove the rows with these ids.
reasonisdead(the validator marked the slot dead),abandoned(the confirmed chain does not descend from it) orother; the rows go either way. - A transaction that landed in another block comes again later as a new
trade, with the same signature and that block’s amounts and time. Append it like any other trade. - REST pages and later snapshots no longer hold the removed rows.
- Never handle a frame
typeyou do not know as a trade: a client that ignoresretractkeeps the rows until its list is replaced by a snapshot.
candles
Parameters:chain, token, interval (1s … 1w, default 1m), unit (usd or marketCap, default usd), currency (usd or native, default usd: native prices the chart in the chain’s coin, and frames then carry "currency": "native").
candle with the same time as your last one replaces it; a later time starts a new candle, which opens at the previous close. volume is in USD in both units, or in the coin with currency=native (the forming candle divides by the coin’s price now; the closed REST candle by its price at the candle’s end). The forming candle’s wick is judged by the rule the REST candles follow, against the same candles. With unit=marketCap every candle is the price times the supply /tokens uses for marketCapUsd, the same on REST, the snapshot and live frames. Candles are built from the trades of the trades channel, so chart and tape agree. A trade the chart does not count (the REST candles leave it out too), or one older than the forming candle, sends nothing; with no trade there is no frame. With unit=marketCap, live candles need the token’s supply: when it is not known, only the snapshot comes.
When a Solana block loses its fork (see retract), the channel can send a fresh snapshot, its candles built again without that block’s trades: it replaces what you hold. token, launchpad and wallet send nothing new for it.
token
Parameters:chain, token.
marketCapUsd on a tick is the trade’s price times the supply of the last snapshot (null while the supply is not known). liquidityUsd is set only when the trade was in the token’s main pool; otherwise it is null: keep the last value you have. The periodic snapshot refreshes holders, stats and liquidity. A tick follows the snapshot’s price rule: where no market can carry a price, priceUsd and marketCapUsd are null.
launchpad
Parameters:board (new, graduating, graduated), chain (optional; omitted, every chain, and frames carry "chain": null).
/tokens/{chain}/{address} gives for the token; key rows on chain + address. While the board is watched, rows also carry stats and statsAt (the 1m–24h windows); a change of stats alone goes with the token’s next update, or on its own at most 15 s later. A token any source reports as graduated is never on graduating; a complete curve waits there at most 5 minutes for its migration. A token moving from graduating to graduated is a remove on one board and an add on the other. Updates are coalesced: at most two per second per token. Under heavy load the server coalesces further, to at most one frame per token every 1 to 2 s: the frame carries the latest values, and a token that joined and left the board within that window sends nothing. After lagged, a fresh snapshot follows at once.
prices
No parameters.prices never sends lagged: a subscriber that fell behind gets the current prices in its next update.
wallet
Parameters:chain (any chain, default sol), wallet (an address of that chain; EVM addresses come back lowercase), balances (optional, true or false).
trade; key them on id (on EVM chains one row per pool a transaction swapped through). Live trade frames carry the token’s name, symbol and image like the snapshot (a token the server has not named yet is named on its next frame), and volumeNative. On Ethereum, BNB Chain, Base and Robinhood Chain swaps come live as they land; a few seconds after it opens the channel reads the wallet’s swaps once more and sends the ones the snapshot lacked. balance and native values follow the holdings rules (no value without a pool of at least $1,000). When the server’s own feed was down for a while, the channel sends a fresh snapshot (and holdings) again. When the history cannot be read, the snapshot is empty ([]); if it was only for a moment, a full snapshot follows within seconds. The server holds a limited number of live wallets: past it a new subscription gets an error with code rate_limited.
trending
Parameters:chain, interval (1m, 5m, 1h, 6h, 24h or 1d; default 1h), sort (as /trending, default trades), limit (0–100, default 50).
The ranking is read about every 10 seconds (less often when many rankings are watched); each read sends a
summary and the changes. With limit 0 only summary comes. A token ranked twice by the source comes once. After lagged, a fresh snapshot and summary follow. If the ranking cannot be read when you subscribe, an error comes first, then the snapshot as soon as a read succeeds.
holders and traders
Parameters:chain, token.
A new list comes at most every 10 s (
holders) or 15 s (traders) while the token trades; a token that does not trade sends nothing new, and you never get the same list twice. If the first read fails, an error comes first, then the snapshot as soon as a retry succeeds. There is no lagged: a subscriber that fell behind gets the latest list.
pairs
Parameters:chain (an EVM chain: eth, bsc, base, robinhood), token.
pool is the pair or pool contract, of any DEX, or the pool’s 32-byte id on a DEX that keeps every pool in one contract (Uniswap V4, PancakeSwap Infinity); token0 and token1 are its two tokens in lowercase, and the token you subscribed is one of them. lastEventAt is the time of the pool’s latest swap or liquidity change the server saw. Key pools on pool: one in the snapshot can also come as pair, and an active pool comes again with a newer lastEventAt. No history is read: pools appear as they trade, so a token nobody watched starts with an empty snapshot. EVM chains only (sol is refused).
lagged
dropped of them. The channel catches up on its own with a fresh snapshot, which replaces what you hold: launchpad, pairs and trending send it right after; trades, candles, token and wallet read their history again first, and retry from 2 s up to every 30 s if that read fails, while live frames keep coming. prices sends no lagged (see prices).
errors
A channel that cannot read its history sends anerror frame instead of its first snapshot, with the channel’s fields and the code the REST route would give:
Wrong parameters never reach a channel: the WebSocket answers an
error for the op, and SSE a 400 before the stream starts. See Live errors.