Use cases
Mirror a wallet
Follow a wallet and copy its moves in real time. See its trades the moment
they land onchain.
Wallet alerts
Get a signal whenever a wallet you watch buys, sells, or moves money.
Whale watching
See big trades. Stream only fills above a USD amount you pick.
Market monitoring
Watch open interest, liquidity, and price ticks for every market. No need to
poll the REST API.
Resolution tracking
Listen for oracle events to know the second a market resolves.
Mempool / early visibility
Get pending transactions from the Polygon mempool, before they are in a
block.
Endpoint
X-API-Key header of the WebSocket upgrade request. See Authentication for the details and safety tips.
One connection can hold many subscriptions, and you can mix confirmed and
pending subscriptions. How many connections and subscriptions you may open
depends on your plan.
Quickstart
- Connect — open the socket with your
X-API-Keyheader. - Subscribe — send a
subscribemessage with the channel name (and filters if you want). - Receive — read the JSON frames that come back. Each one has a
type, achannel, and adatapayload.
Channels at a glance
| Channel | Purpose |
|---|---|
trading | Order fills, matches, cancels, preapprovals, and trading pauses. |
fees | Exchange fees charged on trades. |
oracle | UMA Adapter and UMA Optimistic Oracle question events. |
resolution | Condition resolutions, reported results, and resolution pauses. |
lifecycle | Market, event, condition, and token preparation. |
positions | CTF base-layer splits, merges, and payout redemptions. |
combos | Module, neg-risk, combinatorial, bridge, and migration position events. |
transfers | ERC-1155 outcome-token transfers. |
accounts | Proxy and deposit wallet creation. |
wallets | Events that touch one or more wallet addresses. |
markets | Events that touch market ids or token ids. |
trading with a min_usd filter.
Connection lifecycle
- Open — start the WebSocket connection with your API key in the upgrade header.
- Authenticate — Radion checks the key and accepts the connection. A bad key returns HTTP
401. - Subscribe — send one or more
subscribemessages to start getting frames on the channels you name. - Receive frames — handle the JSON event and control frames until you are done or an error happens.
- Reconnect — if the connection drops, connect again with exponential back-off, then send your subscriptions again. See Connection state for heartbeat and reconnect tips.
Further reading
Examples
Ready-to-run Node.js + TypeScript examples for every channel.
Authentication
Put your API key in the upgrade request.
Subscribe
Subscribe, unsubscribe, and ping messages.
Channels
Full channel list with typed schemas.
Filters
Narrow a channel to wallets, markets, tokens, or size.
Frames
Event, control, and error frame shapes.
Mempool
Pending transactions before they are in a block.
Connection state
Reconnect, heartbeats, and the health endpoint.
Rate limits
Connection and subscription limits per plan.
Limitations
What the WebSocket streams do and do not promise.