Skip to main content
Liquidation events as our indexer publishes them: one frame per liquidated position, already aggregated across the liquidators that absorbed it.

Subscribe

The subscription name is plural, liquidations. The singular is refused with {"type":"error","message":"Unsupported subscription: liquidation"}. Data frames, on the other hand, carry the singular "type": "liquidation".
Connection, authentication and heartbeat are the same for every stream, see the WebSocket overview. The subscription is acknowledged with {"channel":"subscriptionResponse","data":{"method":"subscribe","subscription":{...}}}, then frames start arriving.

A real frame

Captured on 19 September 2026, trimmed to its first row:
count is the number of rows in data, not a running total.

Filters

All filters are optional and can be combined.
An invalid users value is refused with an error frame and no subscription: {"type":"error","message":"liquidations: 'users' must be a non-empty list of 0x-prefixed addresses"}, or "... accepts at most 50 addresses".

Unsubscribe

From the shell

Historical liquidations

Right after the acknowledgement, the server sends one liquidation frame with the most recent events it holds in cache, filtered like the stream: up to 200, newest first. The cache empties after ten minutes without any liquidation, so this first frame can have count: 0. There is no longer replay: for anything older, use GET /liquidations/, which serves liquidations since 22 March 2025.