For the complete documentation index, see llms.txt. This page is also available as Markdown.

builderLiquidations

Stream live liquidation fills of your users. Based on last touch attribution, if the last non-liquidation fill for that coin had your builder code, the liquidation will be broadcast to your channel.

Every live data message includes both routing identifiers with the same value:

{"type": "builderLiquidations", "channel": "builderLiquidations"}

Other payload fields are omitted above. Existing clients may continue routing on either field.

Note: TWAP fills do not carry builder codes. If a user's last fill before liquidation was a TWAP fill, no builder liquidation notification will be sent.

💧New endpoint - this endpoint is not part of the original Hyperliquid API. Hydromancer added it for builder convenience.

Subscribe

{ 
  "type": "subscribe", 
  "subscription": { 
    "type": "builderLiquidations", 
    "builder": "0x..", // your builder address
    "aggregateByTime": true
  }
}

Parameters

Parameter
Type
Required
Default
Description

builder

string

Yes

-

Your builder address

dex

string

No

null

Filter by DEX: "xyz", "main" ( for fills only on first dex)

aggregateByTime

boolean

No

true

Aggregate multi-fill liquidations by (user, time, order_id)

Unsubscribe

note: make sure to use exactly the same message as subscription message.

Liquidation data format

Reconnection Note: When reconnecting with a session, replay and live events may overlap. Deduplicate using (time, txIndex) - skip liquidation fills where this tuple is at or before your last processed fill. See Session Management for details.

Each message contains an array of liquidation fills. Each fill is a tuple of [user_address, fill_data].

Examples

Error messages:

Common errors

Last updated