Skip to content
Suspicious Incident Monitoring

Edit Suspicious Event

Edits an existing suspicious event (AML suspicious incident) record, updating its trigger details and alert date.

Request parameters

  • Required: event_id (suspicious event record ID), aaid (associated securities account), tigger_indicator (trigger indicator), and last_alert_date (latest alert date).
  • Optional: tigger_indicator_remark (trigger indicator remark), remark (event remark), and audit_frontend_resource (caller-provided audit context).
  • The field names tigger_indicator and tigger_indicator_remark are spelled as shown; the admin frontend sends these names, not trigger_indicator or trigger_remark.
  • event_id is the id of the event row in the suspicious event list, not event_no; aaid is the aaid of the same row. The aml_suspicious_events list response does not currently document id or aaid.
  • See the field definitions for each field's format, allowed values, and business meaning.

Business notes

The target event is located by event_id, and the submitted field values overwrite the existing content.

Risk warning

This operation modifies an existing suspicious-event record and affects the downstream AML review and compliance handling. Confirm that event_id points to the correct record and that all fields are correct before calling.

Result

On success the suspicious event is updated; final state and returned data follow the 200 response definition.

POSThttps://b-api.lbkrs.com/account/kyc/edit_suspicious_event

Authorization

AuthorizationstringheaderRequired

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

Permission

account.sem_updatekyc.suspicious_incident_monitoring

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

Request body application/json

event_idstringrequired

Suspicious event record ID, the id of the event row in the suspicious event list (not event_no).

aaidstringrequired

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.

tigger_indicatorstringrequired

Trigger indicator. Values come from the kyc_suspicious_event_tigger_indicator reference options.

tigger_indicator_remarkstring

Trigger indicator remark.

remarkstring

Event remark.

last_alert_dateintegerrequired

Latest alert date, as a Unix timestamp in seconds.

audit_frontend_resourceobject

Provides audit context for this operation.

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