When to use WebSocket
Use streams for monitoring, alerts, and pre-trade checks; use REST for history and ad-hoc queries. Do not replace stream with aggressive polling.
Guide
WebSocket is the right production path for live quotes. This guide covers subscribe payloads, message types, and REST vs stream roles.
Use streams for monitoring, alerts, and pre-trade checks; use REST for history and ad-hoc queries. Do not replace stream with aggressive polling.
After connecting to /api/v1/market/stream, send action=subscribe with market and symbols. Symbol count is plan-capped.
Expect subscribed ack, then type=tick frames. Errors arrive as type=error with a code such as WS_CONN_LIMIT.
Handshake counts toward quota/RPM; ticks are not metered per message. Connection and symbol caps apply by plan.
See /docs/api/stream and the WebSocket vs REST glossary entry.