api.liquidations.list
List auto-liquidations draining the org's virtual accounts: the automatic conversion and on-chain settlement of deposits into accounts that carry a liquidation target. Seismic registers each liquidation when it is first reported and advances its status forward as it settles (pending / processing / sent → completed, or refunded / failed when the payout bounces), so a liquidation that never completes is still visible here. The read-side twin of the account.deposit_liquidated webhook event: each entry's id matches the event's liquidation.id, so the surfaces reconcile. Newest first. Optionally filter by account, customer, or funding deposit.
const = await ..();
// Liquidations draining a single virtual account.
const = await ..({
: "7c1d2a90…",
});
// The liquidation that settled one specific deposit.
const = await ..({
: "3628c1c7…",
});Arguments
| Param | Type | Notes |
|---|---|---|
account_id | string? | Narrow to a single drained account. |
customer_id | string? | Narrow to a single customer. |
deposit_id | string? | Narrow to the liquidation(s) of one deposit. |
limit | integer (1–200, default 50)? | Page size. |
cursor | string? | Opaque cursor from the prior page's next_cursor. |
Returns: Promise<AccountLiquidation[]>. See Liquidation fields for the shape. status is the liquidation's lifecycle state and status_reason (usually absent) carries the reported explanation for it. created_at is when Seismic registered the liquidation. deposit_id links back to the funding deposit on api.deposits.list, and transaction_hash / destination_address / destination_chain describe the on-chain settlement of the proceeds.
REST endpoint: GET /liquidations.