Operate Index Level

Unified maintenance endpoint for Index Levels, using operation to distinguish create, edit, delete, and data-initialization actions.

Request parameters

Required: index_code, index_name, index_type (index level type), operator, operation (operation type).
Optional: remark, id (record ID).
See the field descriptions for the format, value range, default behavior, and business meaning of each field.

Business notes

operation selects the action: create (0) submits index code/name/level type/remark; edit (1) additionally carries id; delete (2) reuses the stock_level field naming (a legacy carry-over); data initialization (3) sends only operation.

Risk warning

This operation changes the index-level configuration used by stress tests and affects the related risk calculations. Confirm the operation type and parameters before calling.

Result

On success, the described operation is completed; subsequent state and returned data follow the 200 response definition.

POSThttps://b-api.lbkrs.com/v1/risk_monitoring/index_level_operate

Authorization

AuthorizationstringheaderRequired

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

Request body application/json

index_codestringrequired

Index Code. This field is required.

index_namestringrequired

Index Name. This field is required.

index_typeintegerrequired

Index Type. Index level, single-select: 0 = Tier1, 1 = Tier2, 2 = Other. The delete operation reuses the field name stock_level (using the record's stock_level_val), a legacy naming artifact.

Values

0
1
2

remarkstring

Remark.

operatorstringrequired

Operator. Current logged-in operator account; included on create/edit/delete

operationintegerrequired

Operation. Operation type: 0 = add, 1 = edit, 2 = delete, 3 = initialize data (sending only operation=3, with no other fields).

Values

0: Add
1: Edit
2: Delete
3: Initialize Data

idinteger

ID. Sent only for edit (operation=1) and delete (operation=2); not sent for create (operation=0) or initialize (operation=3).

Responses

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