Skip to content
Dealer Limit

Trader Batch Apply Trade Limit

Batch-applies the effective state of a set of trader trading limits, using is_apply to enable or disable the target records.

Request parameters

  • Required: list (trader-limit record list), is_apply (whether to take effect)
  • Optional: audit_frontend_resource (caller-provided audit context)
  • See the field notes for each field's format, value range, and business meaning.

Business notes

Each entry in list identifies an existing limit configuration. This endpoint only toggles the effective state in bulk; it does not change the limits' thresholds.

Risk warning

This operation changes the effective state of live trading limits and directly affects whether subsequent trades pass risk checks. Verify the target record list and the is_apply value before calling.

Result

On success, the bulk effective-state change is completed; the resulting state and returned data follow the 200 response definition.

POSThttps://b-api.lbkrs.com/risk_limit/v1/trader/batch_apply

Authorization

AuthorizationstringheaderRequired

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

Permission

lb_hk_risk_limit_config.risk_limit_config_trader_update

The Broker ACCESS_TOKEN must be granted the permission above, or the call will be rejected.

Request body application/json

listarray<string>required

Trader Limit Record List. The batch-selected (or single) limit records; element fields: counter_id (counter ID), aaid (account AAID), code (instrument code), trader (trader account), trader_name (trader name), client_group (client group ID), client_group_name (client group name), stock_group (securities group ID).

is_applybooleanrequired

Is Apply. true = batch activate (apply to enable limits), false = batch deactivate (revoke/disable limits).

Values
true
Batch Activate
false
Batch Deactivate
audit_frontend_resourceobject

Audit Context. Audit metadata for client tracking, containing $action (add/delete) and $behavior (an operation-description label, e.g. "limit effective" / "limit invalid").

Responses

HTTP 200The request was processed successfully. The response data does not contain additional business fields.
Standard response envelopecodemessagedata
dataobjectdata structure

On success data is an empty object.

No nested fields

HTTP 400Bad request. Check the business error code in code and the error details in message.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

HTTP 401The user is not authenticated, or the login session has expired.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

HTTP 403The current account is not authorized to use this feature. Grant the required permission to the account in User Permission.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

HTTP 408The request timed out. Check the business error code in code and the error details in message.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

Whale Docs