---
title: "GET /private/get_lsp_participant_config"
method: GET
path: "/private/get_lsp_participant_config"
tags: ["lsp", "Private"]
---

# GET /private/get_lsp_participant_config

`GET /private/get_lsp_participant_config`

Retrieves the LSP (Liquidity Support Program) participant configuration for the authenticated account.

LSP participants are designated subaccounts that receive assigned positions from liquidated users as an alternative to auto-deleveraging (ADL). This method must be called with an API key belonging to the LSP participant subaccount itself — it returns an error if the authenticated account has no LSP configuration.

The response includes the participant's enable/disable state and any per-cooldown-group limit overrides. When the platform-side participant position lock is switched on, enrolling a subaccount as an LSP participant also locks it to reduce-only trading; this lock is off by default, so participation does not by itself restrict the subaccount to reduce-only.

**Scope:** `account:read`

[Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fget_lsp_participant_config)

## Response `200`

Success response

- PrivateGetLspParticipantConfigResponse
  - `jsonrpc` '2.0', required — The JSON-RPC version (2.0)
  - `id` integer — The id that was sent in the request
  - `result` object, required
    - `config` LspConfig, required — LSP participation configuration for a single subaccount. Note: designating a subaccount as an LSP participant also locks it to reduce-only trading platform-side. This lock is not automatically released when the participant is removed — an admin must clear it manually.
      - `enabled` boolean, required — Whether this subaccount is currently an active LSP participant eligible to receive assignments.
      - `group_limits` object, required — Per-participant overrides of the assignment limit for each cooldown group, expressed as a percentage of the participant's own equity. Keyed by group: `"1"` through `"6"` (crypto tiers, `"6"` is the catch-all tier) or `"rwa"` (real-world-asset instruments, e.g. tokenized equities/commodities). A group absent from this map inherits the platform-wide default for that group. A value of `0` disables assignments for that group entirely. The maximum allowed value for any group is `notional_capacity_factor * 100` (see the global LSP config) — that factor caps the total notional LSP may assign to a participant as a multiple of its equity, and does not change the participant account's own maximum leverage.

## Other responses

- `401` — Success response

---

[API](https://skmtc.net/deribit/apis/deribit-api-2.md) · [All operations](https://skmtc.net/deribit/apis/deribit-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/deribit/deribit-api-2/revisions/8dfbbe9fdddf/schema)