WebSocket
Upgrade to a WebSocket that carries up to 200 live channels. Send JSON ops, receive JSON frames:
id is optional (the server assigns s1, s2, …). Query parameters of the upgrade URL
(?channel=trades&chain=sol&token=…) subscribe one channel right away, with the id s1. A wrong op or
subscribe answers a frame of type error with the subscription’s id. The server pings
every 20 s and closes a socket that sends nothing at all (not even a pong) for 60 s.
Channels and frames: see the Streaming guide.
The key is checked before the upgrade (401), and opening the socket counts as one request
against the rate limit. While the server is at capacity, a new socket’s upgrade answers 503
(server_busy, Retry-After: 30); open sockets keep running. The same socket is at
wss://ws.raze.bot.
A Solana block that loses its fork. Its trades may already have gone out live, and they
never happened there. On Solana the trades channel can then send one retract frame per
lost slot, after the trades it names, usually 10–40 s after them:
Remove the rows with these ids. 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. Never handle a frame type you do not know as a trade. On
candles the same event can bring a fresh snapshot, its candles built again without the
lost slot; token, launchpad and wallet send nothing new for it.
Query Parameters
Response
Switching protocols