Market WebSocket
Use Market WebSocket when your app needs one hosted market socket for live price updates, rolling short-range OHLCV candles, and explicit stream-status signals under the same API key model as the rest of the public product.
This is the product-level stream surface. Use raw RPC WebSocket only when you need native chain subscriptions.
Access
Endpoint source
Auth header
Authorization: Bearer {API_KEY}Surfaces
wsChain focus
EVM family primaryHighlights
- One hosted WebSocket connection for live price, OHLCV, and stream-status updates.
- Connection, price, OHLCV, and stream-status pages now live under this family.
How to use the stream tree
Connect once
Open the hosted websocket endpoint and send the bearer header during upgrade.
Start with one price target
Confirm the first MARKET_PRICE event before widening into more targets.
Handle status events early
Wire explicit status events before production rollout so retry and fallback paths are visible from day one.
Child pages
- Connect: open the endpoint, pass bearer auth, and send the first subscribe frame.
- Price streams: review the
MARKET_PRICEevent envelope and payload. - OHLCV streams: review the rolling
candle payload for
short_range_ohlcvtargets. - Status events: handle continuity gaps, backpressure overflow, and source changes.
Where to start
- Get API Key: create one API key first, then reuse it across every hosted surface.
- Use Market WebSocket: start from the simplest integration flow.
- Market overview: return to the shared Market family before drilling into one stream path.
- Market WebSocket overview: review the product-level stream overview before opening child pages.
Last updated on