Skip to content
Longport Whale
Client Limit

Client Batch Apply Trade Limit

On the Client Limit page, triggered by the inline "Activate/Deactivate" button or the floating batch-action bar after selecting rows; only the specific values passed by the caller differ. It changes the live activation state of trading limits and is relatively high-risk.

POSThttps://b-api.longbridge.xyz/risk_limit/v1/client/batch_apply

Authorization

AuthorizationstringheaderRequired

Send the Broker ACCESS_TOKEN as Authorization: Bearer <token>.

Request body application/json

listarray<string>required

Batch target limit config list. Field meanings per item: counter_id (counter number), aaid (customer account ID, the key field for the customer dimension), code (security code, usually empty), trader/trader_name (trader ID/name), client_group/client_group_name (client category/group ID/name), stock_group (stock-group ID).

is_applybooleanrequired

Apply flag. true = batch activate, false = batch deactivate; determined by the negated value passed when the "Activate/Deactivate" button is clicked (!(is_apply_val === 'true')).

audit_frontend_resourceobject

Frontend audit log metadata. Not a business parameter; used only for backend audit logging. $action: 'add' (activate) | 'delete' (deactivate); $behavior: the audit-action description text (i18n keys audit_limit_effective/audit_limit_invalid).

Responses

HTTP 200No confirmable field definitions are available for the response yet.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

Whale Docs