Credit Cost
1 per minute
Processing
Realtime
- Wire-compatible with
wss://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
Your GoldRush API key. Passed as a query parameter at connection time - no
Authorization header is used.Subscribe
Send this JSON message after the connection is established:Always
"subscribe".Example
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
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.
Always
"orderUpdates".Array of order lifecycle events from the same HyperCore block. Each entry carries its own
user field, so a single push can contain events for multiple subscribed wallets.Related endpoints
userNonFundingLedgerUpdates
stream real-time non-funding ledger events (deposits, withdrawals, vault and staking activity) for one or…