Skip to main content
Clients can use the stream to receive:
  • Blocks applied by the node
  • Per-coin order book diffs
  • Mempool transactions, when enabled
  • Timing metrics
  • Low-latency ping frames
  • Server-side error events
The service is designed for teams that need fast and reliable Hyperliquid data for execution systems, trading infrastructure, monitoring, research, and latency-sensitive workflows.

​
How it works

Hyperliquid Data Stream runs as a WebSocket service in front of a Hyperliquid node. Clients connect to the provided endpoint, subscribe to the required data streams, and receive real-time updates as soon as they are available from the node. The service supports two modes: JSON mode is useful for a quick smoke test. For production, use binary mode.

​
Endpoint

Hyperliquid Data Stream speaks WebSocket over plain TCP.
The endpoint URL is provided during onboarding. Important: The service uses ws://, not wss:/.

​
Access control

Access is granted per source IP at the network layer. If a client’s egress IP changes, the new IP must be added to the allowlist. Otherwise, the TCP connection may hang or time out.

​
Limits

Related topics

Getting StartedProtocol ReferenceOperational Notes