WebSocket channels

Channels identify the stream you want. Symbols identify the market inside that channel’s venue family.

Lighter live subscriptions are available on lighter_orderbook, lighter_trades, lighter_open_interest, and lighter_funding through wss://api.0xarchive.io/ws. lighter_candles and lighter_l3_orderbook are replay-only, and all six Lighter channels support historical replay. See Lighter WebSocket channels for live message shapes.Lighter on Robinhood Chain live subscriptions are available on rh_lighter_orderbook, rh_lighter_trades, rh_lighter_open_interest, and rh_lighter_funding through wss://api.0xarchive.io/ws. rh_lighter_candles is replay-only, and all five Robinhood Chain channels support historical replay. See Lighter on Robinhood Chain.

Examples

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "orderbook",
  symbol: "BTC"
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "hip3_l4_diffs",
  symbol: "km:US500"
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "spot_orderbook",
  symbol: "HYPE-USDC"
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "hip4_trades",
  symbol: "#0"
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "lighter_orderbook",
  symbol: "BTC",
  interval_ms: 1000
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "lighter_trades",
  symbol: "BTC"
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "lighter_orderbook",
  symbol: "BTC",
  start: 1785193200000,
  end: 1785196800000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "lighter_trades",
  symbol: "BTC",
  start: 1785193200000,
  end: 1785196800000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "lighter_candles",
  symbol: "BTC",
  start: 1785193200000,
  end: 1785196800000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "lighter_open_interest",
  symbol: "BTC",
  start: 1785193200000,
  end: 1785196800000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "lighter_funding",
  symbol: "BTC",
  start: 1785193200000,
  end: 1785196800000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "lighter_l3_orderbook",
  symbol: "BTC",
  start: 1785193200000,
  end: 1785196800000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "rh_lighter_orderbook",
  symbol: "BTC",
  interval_ms: 1000
}));

ws.send(JSON.stringify({
  op: "subscribe",
  channel: "rh_lighter_trades",
  symbol: "AAPL-USDG"
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "rh_lighter_orderbook",
  symbol: "BTC",
  start: 1788220800000,
  end: 1788224400000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "rh_lighter_trades",
  symbol: "BTC",
  start: 1788220800000,
  end: 1788224400000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "rh_lighter_candles",
  symbol: "BTC",
  start: 1788220800000,
  end: 1788224400000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "rh_lighter_open_interest",
  symbol: "BTC",
  start: 1788220800000,
  end: 1788224400000,
  speed: 10
}));

ws.send(JSON.stringify({
  op: "replay",
  channel: "rh_lighter_funding",
  symbol: "BTC",
  start: 1788220800000,
  end: 1788224400000,
  speed: 10
}));

Unsubscribe

ws.send(JSON.stringify({
  op: "unsubscribe",
  channel: "orderbook",
  symbol: "BTC"
}));

Pick the channel family and symbol format together. A HIP-3 symbol does not belong on a Lighter channel.

Channel Selection

Choose channels the same way you choose REST route families. Hyperliquid core channels are for standard perp symbols such as BTC and ETH. Spot work should use Spot-specific route and stream context when available. HIP-3 channels keep the builder prefix, HIP-4 channels keep outcome identifiers, and Lighter channels stay under the Lighter family.

Channel Family Matrix

Use this matrix to avoid treating every WebSocket channel as the same stream.

