Skip to content
Client Order

Batch Reject Fund Channel Order

Batch-reject the selected fund channel (SaaS) customer orders, recording a customer-visible rejection reason and an internal remark.

Request parameters

  • Required: ut_ids (order ID list), reason (rejection reason, visible to the customer), remark (internal remark).
  • Both reason and remark are serialized strings of a multilingual object {zh-CN, zh-HK, en}.
  • See the field definitions for each field's format, allowed values, and business meaning.

Business notes

Each order in ut_ids is rejected. reason is shown to the customer; remark is kept for internal reference only.

Risk warning

This operation changes order status and is customer-visible. Confirm the order list and reason before calling.

Returns

On success the batch rejection is completed; see the 200 response for the exact payload.

POSThttps://b-api.lbkrs.com/portfolio/funds/batch/reject_saasorder

Authorization

AuthorizationstringheaderRequired

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

Permission

fund.reject_order

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

Request body application/json

ut_idsarray<string>required

Order ID List. The list of channel-order ids being batch-rejected; elements are strings, taken from the selected rows.

reasonstringrequired

Reject Reason (customer-facing). Rejection reason; a serialized string of a multilingual object {zh-CN, zh-HK, en} (can be quickly chosen from a preset-remark library).

remarkstringrequired

Internal Remark. Internal remark; a serialized string of a multilingual object {zh-CN, zh-HK, en}, visible internally only.

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