Skip to main content
Real-time market data means live subscription behavior. Reach for it when REST snapshots and historical replay are the wrong primitives. Real-time WebSocket is the right surface when the application needs continuing updates: live dashboards, monitors, alerts, local order-book state, or agent workflows that watch a bounded market. Use REST when you need one response. Use WebSocket replay when the job needs historical stream order.

​
Real-Time Fit

​
Subscription Design

1

Choose route family

Pick Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before choosing a channel.
2

Choose one channel and symbol

Start with the minimum channel-symbol pair that confirms the consumer can keep up.
3

Handle state changes

Track snapshots, updates, gaps, unsubscribe events, reconnects, and local state rebuilds.
4

Observe lag

Watch consumer lag, message queue depth, reconnect count, and gap events before widening.

​
Live Subscription Checklist

Use this checklist before opening or regenerating a live subscription.

​
Real-Time Safety

Do not subscribe to every channel by default. A broad subscription set can create local backlog, stale UI, duplicate reconnect subscriptions, or incorrect local books even if the server accepts the connection. Record active subscriptions as application state, not as unreviewed prompt text. If an alert or model depends on a real-time stream, pair the stream with data-quality behavior. The stream client should know what to do when a gap appears, when reconnect occurs, or when freshness falls outside the job tolerance.

​
Agent Prompt Shape

​
Next Step

Use WebSocket channels for channel examples, Keep alive for reconnect behavior, and WebSocket L4 order book when the stream maintains order-level book state.
Last modified on June 28, 2026