Operate Index Level

The Index Level page uses one endpoint for four actions: add (operation=0, submitting index_code/index_name/index_type/remark), edit (operation=1, plus an id), delete (operation=2, which reuses the field name stock_level instead of index_type, a legacy naming artifact), and initialize data (operation=3, sending only operation).

POSThttps://b-api.longbridge.xyz/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. Required when adding/editing.

index_namestringrequired

Index Name. Required when adding/editing.

index_typeintegerrequired

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

remarkstring

Remark. Remark, optional.

operatorstringrequired

Operator. The currently logged-in admin 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).

idinteger

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

Responses

HTTP 200No confirmable field definitions are available for the response yet.

Standard response envelopecodemessagedata

dataobjectdata structure

No nested fields

Request

curl --request POST \
  --url 'https://b-api.longbridge.xyz/v1/risk_monitoring/index_level_operate' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json'
  --data '{
  "index_code": "HSI",
  "index_name": "恒生指数",
  "index_type": 0,
  "remark": "港股一级指数",
  "operator": "user@example.com",
  "operation": 1,
  "id": 10086
}'

Response

{
  "code": 0,
  "message": null,
  "data": {}
}