https://b-api.lbkrs.com/account/kyc/edit_suspicious_eventAuthorization
Send the Broker ACCESS_TOKEN as Authorization: Bearer <token>.
Permission
The Broker ACCESS_TOKEN must be granted the permission above, or the call will be rejected.
Request body application/json
Suspicious event record ID, the id of the event row in the suspicious event list (not event_no).
Securities account associated with the event. The admin frontend takes it from the event row and does not allow it to be changed.
Pass the internal numeric ID of the customer's securities account (aaid), not the securities account number account_no (such as H00000000) or the customer ID member_id. One customer can have multiple aaid values.
Trigger indicator. Values come from the kyc_suspicious_event_tigger_indicator reference options.
Trigger indicator remark.
Event remark.
Latest alert date, as a Unix timestamp in seconds.
Provides audit context for this operation.
Responses
HTTP 200The request was processed successfully. The response data does not contain additional business fields.codemessagedatadataobjectdata structureNo nested fields
HTTP 400Bad request. Check the business error code in code and the error details in message.codemessagedatadataobjectdata structureNo nested fields
HTTP 401The user is not authenticated, or the login session has expired.codemessagedatadataobjectdata structureNo nested fields
HTTP 403The current account is not authorized to use this feature. Grant the required permission to the account in User Permission.codemessagedatadataobjectdata structureNo nested fields
HTTP 408The request timed out. Check the business error code in code and the error details in message.codemessagedatadataobjectdata structureNo nested fields