Credit Cost
1 per minute
Processing
Realtime
- GoldRush-native: No
wss://api.hyperliquid.xyz/wsequivalent. The public WebSocket exposes per-wallet fills only; attributing a liquidation to a builder there would require subscribing to every wallet and filtering. - Builder-scoped:
builderis required. The stream returns only liquidation fills whose closing order was routed through your builder code - it is the intersection ofliquidationFillsandbuilderFills. - Every entry carries a non-null
liquidationobject plus the attributedbuilder; the rest of the payload mirrorsuserFills. - TWAP caveat: TWAP fills do not carry builder codes. If a user’s last fill before liquidation was a TWAP fill, no builder liquidation is emitted for it.
builder address to receive every liquidation fill attributed to your builder code, in real time. This is the builder-attributed slice of the global liquidationFills stream: same per-fill shape as userFills, with both the liquidation object and the builder attribution populated on every entry.
Endpoint
string
required
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.builder is required.
string
required
Always
"subscribe" - GoldRush house style, matching the sibling channels. This is the only accepted form; a bare type: "subscribe" envelope is not recognized and is relayed upstream unchanged.object
required
Example
Unsubscribe
Send the samesubscription body with method: "unsubscribe":
Streamed message
Each push keeps the upstream wire shape:type: "builderLiquidations" and a liquidations array of [address, fill] tuples - it is not normalized to the channel/fills shape used by the sibling channels. The address (and mirrored user field) is the wallet whose position was liquidated; liquidation.liquidatedUser repeats it, and builder is the attributed builder code.
string
Always
"builderLiquidations".array<[string, object]>
Tuples of
[address, fill]. The address is the liquidated wallet. Same fill shape as userFills, with liquidation and builder always populated.All other fields (coin, px, sz, side, time, startPosition, dir, closedPnl, hash, oid, crossed, fee, tid, feeToken, twapId, and optional cloid) match the userFills shape.TWAP-preceded liquidations are omitted. TWAP fills do not carry builder codes, so if a user’s last fill before liquidation was a TWAP slice, GoldRush cannot attribute the liquidation to a builder and no entry is emitted on this stream. Use the global
liquidationFills stream if you need every liquidation regardless of builder attribution.Errors
A missing or malformedbuilder field returns an error message:
Related endpoints
liquidationFills
stream a global, market-wide feed of every liquidation fill on HyperCore.
builderFills
stream live attributed fills for one or more builder addresses in real time.
allFills
stream every fill on HyperCore in real time for global market analytics and cross-wallet order-flow…
userFills
stream real-time trade fills for one or more wallets as they execute on HyperCore.