Skip to content
Sub Account View

Create Sub Account View

Creates a sub-position view that organizes sub-position scopes into groups.

Request parameters

  • Required: view_name (view name), usage_scene (usage scenario), groups (group list), groups[].group_name (group name), and groups[].sub_position_scope (sub-position scope).
  • Optional: remark.
  • See the field descriptions for each field's format, range, and business meaning.

Business notes

A sub-position view is scoped by usage_scene and may contain multiple groups, each defining its own sub-position scope.

Risk warning

This operation creates a real sub-position view configuration that may be referenced by downstream business such as corporate actions. Confirm the view name, scenario, and group scopes before calling.

Result

On success the sub-position view is created; subsequent state and returned data follow the 200 response definition.

POSThttps://b-api.lbkrs.com/corporate_action/sub_position_view/create

Authorization

AuthorizationstringheaderRequired

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

Permission

corporate.sub_account_view_update

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

Request body application/json

view_namestringrequired

This field is required.

usage_scenenumberrequired

Required. Single-select usage scenario for the sub-account view.

Allowed values: 1 Rounding Adjustment, 2 Refund, 3 After-event Adjustment

Values
1
Rounding Adjustment
2
Refund
3
After-event Adjustment
remarkstring
groupsarray<string>required

A list of groups, multiple can be added; each item contains a group name and a sub-account scope.

Responses

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

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