> ## Documentation Index > Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt > Use this file to discover all available pages before exploring further. # user.isolated.liquidation > Lets a **main** account observe the liquidation, ADL, and LSP activity of all of its **isolated-margin subaccounts**, without subscribing to each subaccount's own `user.liquidation` channel individually. Every event on this channel is a fan-out copy of an event also delivered on the affected subaccount's own `user.liquidation` channel — the payload is identical, including `isolated: true` and the subaccount's `user_id`. The main account's *own* liquidation activity is never delivered here; it stays on the main account's regular `user.liquidation` channel. Requires the `account:read` scope on an API key belonging to the **main account**, and is only available while isolated margin is enabled on the platform. ## AsyncAPI ````yaml api-reference/coinbase-deribit-app-api/adv-starbase-asyncapi.json user.isolated.liquidation id: user.isolated.liquidation title: 'user.isolated.liquidation ' description: > Lets a **main** account observe the liquidation, ADL, and LSP activity of all of its **isolated-margin subaccounts**, without subscribing to each subaccount's own `user.liquidation` channel individually. Every event on this channel is a fan-out copy of an event also delivered on the affected subaccount's own `user.liquidation` channel — the payload is identical, including `isolated: true` and the subaccount's `user_id`. The main account's *own* liquidation activity is never delivered here; it stays on the main account's regular `user.liquidation` channel. Requires the `account:read` scope on an API key belonging to the **main account**, and is only available while isolated margin is enabled on the platform. servers: - id: private protocol: wss host: drb.coinbase.com/ws/api/v2 bindings: [] variables: [] address: user.isolated.liquidation parameters: [] bindings: [] operations: - &ref_1 id: receive_user_isolated_liquidation title: Receive user description: Client receives user notifications type: receive messages: - &ref_3 id: subscribe_request contentType: application/json payload: - name: Subscription Request description: >- Client sends subscription request to subscribe to notification channel. Please refer to [Notification page](https://deribit.mintlify.app/articles/notifications) for more information. type: object properties: - name: id type: integer description: Client request id, echoed in the response. required: true - name: jsonrpc type: string description: JSON-RPC version. Always `2.0`. required: true - name: method type: string description: >- `private/subscribe` on the private WebSocket, after `public/auth`. enumValues: - private/subscribe required: true - name: params type: object required: true properties: - name: channels type: array description: >- Stream names to subscribe to, for example `quote.BTC-PERPETUAL`. required: true properties: - name: item type: string required: false headers: [] jsonPayloadSchema: additionalProperties: false properties: id: default: 42 description: Client request id, echoed in the response. type: integer x-parser-schema-id: jsonrpc: default: '2.0' description: JSON-RPC version. Always `2.0`. type: string x-parser-schema-id: method: default: private/subscribe description: >- `private/subscribe` on the private WebSocket, after `public/auth`. enum: - private/subscribe type: string x-parser-schema-id: params: additionalProperties: false properties: channels: default: - user.isolated.liquidation description: >- Stream names to subscribe to, for example `quote.BTC-PERPETUAL`. items: type: string x-parser-schema-id: type: array x-parser-schema-id: required: - channels type: object x-parser-schema-id: required: - id - jsonrpc - method - params type: object x-parser-schema-id: title: Subscription Request description: >- Client sends subscription request to subscribe to notification channel. Please refer to [Notification page](https://deribit.mintlify.app/articles/notifications) for more information. example: |- { "id": 42, "jsonrpc": "2.0", "method": "private/subscribe", "params": { "channels": [ "user.isolated.liquidation" ] } } bindings: [] extensions: - id: x-parser-unique-object-id value: subscribe_request bindings: [] extensions: &ref_0 - id: x-parser-unique-object-id value: user.isolated.liquidation - &ref_2 id: send_subscribe_user_isolated_liquidation title: Send subscribe request description: Client sends subscription request for user type: send messages: - &ref_4 id: subscription_message contentType: application/json payload: - name: Subscription Notification Data description: Server sends subscription notification data type: object properties: - name: data type: object required: true properties: - name: amount type: number description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. required: false - name: close_out_margin type: number description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. required: false - name: commission type: number description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. The commission charged (on `lsp_transfer`/`adl_transfer`) or this account's share of the commission (on `adl_transfer_received`, proportional to the position this account absorbed). Intra-account subaccount ADL moves are commissioned the same way as moves onto another user's account. required: false - name: currency type: string description: Currency, i.e `"BTC"`, `"ETH"`, `"USDC"` enumValues: - BTC - ETH - EURR - USDC - USDT required: false - name: direction type: string description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. This account's own resulting position side. enumValues: - buy - sell required: false - name: equity type: number description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. required: false - name: initial_margin type: number description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. required: false - name: instrument_name type: string description: Unique instrument identifier required: false - name: isolated type: boolean description: >- Present and `true` only when this event applies to an isolated-margin subaccount. required: false - name: maintenance_margin type: number description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. required: false - name: margin_balance type: number description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. required: false - name: price type: number description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. The transfer price applied. required: false - name: state type: string description: > The stage of the liquidation/ADL/LSP process this notification represents: - `liquidation_started` / `liquidation_completed`: The standard (order-book) liquidation process has started or completed for this account. - `close_out_liquidation_started` / `close_out_liquidation_completed`: The LSP/ADL close-out process has started or completed for this account. An account can go through this pair, the `liquidation_started`/`liquidation_completed` pair, or both in sequence (e.g. LSP/ADL close-out first, handed off to standard liquidation if it can't fully resolve the breach). - `lsp_transfer`: A position was transferred off this account to an LSP participant. Sent to the liquidated (source) account — see the `user.lsp` channel for the notification sent to the receiving participant. - `adl_transfer`: A position was auto-deleveraged off this account. Sent to the account being deleveraged (source). - `adl_transfer_received`: A position was auto-deleveraged onto this account from a counterparty. Sent to the receiving (counterparty) account. enumValues: - adl_transfer - adl_transfer_received - close_out_liquidation_completed - close_out_liquidation_started - liquidation_completed - liquidation_started - lsp_transfer required: true - name: timestamp type: integer description: The timestamp (milliseconds since the Unix epoch) required: true - name: user_id type: integer description: Unique user identifier required: true headers: [] jsonPayloadSchema: additionalProperties: false description: Response containing notification data properties: data: additionalProperties: false properties: amount: description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. type: number x-parser-schema-id: close_out_margin: description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. type: number x-parser-schema-id: commission: description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. The commission charged (on `lsp_transfer`/`adl_transfer`) or this account's share of the commission (on `adl_transfer_received`, proportional to the position this account absorbed). Intra-account subaccount ADL moves are commissioned the same way as moves onto another user's account. type: number x-parser-schema-id: currency: description: Currency, i.e `"BTC"`, `"ETH"`, `"USDC"` enum: - BTC - ETH - EURR - USDC - USDT type: string x-parser-schema-id: direction: description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. This account's own resulting position side. enum: - buy - sell type: string x-parser-schema-id: equity: description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. type: number x-parser-schema-id: initial_margin: description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. type: number x-parser-schema-id: instrument_name: description: Unique instrument identifier example: BTC-PERPETUAL type: string x-parser-schema-id: isolated: description: >- Present and `true` only when this event applies to an isolated-margin subaccount. type: boolean x-parser-schema-id: maintenance_margin: description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. type: number x-parser-schema-id: margin_balance: description: >- Present for `liquidation_started`, `liquidation_completed`, `close_out_liquidation_started`, and `close_out_liquidation_completed`. type: number x-parser-schema-id: price: description: >- Present for `lsp_transfer`, `adl_transfer`, and `adl_transfer_received`. The transfer price applied. type: number x-parser-schema-id: state: description: > The stage of the liquidation/ADL/LSP process this notification represents: - `liquidation_started` / `liquidation_completed`: The standard (order-book) liquidation process has started or completed for this account. - `close_out_liquidation_started` / `close_out_liquidation_completed`: The LSP/ADL close-out process has started or completed for this account. An account can go through this pair, the `liquidation_started`/`liquidation_completed` pair, or both in sequence (e.g. LSP/ADL close-out first, handed off to standard liquidation if it can't fully resolve the breach). - `lsp_transfer`: A position was transferred off this account to an LSP participant. Sent to the liquidated (source) account — see the `user.lsp` channel for the notification sent to the receiving participant. - `adl_transfer`: A position was auto-deleveraged off this account. Sent to the account being deleveraged (source). - `adl_transfer_received`: A position was auto-deleveraged onto this account from a counterparty. Sent to the receiving (counterparty) account. enum: - adl_transfer - adl_transfer_received - close_out_liquidation_completed - close_out_liquidation_started - liquidation_completed - liquidation_started - lsp_transfer type: string x-parser-schema-id: timestamp: description: The timestamp (milliseconds since the Unix epoch) example: 1536569522277 type: integer x-parser-schema-id: user_id: description: Unique user identifier example: 57874 type: integer x-parser-schema-id: required: - state - timestamp - user_id type: object x-parser-schema-id: required: - data type: object x-parser-schema-id: title: Subscription Notification Data description: Server sends subscription notification data example: |- { "data": { "close_out_margin": 130, "currency": "USDC", "equity": 110, "initial_margin": 150, "isolated": true, "maintenance_margin": 120, "margin_balance": 110, "state": "liquidation_started", "timestamp": 1750000400000, "user_id": 220042 } } bindings: [] extensions: - id: x-parser-unique-object-id value: subscription_message bindings: [] extensions: *ref_0 sendOperations: - *ref_1 receiveOperations: - *ref_2 sendMessages: - *ref_3 receiveMessages: - *ref_4 extensions: - id: x-parser-unique-object-id value: user.isolated.liquidation securitySchemes: [] ````