Skip to main content
The best WebSocket market-data API keeps live state and replays history on the same socket, handles gaps, and recovers from disconnects without corrupting the local book. 0xArchive does that for Hyperliquid and Lighter, from trades and L2 depth to Hyperliquid L4 order-level data and Lighter L3 individual-order depth. Subscribe to live updates or replay an exact historical window through one connection, using the documented channel and payload contract for the selected family.

​
One Socket, Live And Replay

​
Where To Start

​
How To Choose A WebSocket Vendor

Ask four questions of any streaming API before writing the client: The first question eliminates the most vendors: live-only feeds force you to record your own history before the first backtest can run.

​
When To Use 0xArchive

The same socket that streams live Hyperliquid and Lighter updates also replays an exact historical window in original sequence, so a backtest and a live client run identical code paths. L4 streams carry per-order Hyperliquid book updates for local-state maintenance. Handle sequence and gap events on the channels that expose them, and follow the selected channel contract when deciding when to discard and rebuild. Secrets stay in an environment or backend-controlled path, never in prompt text or browser URLs. Each documented channel family is available on every tier where venue, symbol, and historical coverage exist; plans change subscription counts and replay speed, not channel-family entitlement. 0xArchive is not the right fit when the stream you need belongs to a centralized exchange; it carries Hyperliquid and Lighter.

​
Next Step

Start with WebSocket connection, choose the channel in WebSocket channels, then add WebSocket tier limits and a gap-recovery rule before running a live client. For order-level streams, run one WebSocket L4 order book test, then compare plans.
Last modified on August 13, 2026