{
"jsonrpc": "2.0",
"method": "public/subscribe",
"id": 42,
"params": {
"channels": [
"user.lsp"
]
}
}{
"data": {
"type": "transfer",
"instrument_name": "BTC-PERPETUAL",
"direction": "sell",
"amount": 5000,
"price": 63481.75,
"currency": "BTC",
"success": true,
"timestamp": 1750000400000
}
}user.lsp
Notifications for an LSP (Liquidity Support Program) participant subaccount: assignment attempts (successful or failed), enable/disable state changes, and effective configuration changes.
Subscribe to this channel with an API key belonging to the LSP participant subaccount itself. See user.liquidation for the notification sent to the liquidated (source) user whose position was transferred.
Every notification includes a type field identifying the event kind — see the notification schema for the full list of types and which fields accompany each.
{
"jsonrpc": "2.0",
"method": "public/subscribe",
"id": 42,
"params": {
"channels": [
"user.lsp"
]
}
}{
"data": {
"type": "transfer",
"instrument_name": "BTC-PERPETUAL",
"direction": "sell",
"amount": 5000,
"price": 63481.75,
"currency": "BTC",
"success": true,
"timestamp": 1750000400000
}
}Client sends subscription request to subscribe to notification channel. Please refer to Notification page for more information.
Server sends subscription notification data
The kind of LSP (Liquidity Support Program) event this notification represents:
transfer: An assignment attempt to this participant completed — checksuccessto see whether it succeeded (fully or partially) or failed and was redistributed to other participants (or fell through to ADL).enabled: This participant's LSP configuration transitioned from disabled to enabled.disabled: This participant's LSP configuration transitioned from enabled to disabled — checkautomaticto see whether this was a manual change or an automatic disable after repeated transfer failures.configuration_changed: This participant's effective configuration changed (enable state and/or any group limit, including a change to the platform-wide default that affects this participant). Fired on every configuration write, including no-op enable/disable transitions.
transfer, enabled, disabled, configuration_changedUnique instrument identifier
Present for transfer only.
buy, sellPresent for transfer only. Size of the position assigned (or attempted).
Present for transfer only. The transfer price applied to this assignment attempt.
Currency, i.e "BTC", "ETH", "USDC"
BTC, ETH, USDC, USDT, EURRPresent for transfer only. true if the assignment succeeded, false if it failed (see error_reason).
Present for transfer only, and only when success is false. Machine-readable failure reason.
platform_locked, lock_count_exceeded, timeout, temporarily_unavailable, not_enough_funds, internal_errorPresent for disabled only. true if this was an automatic disable after repeated transfer failures, false if a manual configuration change.
Present for disabled only, and only when automatic is true. Number of transfer failures that triggered the auto-disable.
Present for disabled only, and only when automatic is true. Length of the failure-counting window, in minutes.
Present for configuration_changed only. The participant's resolved effective configuration: enabled, plus every cooldown group's effective limit percentage (group_limits, keyed by group) — per-participant overrides are already resolved against the platform-wide defaults, so every group appears here regardless of whether this participant has an explicit override.
The timestamp (milliseconds since the Unix epoch)
Related topics
user.liquidation Liquidity Support Program (LSP) API Guideprivate/get_lsp_participantsprivate/get_lsp_participants_usageprivate/get_lsp_usageWas this page helpful?