Hyperliquid WebSocket API
Critical Rules
- WebSocket URL:
wss://hypercore.goldrushdata.com/ws?key=<GOLDRUSH_API_KEY>(note:hypercore, nothyperliquid; auth is a?key=query parameter, not anAuthorizationheader). - Wire-compatible with
wss://api.hyperliquid.xyz/wsfor shared subscription types (e.g.l2Book). - No 1000-subscription-per-IP cap. Multiplex many subscriptions on one connection.
l2Book- aggregated price-level snapshots{px, sz, n}.coinis optional - omit it to stream every asset over a single subscription. Whencoinis omitted,marketTypesdefaults to["perp"](perps only); pass["spot"],["outcome"], a mix, or["*"]to opt into spot, outcome, and any future market types.l2BookDiff- GoldRush-native L2 diff transport. Same aggregated{px, sz, n}shape asl2Book, but emits oneSnapshotper subscribed coin and then per-blockUpdatescarrying only changed levels.coinaccepts a single asset, an array of assets, or can be omitted for wildcard (samemarketTypesdefault - perps only - applies whencoinis omitted). Treatsz: "0"(withn: 0) as level removal. Not available on the public Hyperliquid WebSocket.l4Book- GoldRush-native order-level stream withuser,oid,cloid,tif, and trigger metadata per order.coinis required. Emits a singleSnapshoton subscribe, then per-blockUpdates(order_statuses+book_diffs). Not available on the public Hyperliquid WebSocket.
Available Subscriptions
Subscribe / Unsubscribe Pattern
When to use which channel
The GoldRush Hyperliquid WebSocket API is a drop-in replacement for
wss://api.hyperliquid.xyz/ws. For the channels GoldRush supports, subscription payloads, channel names, and message shapes are byte-for-byte identical to the public Hyperliquid feed. The only difference is the connection URL - authentication is a required key query parameter, so no header changes are needed in your client.
Endpoint
Comparison with the public Hyperliquid WebSocket
Available subscriptions
Order book
Stream the Hyperliquid order book in real time - three channels, from aggregated L2 snapshots to full order-level (L4) detail. Omitcoin on l2Book or l2BookDiff to stream every asset on a single subscription, which the public WebSocket’s 1000-subscription-per-IP cap makes impractical.
Wallet activity
Note: Looking forcandle,trades,bbo, orallMids? These public Hyperliquid market-data channels aren’t mirrored on the GoldRush WebSocket - use the GoldRush equivalents instead:
- OHLCV candles - the Info API
candleSnapshotendpoint for historical candles, or the Streaming API OHLCV Pairs / OHLCV Tokens subscriptions for real-time candles across every HIP-3/HIP-4 market. - Trade tape -
allFillsstreams every fill on HyperCore (the global trade tape);userFillsnarrows it to specific wallets. - Best bid/offer and mids - derive top-of-book from
l2Book, or read mark and mid prices for the full universe frommetaAndAssetCtxs.
Limits
No 1000-subscription-per-IP cap. Onl2Book and l2BookDiff, filter parameters are optional - omit coin to stream the full L2 book across every asset on a single subscription. The wildcard defaults to perps only (marketTypes: ["perp"]); pass ["spot"], ["outcome"], a mix, or ["*"] to opt into spot, outcome, and future market types. l2BookDiff additionally accepts an array of coin symbols for a fixed multi-asset subscription. l4Book requires coin and is one-asset-per-subscription. See Limits & Connections for details.
For richer real-time analytics (pre-decoded HyperCore fills, liquidations, vault events, OHLCV across every HIP-3/HIP-4 market), pair the WebSocket with the GraphQL Streaming API.
Moving from the public Hyperliquid WebSocket to GoldRush is one change:
- URL - replace
wss://api.hyperliquid.xyz/wswithwss://hypercore.goldrushdata.com/ws?key=.
key query parameter, so no header swap is needed in your client.
Side-by-side
wscat
Public Hyperliquid
GoldRush
JavaScript / TypeScript
Public Hyperliquid
GoldRush
Python
Public Hyperliquid
GoldRush
Behavioral notes
Things to be aware of when you cut over.Stream payloads are byte-equal, modulo live drift
Thechannel name and data shape match Hyperliquid byte-for-byte - same keys, same nesting, same value types. Numeric fields update independently on each side, so a price level may differ by tens of milliseconds, but the schema is identical.
Auth errors close the connection
A missing or invalidkey query param returns HTTP 401 on the upgrade handshake, so the WebSocket never opens. Public Hyperliquid has no auth and never rejects the handshake.
Filter parameters are optional on GoldRush
Parameters that the public Hyperliquid WebSocket requires (e.g.coin on l2Book) are optional on GoldRush. Omit them to stream the entire channel on a single subscription instead of fanning out one subscription per asset. See Limits.
Existing SDKs work after a wsUrl override
Most popular Hyperliquid SDKs accept a WebSocket base URL override - point them at wss://hypercore.goldrushdata.com/ws?key= and the rest of the SDK works unchanged. See SDK compatibility for the override snippets.
Authentication
The WebSocket API uses your standard GoldRush API key, passed as akey query parameter at connection time. The same key works against the Foundational API, the Streaming API, the Pipeline API, and the Info API. If you don’t have one yet, sign up here.
Never hardcode keys in source. Use environment variables or a secrets manager.
What you gain
- No subscription cap. No 1000-subscription-per-IP limit; multiplex hundreds of subscriptions on a single connection.
- Wildcard subscriptions. Omit filter parameters to stream the entire channel - e.g. the full L2 order book across every asset on one subscription.
- One key for everything Hyperliquid. The same API key unlocks Streaming, Pipeline, the Info API, and HyperEVM via the Foundational API.
The most popular Hyperliquid SDKs work against the GoldRush WebSocket API after a one-line URL override. Authentication is a
key query parameter on the connection URL - no header injection is needed.
JavaScript / TypeScript: nomeida/hyperliquid
Install
npm
yarn
Configure
Note: If your SDK version doesn’t expose a wsUrl option, instantiate the WebSocket client manually and pass it to the SDK, or patch the constant the SDK uses. See the override fallback below.
Manual WebSocket fallback
When the SDK doesn’t expose awsUrl knob, bypass it and drive the raw socket yourself:
Python: hyperliquid-dex/hyperliquid-python-sdk
Install
Configure
Tip: The SDK’sInfoclass manages both REST and WebSocket. If you only need WebSocket, you can skip thesession.headers.update(...)line. If you only need REST, passskip_ws=Trueinstead.
Verification
After cutover, confirm everything is wired correctly:- Diff a known subscription - subscribe to
l2Bookfor the same coin against both endpoints; the streamedchannelanddatashape (keys, nesting, types) should match exactly. - Confirm auth - remove the
keyquery parameter and confirm the WebSocket upgrade fails with HTTP401. If the socket opens, your request isn’t reaching GoldRush. - Confirm wildcard - subscribe to
l2Bookwithout acoinand confirm you receive book snapshots for multiple assets. This call would be rejected on the public Hyperliquid WebSocket.
Other SDKs
The pattern is the same for any WebSocket client: override the connection URL towss://hypercore.goldrushdata.com/ws?key=. If you run into a specific SDK that doesn’t expose a URL override, email us - we’ll publish a recipe.
Hyperliquid WebSocket rate limits
The public Hyperliquid WebSocket (wss://api.hyperliquid.xyz/ws) caps each IP at 1000 active subscriptions, and most channels require one subscription per asset - so tracking the full market means fanning out hundreds of subscriptions and risking the cap.
The GoldRush Hyperliquid WebSocket API removes that cap. It’s a drop-in replacement with no per-IP, per-key, or per-connection subscription limit, plus wildcard subscriptions that stream an entire channel over a single subscription.
No subscription cap
With no subscription limit, you can:- Open as many concurrent subscriptions as your client supports.
- Multiplex hundreds of
l2Booksubscriptions on a single connection. - Track every active wallet, market, and asset from one process.
Wildcard subscriptions
Filter parameters that the public Hyperliquid WebSocket requires are optional on GoldRush. Omit them to stream the entire channel on one subscription instead of fanning out one subscription per asset.
So a single connection can stream Hyperliquid’s full live book state without any client-side fan-out logic.
How streaming works
Messages are pushed directly from a live Hyperliquid ingestion pipeline - no polling, no cache delay. Latency from upstream Hyperliquid event to your client is dominated by network round-trip from our Tokyo nodes.Connection management
You’re not rate-limited, but a few client-side defaults are worth tuning.Reconnect sketch
TypeScript
Python
Watch out for client-side limits
GoldRush has no caps, but the rest of your stack might:- OS file descriptor limits - if you’re opening many connections in parallel, raise
ulimit -n. - Reverse proxy idle timeouts - if you’re terminating WS through nginx, HAProxy, or a cloud load balancer, set the idle timeout above your heartbeat interval (typically 60 seconds minimum).
- Browser concurrency - browsers limit WebSocket connections per origin; one connection multiplexing many subscriptions is always preferable to many connections.
Network and TLS
- HTTP/1.1 Upgrade to WSS is supported (standard WebSocket handshake).
- TLS 1.2+ required.
- Compression (
permessage-deflate) is negotiated when offered by the client.
Need higher guarantees?
Enterprise SLA, dedicated capacity, regional pinning, and on-prem options are all available. Email sales.WebSocket API Reference
allFills | Hyperliquid WebSocket API
Credit Cost: 1 per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native: No wss://api.hyperliquid.xyz/ws equivalent.
- Filters
coinandaggregateByTimeare both optional. Omitcointo stream every market. - Live-only: No historical snapshot on subscribe. For windowed history, use the Info API
userFillsByTime. - Same per-fill shape as
userFills; channel name in messages isallFills.
[address, fill] tuples. Optional coin filter narrows the stream to a single market; aggregateByTime merges partial fills of the same order in a block.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. A subscription created with{"type": "allFills", "coin": "BTC"}is a different subscription from a wildcard{"type": "allFills"}- they must be unsubscribed independently.
Streamed message
Each push haschannel: "allFills" and a fills array of [address, fill] tuples - every fill from the same HyperCore block that matches the optional coin filter, with the executing wallet as the first element of each tuple.
Related endpoints
builderFills
stream live attributed fills for one or more builder addresses in real time.liquidationFills
stream a global, market-wide feed of every liquidation fill on HyperCore.userFills
stream real-time trade fills for one or more wallets as they execute on HyperCore. Last reviewed: 2026-06-19builderFills | Hyperliquid WebSocket API
Credit Cost: 1 per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native: No wss://api.hyperliquid.xyz/ws equivalent.
- Pass
builder(string) for a single builder oraddresses(string[]) for many.aggregateByTimeoptional. - Live-only: No historical snapshot on subscribe. For windowed history, use the Info API
builderFillsByTime. - Same per-fill shape as
userFills, plusbuilderandbuilderFeeon every entry; channel name in messages isbuilderFills.
builder) or many (addresses) and receive every fill routed through those builders as they execute, batched per block as [address, fill] tuples. Each fill carries the matched builder address and the corresponding builderFee.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established. Provide eitherbuilder (single address) or addresses (array of addresses).
Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. A subscription created withbuilder: "0xAAA"is a different subscription from one created withaddresses: ["0xAAA"], even if they target the same builder. To narrow a multi-builder set, unsubscribe the original list in full, then resubscribe with the smaller list.
Streamed message
Each push haschannel: "builderFills" and a fills array of [address, fill] tuples. The first element of each tuple is the trader who executed the fill; the fill object carries the trade details, including the builder it was routed through and the builderFee earned.
Errors
A missing or malformedbuilder/addresses field returns an error message on the same channel:
Related endpoints
allFills
stream every fill on HyperCore in real time for global market analytics and cross-wallet order-flow…liquidationFills
stream a global, market-wide feed of every liquidation fill on HyperCore.userFills
stream real-time trade fills for one or more wallets as they execute on HyperCore. Last reviewed: 2026-06-19l2BookDiff | Hyperliquid WebSocket API
Credit Cost: 0.1 per coin per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native.l2BookDiffis not exposed onwss://api.hyperliquid.xyz/ws. Pointing a client at the public endpoint with this subscription type will fail.
- Snapshot, then diffs. The first message is always a
Snapshot; every message thereafter is anUpdates. Clients must seed local book state from the snapshot and apply diffs from there. On reconnect, drop local state and re-seed from the next snapshot. coinis optional. Omit it to stream the entire L2 order book across every asset on a single subscription.- When
coinis omitted, the optionalmarketTypesfilter selects which market families to include. It defaults to["perp"]only. - Pass
"marketTypes": ["spot"], or"marketTypes":["outcome"], or a mix (e.g."marketTypes": ["perp","spot"]), or use the wildcard"marketTypes": ["*"]to opt into spot, perps, outcome, and any future market types. - No 1000-subscription-per-IP cap - multiplex hundreds of
l2BookDiffsubscriptions on a single connection. - For OHLCV candles instead of raw book state, use the Streaming API OHLCV streams.
coin is omitted, a credit rate of 10 credits per minute subscribed is applied.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
Pick the subscription shape that matches the coverage you want. Every subscription starts with oneSnapshot per coin in scope, then per-block Updates carrying only changed levels:
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. A subscription created withYou cannot unsubscribe a partial set of coins from an existing multi-coin subscription. To narrow the set, unsubscribe the originalcoin: ["BTC", "ETH"]is a different subscription from one created withcoin: "BTC"orcoin: "ETH".
coin array in full, then resubscribe with the smaller list:
Streamed messages
Every message haschannel: "l2BookDiff". The data payload contains exactly one of two variants: a Snapshot (emitted once per subscribed coin, immediately after subscribe) or an Updates (emitted on each subsequent HyperCore block where the book for at least one subscribed coin changed).
Initial snapshot
After subscribe, the server emits oneSnapshot message per coin currently in scope. For a single-coin subscription that is one message; for a list or wildcard subscription that is one message per asset. Each entry in levels[0] (bids) and levels[1] (asks) is an aggregated price level, sorted best-first.
Incremental updates
Subsequent messages carry only the levels that changed since the previous block, grouped by coin. A level entry withsz: "0" and n: 0 means the level at that price has been removed; any other entry replaces the current state at that px with the new {sz, n}.
Response fields
Related endpoints
l2Book
Subscribe to real-time L2 order book snapshots for all Hyperliquid assets over WebSocket. Last reviewed: 2026-06-16l2Book | Hyperliquid WebSocket API
Credit Cost: 0.5 per coin per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-compatible withwss://api.hyperliquid.xyz/wsl2Booksubscriptions - same channel name, samelevelsshape.
coinis optional on GoldRush. Omit it to stream the entire L2 order book across every asset on a single subscription. The public Hyperliquid API requirescoinand locks each subscription to one asset at a time.- When
coinis omitted, the optionalmarketTypesfilter selects which market families to include. It defaults to["perp"]only. - Pass
"marketTypes": ["spot"], or"marketTypes":["outcome"], or a mix (e.g."marketTypes": ["perp","spot"]), or use the wildcard"marketTypes": ["*"]to opt into spot, perps, outcome, and any future market types. - No 1000-subscription-per-IP cap - multiplex hundreds of
l2Booksubscriptions on a single connection. - For OHLCV candles instead of raw book state, use the Streaming API OHLCV streams.
coin is omitted, a credit rate of 50 credits per minute subscribed is applied.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
Pick the subscription shape that matches the coverage you want:wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. A subscription created withYou cannot unsubscribe a partial set of coins from an existing multi-coin subscription. To narrow the set, unsubscribe the originalcoin: ["BTC", "ETH"]is a different subscription from one created withcoin: "BTC"orcoin: "ETH".
coin array in full, then resubscribe with the smaller list:
Streamed message
Each message haschannel: "l2Book" and a data payload with the current book snapshot for the subscribed coin.
Related endpoints
l2BookDiff
Subscribe to real-time L2 order book (initial snapshot + diffs) for all Hyperliquid assets over WebSocket. Last reviewed: 2026-06-16l4Book | Hyperliquid WebSocket API
Credit Cost: 2 per coin per minute (except BTC which is 20 per minute) Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native.l4Bookis not exposed onwss://api.hyperliquid.xyz/ws. Pointing a client at the public endpoint with this subscription type will fail.
- Perps only. No spot assets.
coinis required. Unlikel2Bookandl2BookDiff, you cannot omitcointo stream every asset. Open one subscription per asset.- Snapshot, then diffs. The first message is always a
Snapshot; every message thereafter is anUpdates. Clients must seed local book state from the snapshot and apply diffs from there. On reconnect, drop local state and re-seed from the next snapshot. - Per-order detail. Each entry exposes
user,oid,cloid,tif, and trigger metadata - enabling queue-position reconstruction, per-trader flow attribution, and microstructure analytics that are not possible withl2Book. - See the L4 Order Book recipe for patterns to maintain book state, attribute flow by
user, or reconstruct aggregated price levels.
"coin":"BTC" is used, a credit rate of 20 credits per minute subscribed is applied.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Streamed messages
Every message haschannel: "l4Book". The data payload contains exactly one of two variants: a Snapshot (emitted once, immediately after subscribe) or an Updates (emitted on each subsequent HyperCore block where the book for coin changed).
Initial snapshot
The first message after subscribe carries the full resting book at the current block. Each entry inlevels[0] (bids) and levels[1] (asks) is an individual order - not an aggregated price level.
Incremental updates
Subsequent messages carry only what changed since the previous block.order_statuses describes order lifecycle events (open, etc.); book_diffs carries the corresponding price-level changes.
Response fields
Order object
The Order type appears insideSnapshot.levels[*][*] and Updates.order_statuses[*].order.
Last reviewed: 2026-06-24
liquidationFills | Hyperliquid WebSocket API
Credit Cost: 1 per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - GoldRush-native: No wss://api.hyperliquid.xyz/ws equivalent. The public WebSocket exposes per-wallet fills only; detecting liquidations there would require subscribing to every wallet and filtering.
- Global stream: Every liquidation fill on HyperCore, across every wallet, on a single subscription. No
addressesfilter is accepted. - Every fill in this stream carries a non-null
liquidationobject. The rest of the payload mirrorsuserFills. - Live-only: No historical snapshot on subscribe. For historical liquidations, query the Streaming API
HypercoreLedgerEventtype.
userFills, with the liquidation object populated (with liquidatedUser, markPx, method) on every entry.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Streamed message
Each push haschannel: "liquidationFills" and a fills array of [address, fill] tuples. The address is the wallet whose order was filled (i.e. the liquidator’s counterparty); liquidation.liquidatedUser is the wallet whose position was liquidated.
Related endpoints
allFills
stream every fill on HyperCore in real time for global market analytics and cross-wallet order-flow…builderFills
stream live attributed fills for one or more builder addresses in real time.userFills
stream real-time trade fills for one or more wallets as they execute on HyperCore. Last reviewed: 2026-06-16orderUpdates | Hyperliquid WebSocket API
Credit Cost: 1 per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-compatible withwss://api.hyperliquid.xyz/wsorderUpdatessubscription - same channel name, same per-update shape.
- Up to 1,000 wallet addresses per subscription. Use
addresses(string[]); aliasesuser(string) andusers(string[]) are also accepted. - Messages are batched per HyperCore block; each push carries one or more
updatesentries, each with its ownuserfield. Subscribe many wallets and receive one push per block containing every matching wallet’s events. - Live-only — no historical snapshot of resting orders on subscribe. For the current resting-order set, use the Info API
frontendOpenOrders. For historical fills, useuserFillsByTime. - No 1,000-subscription-per-IP cap. Multiplex many
orderUpdatessubscriptions on a single connection.
updates array of objects, each tagged with the originating user.
Supports up to 1,000 wallet addresses per subscription.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. A subscription created with addresses: ["0xAAA", "0xBBB"] is a different subscription from two single-address subscriptions. To narrow the set, unsubscribe the original list in full, then resubscribe with the smaller list.
Streamed message
Each push haschannel: "orderUpdates" and an updates array of objects - every order lifecycle event from the same HyperCore block that matches any subscribed wallet. Each entry is self-tagged with the originating user.
Related endpoints
userNonFundingLedgerUpdates
stream real-time non-funding ledger events (deposits, withdrawals, vault and staking activity) for one or… Last reviewed: 2026-06-18userFills | Hyperliquid WebSocket API
Credit Cost: 1 per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-compatible withwss://api.hyperliquid.xyz/wsuserFillssubscription - same channel name, same per-fill shape.
- Up to 1,000 wallet addresses per subscription. Use
addresses(string[]); aliasesuser(string) andusers(string[]) are also accepted. - Messages are batched per HyperCore block as
[address, fill]tuples; subscribe many wallets, receive one push per block per wallet that had activity. - Live-only - no historical snapshot on subscribe. For windowed history, use the Info API
userFillsByTime. - No 1,000-subscription-per-IP cap. Multiplex many
userFillssubscriptions on a single connection.
[address, fill] tuples.
Supports up to 1,000 wallet addresses per subscription.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. A subscription created with addresses: ["0xAAA", "0xBBB"] is a different subscription from two single-address subscriptions. To narrow the set, unsubscribe the original list in full, then resubscribe with the smaller list.
Streamed message
Each push haschannel: "userFills" and a fills array of [address, fill] tuples - all fills from the same HyperCore block that match any subscribed wallet.
Related endpoints
allFills
stream every fill on HyperCore in real time for global market analytics and cross-wallet order-flow…builderFills
stream live attributed fills for one or more builder addresses in real time.liquidationFills
stream a global, market-wide feed of every liquidation fill on HyperCore.userNonFundingLedgerUpdates
stream real-time non-funding ledger events (deposits, withdrawals, vault and staking activity) for one or… Last reviewed: 2026-06-16userNonFundingLedgerUpdates | Hyperliquid WebSocket API
Credit Cost: 1 per minute Processing: RealtimeTip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Wire-compatible withwss://api.hyperliquid.xyz/wsuserNonFundingLedgerUpdatessubscription - same channel name, samedeltashape per event.
- Up to 1,000 wallet addresses per subscription. Use
addresses(string[]); aliasesuser(string) andusers(string[]) are also accepted. - Covers everything that moves USDC or token balances except funding payments - deposits, withdrawals, transfers, liquidations, vault actions, staking, rewards.
- Live-only:
isSnapshotis alwaysfalseon this transport. For windowed history, use the Info APIuserNonFundingLedgerUpdates.
{time, hash, delta} entries where delta.type identifies the event class and the remaining delta fields are type-specific.
Supports up to 1,000 wallet addresses per subscription.
Endpoint
Authorization header is used.
Subscribe
Send this JSON message after the connection is established:Example
wscat
TypeScript
Python
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Note: Unsubscribe matches subscriptions by exact body. To narrow the wallet set, unsubscribe the original addresses list in full, then resubscribe with the smaller list.
Streamed message
Each push haschannel: "userNonFundingLedgerUpdates" and a data object keyed to a single wallet. Multi-wallet subscriptions receive one push per affected wallet.
Delta types
delta.type is one of:
The remaining keys on
delta vary by type and follow the public Hyperliquid info API userNonFundingLedgerUpdates payload. Common fields include amount (decimal string), usdcValue (decimal string), coin (string), destination / source (address strings), and nativeTokenFee (decimal string).
Related endpoints
orderUpdates
stream real-time order lifecycle events (placements, fills, cancels, and rejections) for one or more wallets…userFills
stream real-time trade fills for one or more wallets as they execute on HyperCore. Last reviewed: 2026-06-17Recipes
Thel2Book channel on wss://hypercore.goldrushdata.com/ws?key= is wire-equal to the public Hyperliquid feed but with coin made optional and the per-IP subscription cap removed. This recipe shows how to turn that stream into common trading and analytics building blocks. For the raw subscription shape see the l2Book reference; for the connection model see the WebSocket API overview.
What you get
- Complete snapshots, not diffs. Every
l2Bookmessage contains the currenttime,coin, and a full[bids, asks]tuple in best-first order, withpx/sz/nper level. Consume each message in isolation - no sequence numbers to track, no diff replay buffer, no REST snapshot to bootstrap. - Self-healing on packet loss. Drop a message, reconnect mid-session, or restart your process - the next message arrives with the full book state, so your in-memory view is correct on the very next tick.
- Upstream-compatible aggregation knobs.
nSigFigsaccepts2,3,4,5, ornull(full precision).mantissaaccepts1,2, or5, and is only valid whennSigFigsis5. - Wildcard coverage. Omit
cointo stream every asset’s book over a single subscription, instead of fanning out one subscription per asset. The wildcard defaults to perps only (marketTypes: ["perp"]); pass["spot"],["outcome"], a mix, or["*"]to opt into spot, outcome, and future market types.
Subscribe and hold book state
The pattern below keeps aMap in memory. Each incoming message replaces the entry for its coin, so the map is always current and never needs reconciliation.
TypeScript
Python
Patterns
Top-of-book tracker
Readbids[0] and asks[0] directly from each message. The spread is Number(asks[0].px) - Number(bids[0].px). No state required - every message is self-contained, so a single-line transformation gives you a live ticker.
Depth-weighted mid quote
Sumpx * sz across the first K levels on each side, then average. This produces a fair-value mid that’s robust to thin top-of-book liquidity, and is useful as a hedging or pricing reference.
TypeScript
Slippage / impact estimator
Walk levels on the relevant side until cumulativesz covers the requested notional. Return the size-weighted average fill price - the difference vs the top-of-book is your expected slippage.
TypeScript
Liquidity heatmap
On each message, append[time, coin, side, px, sz] rows to your time-series store (Clickhouse, TimescaleDB, Parquet). Because every message is a complete snapshot of the top levels, the heatmap rebuilds correctly from any contiguous slice of history - you don’t need a separate “initial book” record to seed the visualisation.
Handling reconnects
Reconnect logic is a one-liner: open a new socket and resend the samesubscribe payload. The first message after subscribe is a full book snapshot, so your books map is correct on the next tick - there’s nothing to replay, nothing to buffer, and no sequence numbers to reconcile against a separately-fetched REST snapshot.
TypeScript
Related
l2BookAPI reference - full subscription and message schema.- WebSocket API overview - endpoint URL, auth, and limits.
clearinghouseState- pair the live book with per-account position and margin state.- OHLCV pairs stream - candles instead of raw book state.
The
l2BookDiff channel on wss://hypercore.goldrushdata.com/ws?key= is a GoldRush-exclusive stream - it has no equivalent on wss://api.hyperliquid.xyz/ws. After subscribing, the server emits one Snapshot per subscribed coin, then per-block Updates carrying only the price levels that changed. The shape per level is the same {px, sz, n} you already get from l2Book, so book-state code only needs to learn how to apply diffs - and coin accepts a single asset, a list, or can be omitted to stream every asset on one subscription. For the raw subscription shape see the l2BookDiff reference; for the connection model see the WebSocket API overview.
What you get
- Snapshot + diff transport. One full
Snapshotper subscribed coin on subscribe, then per-blockUpdatescontaining only the levels that changed. Apply diffs to local state. - Aggregated
{px, sz, n}shape. Identical tol2Booklevels - reuse your existing aggregated-book types and just add a level-apply function. - Multi-coin / wildcard friendly.
coinaccepts a single asset, an array of assets, or can be omitted to stream every asset on one subscription. Whencoinis omitted,marketTypesdefaults to["perp"]- pass["spot"],["outcome"], a mix, or["*"]to opt into spot, outcome, and future market types.l4Bookis one-coin-per-subscription;l2Bookrequires per-asset fan-out on the public feed. - Bandwidth proportional to change. Quiet markets cost almost nothing; only the levels that actually moved arrive over the wire, instead of a full re-snapshot every tick.
- GoldRush-exclusive. Public Hyperliquid has no L2-diff transport -
l2Bookis full-snapshot only.
Subscribe and maintain book state
The pattern below keeps aMap, asks: Map }>. Each Snapshot seeds the per-coin entry; each book_diff inside Updates either deletes a level (when sz === "0") or replaces it with the new {sz, n}.
TypeScript
Python
Patterns
Single coin, list, or wildcard
All three subscription shapes share the same handler - only the payload sent atsubscribe time changes. Use whichever matches your coverage requirements.
TypeScript
Snapshot per live coin before diffs begin, so the books map fills in over the first few messages rather than all at once. marketTypes is only valid when coin is omitted; it defaults to ["perp"], so spot and outcome markets require explicit opt-in. A second subscribe with a different marketTypes value replaces the previous filter rather than coexisting with it.
Reconstruct a top-of-book stream
After each diff is applied, the best bid is the highestpx in book.bids and the best ask is the lowest px in book.asks. Emit only when the top level changes to avoid noise.
TypeScript
Related
l2BookDiffAPI reference - full subscription, snapshot, and update schema.l2Bookreference - full-snapshot transport when diff replay isn’t desirable.l4Bookreference - order-level stream withuser,oid,cloid,tif, and trigger metadata.- WebSocket API overview - endpoint URL, auth, and limits.
The
l4Book channel on wss://hypercore.goldrushdata.com/ws?key= is a GoldRush-exclusive stream - it has no equivalent on wss://api.hyperliquid.xyz/ws. After subscribing, the server sends a single Snapshot of every resting order, then per-block Updates carrying lifecycle events and per-order book changes. Each order arrives with its user, oid, cloid, tif, and trigger metadata, so you can reconstruct queue position and price-time priority, attribute flow to specific wallets, and run microstructure analytics that l2Book’s aggregated {px, sz, n} view hides. For the raw subscription shape see the l4Book reference; for the connection model see the WebSocket API overview.
What you get
- Per-order visibility. Every level in the snapshot is an individual order keyed by
oid, withuser,cloid,tif,orderType, and trigger metadata attached.l2Bookonly exposes{px, sz, n}per price level. - Snapshot + diff transport. One full
Snapshoton subscribe, then per-blockUpdatescontainingorder_statuses(lifecycle events) andbook_diffs(per-order changes). Apply diffs to local state. - Per-block cadence. Updates fire on each HyperCore block where the book for the subscribed
coinchanged. Thetimeandblock_heightfields anchor each message to a specific block. - GoldRush-exclusive. Not available on the public Hyperliquid WebSocket - this stream surfaces user attribution and per-order metadata the public feed never exposes.
- One coin per subscription. Unlike
l2Book,coinis required. To cover multiple assets, open onel4Booksubscription per asset on the same connection.
Subscribe and maintain book state
The pattern below keeps aMap per coin. The snapshot seeds the map; each Updates message applies book_diffs against it. Reconnects drop the map and re-seed from the next snapshot.
TypeScript
Python
Patterns
Track individual orders by oid
oid is the Hyperliquid order id, stable for the lifetime of the order - use it as the primary key in your local map. cloid is the client-supplied id (may be null); index on it when you need to correlate fills back to a specific trading bot’s instructions.
Per-user flow attribution
Every order entry carriesuser. Group orders by wallet to surface market-maker behavior, identify spoofing patterns, or build a per-trader heatmap of resting size. Pair this with clearinghouseState for per-user position and margin context.
TypeScript
Reconstruct aggregated price levels
If a downstream consumer expects anl2Book-style aggregated view, sum sz across all orders sharing a limitPx on the same side. Going the other way isn’t possible - l2Book collapses the per-order detail you’d lose.
TypeScript
Handling reconnects
On reconnect, resend the samesubscribe payload. The first message back is always a fresh Snapshot - drop your local orders map and re-seed from it. Do not attempt to replay missed Updates - the snapshot is authoritative and supersedes anything you held before the disconnect.
TypeScript
Related
l4BookAPI reference - full subscription, snapshot, and update schema.l2Bookreference - aggregated price-level snapshots when per-order detail isn’t needed.- WebSocket API overview - endpoint URL, auth, and limits.
clearinghouseState- pair per-user resting orders with position and margin state.