Set Admin Auto Liq Action
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Response
Non-empty if the request failed
Bearer authentication of the form Bearer <token>, where token is your auth token.
Non-empty if the request failed
Available to: Organization administrators
Environments: Demo
Rate Limit: No endpoint-specific limit
Set the auto-liquidation action for an account. Use this endpoint to lock an account (rejecting new orders), trigger liquidation, or unlock it by setting the action back to Normal.
adminAction set to Normal. It does not auto-unlock at the next trading session, time out, or reset on its own.There is no bulk version of this endpoint. You must call it separately for each account.
adminAction Values
adminActionReasonCode Values
Most partners use Other (with a descriptive adminActionReason). The Close* and Restricted* codes are used internally for brokerage account management.
When adminActionReasonCode is Other, you must provide an adminActionReason describing why you’re taking the action. For all other reason codes, adminActionReason is optional.
Common Partner Workflows
adminAction to LockTradingImmediately to prevent new orders. The account’s open positions are not affected.adminAction to LiquidateImmediately, then call the endpoint again with adminAction set to LockTradingImmediately.adminAction to LiquidateOnlyModeImmediately. The account can still close existing positions but cannot open new ones.adminAction to Normal to allow the account to resume trading.doNotUnlock enabled): If the account’s doNotUnlock field is set to true, a daily loss limit breach locks the account and the lock does not auto-reset at the next market open. Call this endpoint with Normal before the next trading session to let the trader resume. The doNotUnlock setting stays in place for future sessions.changeDemoBalance and updateMaxNetLiq to reset an account after an incident.Best Practices
accountRiskStatus object in the response or by calling accountRiskStatus/deps.Common Failure Scenarios
accountId does not reference a valid account (returns HTTP 404)adminActionReasonCode is Other but adminActionReason is missingadminActionReason exceeds 8,192 charactersHTTP 401)Error Messages