Family	Example channels	Symbol shape	Notes
Hyperliquid core	`orderbook`, `trades`, `funding`, `open_interest`, `liquidations`, `l4_diffs`, `l4_orders`	`BTC`, `ETH`	Core perp channels use bare symbols. Trade-row `user_address` and `builder_address` fields may be null depending on source; filter them client-side. L4 channels are order-level surfaces, available on every tier.
Hyperliquid Spot	`spot_orderbook`, `spot_trades`, `spot_l4_diffs`, `spot_l4_orders`, `spot_twap`	`HYPE-USDC`, `PURR-USDC`	Spot L4 channels carry order-level diff/event updates. Initialize or recover resting-book state from the documented snapshot/checkpoint routes. The separate REST Spot order-history route contains lifecycle records. Funding, open interest, and liquidations are not Spot data families.
HIP-3	`hip3_orderbook`, `hip3_trades`, `hip3_funding`, `hip3_liquidations`, `hip3_l4_diffs`, `hip3_l4_orders`	`km:US500`, `hyna:BTC`	Preserve the builder prefix and case. Do not normalize these into ordinary perp symbols.
HIP-4	Live: `hip4_trades`, `hip4_l4_diffs`, `hip4_l4_orders`. Replay from stored history: `hip4_orderbook`, `hip4_trades`, `hip4_open_interest`	`#0`, numeric side ids, or outcome-side context	Preserve outcome and side context. Use REST for current `hip4_orderbook` and outcome-side `hip4_open_interest` reads. HIP-4 has no funding, liquidation, or dedicated candle stream.
Lighter	`lighter_orderbook`, `lighter_l3_orderbook`, `lighter_trades`, `lighter_candles`, `lighter_funding`, `lighter_open_interest`	`BTC`, `ETH`	Live: `lighter_orderbook`, `lighter_trades`, `lighter_open_interest`, and `lighter_funding`. Replay-only: `lighter_candles` and `lighter_l3_orderbook`; use REST for their current data. All six replay, and REST and exports also serve history. Keep Lighter data under the Lighter family even when the symbol text matches a Hyperliquid market.
Lighter on Robinhood Chain	`rh_lighter_orderbook`, `rh_lighter_trades`, `rh_lighter_candles`, `rh_lighter_funding`, `rh_lighter_open_interest`	`BTC`, `AAPL-USDG`	Lighter’s second deployment, with its own markets and channel family. Live: `rh_lighter_orderbook`, `rh_lighter_trades`, `rh_lighter_open_interest`, and `rh_lighter_funding`, with the mainnet Lighter live shapes. Replay-only: `rh_lighter_candles`. No L3 channel. Spot symbols are dashed with the USDG quote.

Live and replay availability

Replay availability is a channel contract, not a family-wide default. Standard timed replay emits timeline events according to speed. Core L4 uses checkpoint-anchored bulk delivery. A live channel can still have no replay path, and stored replay can remain available while current reads use REST.

Channel group	Live subscription	Historical replay	Replay delivery
Hyperliquid core standard: `orderbook`, `trades`, `candles`, `liquidations`, `open_interest`, `funding`	Yes	Yes	Timed replay; `speed` applies
Hyperliquid core context: `ticker`, `all_tickers`	Yes	No	Real-time only
Hyperliquid core full depth: `orderbook_full`	Yes	No	Real-time only
Hyperliquid core L4: `l4_diffs`, `l4_orders`	Yes	Yes	Checkpoint-anchored bulk replay; `speed` is ignored
Hyperliquid Spot: `spot_orderbook`, `spot_trades`, `spot_l4_diffs`, `spot_l4_orders`, `spot_twap`	Yes	No	Real-time only
HIP-3 standard: `hip3_orderbook`, `hip3_trades`, `hip3_candles`, `hip3_funding`, `hip3_open_interest`, `hip3_liquidations`	Yes	Yes	Timed replay; `speed` applies
HIP-3 full depth: `hip3_orderbook_full`	Yes	No	Real-time only
HIP-3 L4: `hip3_l4_diffs`, `hip3_l4_orders`	Yes	No	Real-time only
HIP-4 trades: `hip4_trades`	Yes	Yes	Timed replay; `speed` applies
HIP-4 stored L2 and OI: `hip4_orderbook`, `hip4_open_interest`	No; use REST for current reads	Yes	Timed replay from stored history
HIP-4 L4: `hip4_l4_diffs`, `hip4_l4_orders`	Yes	No	Real-time only
Lighter live: `lighter_orderbook`, `lighter_trades`, `lighter_open_interest`, `lighter_funding`	Yes	Yes	Timed replay; `speed` applies
Lighter candles: `lighter_candles`	No; use REST for current reads	Yes	Timed replay; `speed` applies
Lighter L3: `lighter_l3_orderbook`	No; use REST for current reads	Yes	Timed replay; `speed` applies
Lighter on Robinhood Chain live: `rh_lighter_orderbook`, `rh_lighter_trades`, `rh_lighter_open_interest`, `rh_lighter_funding`	Yes	Yes	Timed replay; `speed` applies
Lighter on Robinhood Chain candles: `rh_lighter_candles`	No; use REST for current reads	Yes	Timed replay; `speed` applies

For core L4, replay starts from the latest usable checkpoint at or before the requested start time. A request can be rejected when no checkpoint is available for that symbol and window. See WebSocket replay for the l4_snapshot and l4_batch event flow.

Lighter live channels

