Every WebSocket connection starts with a subscribe message. The filters you choose determine which events you receive.Documentation Index
Fetch the complete documentation index at: https://hypernode-docs.polynode.dev/llms.txt
Use this file to discover all available pages before exploring further.
By use case
Whale tracking
See every order placed on HyperLiquid. Filter client-side by notional size."order" matches: order, order_filled, order_canceled, order_rejected.
Volume: ~2,000 events/sec across all assets.
Track a specific wallet
Copy trading
Market making signals
Pre-consensus cancels and modifications tell you the order book is about to change.All activity on one asset
Liquidation monitoring
event.type === "order_rejected" and check event.data.status for margin rejections.
Prediction markets
Full firehose
Multiple subscriptions
You can send multiple subscribe messages on one connection. Each creates a separate subscription. Events matching any subscription are delivered.Unsubscribe
Quick reference
| Goal | Filters |
|---|---|
| Track a wallet (all activity) | addresses only |
| Track a wallet (trades only) | addresses + action_types: fill |
| Track an asset (orders + fills) | assets + action_types: order, fill |
| Early cancel signal | assets + action_types: cancel, batchModify |
| Liquidation signals | action_types: order, filter client-side |
| Prediction markets | assets with # prefix |
| Everything (firehose) | no filters |