Live Lighter channels use the same subscribe command and data envelope as live Hyperliquid channels, on wss://api.0xarchive.io/ws. lighter_orderbook sends a full top-20 book at most once per interval: one book per second by default, or the rate set by the optional interval_ms subscribe field (100 to 5000). lighter_trades sends fill legs, two per trade with the same tid. lighter_open_interest and lighter_funding carry the same market-context message. Live payloads differ from the historical_data rows that Lighter replay returns, so parse them separately. See Lighter WebSocket channels for payload fields, errors, and lag notices. Lighter on Robinhood Chain live subscriptions are available on rh_lighter_orderbook, rh_lighter_trades, rh_lighter_open_interest, and rh_lighter_funding through wss://api.0xarchive.io/ws. rh_lighter_candles is replay-only, and all five Robinhood Chain channels support historical replay. The live messages use the same shapes as the mainnet channels, rh_lighter_orderbook takes the same interval_ms range, and a multi-channel replay keeps rh_lighter_* and lighter_* channels in separate commands.

Native `userFills` terminology

Native Hyperliquid userFills maps to 0xArchive trades. 0xArchive has no WebSocket channel named userFills; do not subscribe to a nonexistent fill channel. Use trades and filter the returned rows client-side when attribution is needed.

Subscription Fields

Record these fields for each active subscription.

Field	Example	Why
Venue family	Hyperliquid core, HIP-3, HIP-4, Lighter mainnet, Lighter on Robinhood Chain	Keeps route semantics tied to the stream
Channel	`orderbook`, `hip3_l4_diffs`, `hip4_trades`, `lighter_orderbook`	Names the server stream
Symbol	`BTC`, `km:US500`, `#0`	Preserves family-specific symbol format
Book interval (`lighter_orderbook` and `rh_lighter_orderbook` only)	`interval_ms: 250`	Restores the chosen book rate; a reconnect without it falls back to one book per second
Consumer	dashboard, alert, local book, replay, export writer	Sets throughput and gap tolerance
Stop condition	unsubscribe, close, replay stop, retry budget	Prevents abandoned streams

Store the checklist with active connection state. On reconnect, restore from this checklist list. On unsubscribe, remove it from the list before trusting local subscription state.

Common Channel Mistakes

Do not send a HIP-3 symbol to a Lighter channel. Do not strip a HIP-3 prefix before subscribing. Do not treat HIP-4 outcome identifiers as ordinary perp symbols. Do not add Spot pairs to a generic perp stream; use Spot channel names such as spot_orderbook and keep dashed pair symbols visible in code.

State Handling

For order books and reconstruction workflows, treat the first snapshot as the baseline and each update as an ordered change. Live lighter_orderbook is the exception: every live message is a full top-20 book, so replace local state with each message instead of applying it as a change. Store channel, symbol, timestamp, and message type with local state so a replay or reconnect can show what happened. If a gap event appears, mark the local state unsafe until it is rebuilt from a fresh snapshot or replay window.

Keep Subscriptions Bounded

Subscribe to the minimum channel and symbol set for the job, then add more only after throughput and reconnection behavior are understood. A dashboard can usually tolerate fewer channels than a backtest replay, and a backtest replay usually needs stronger gap handling than a simple monitor.

Unsubscribe And Reconnect Discipline

Subscription code should include the inverse operation. If an example subscribes, also show or link to unsubscribe behavior. Long-running clients should track active subscriptions so reconnects do not accidentally duplicate streams. Treat subscription state as application state. Expose the active channel set in debug output so stream bugs can be inspected without reproducing the whole session.

Connect

Stream

Replay

Webhooks

WebSocket channels

Examples

Unsubscribe

Channel Selection

Channel Family Matrix

Live and replay availability

Lighter live channels

Native `userFills` terminology

Subscription Fields

Common Channel Mistakes

State Handling

Keep Subscriptions Bounded

Unsubscribe And Reconnect Discipline

​Examples

​Unsubscribe

​Channel Selection

​Channel Family Matrix

​Live and replay availability

​Lighter live channels

​Native userFills terminology

​Subscription Fields

​Common Channel Mistakes

​State Handling

​Keep Subscriptions Bounded

​Unsubscribe And Reconnect Discipline

Examples

Unsubscribe

Channel Selection

Channel Family Matrix

Live and replay availability

Lighter live channels

Native `userFills` terminology

Subscription Fields

Common Channel Mistakes

State Handling

Keep Subscriptions Bounded

Unsubscribe And Reconnect Discipline