Skip to main content
POST
Report Transaction Risk

Overview

Use this endpoint when an analyst confirms that a transaction requires investigation under an active category such as FRAUD or AML. The operation:
  • marks the transaction as manually reported and sets flagged=true;
  • creates an alert without a rule, rule snapshot, or numeric risk score;
  • creates a new investigation or attaches the alert to the compatible active investigation explicitly selected by the analyst;
  • writes transaction and investigation audit events.
It does not change the transaction status, execute rules, or create a risk analysis audit.

Authentication

Requires transactions:edit.

Request body

string
required
Code of an active investigation category, for example FRAUD or AML.
"origin" | "destination"
required
Transaction party that becomes the investigation subject. The selected side must reference an entity in the same organization.
"create" | "consolidate"
required
Whether to create a separate investigation or consolidate into an existing one.
string
Required only with investigationAction="consolidate". The investigation must be active and match the organization and selected subject. It does not need to share the reported category: an investigation accumulates several in categoriesAffected. Because the alert belongs to a transaction, the investigation must also group transaction or combined alerts: investigations scoped to person, company or device, and single-alert ones, are rejected with MANUAL_RISK_INVESTIGATION_INVALID.
boolean
default:"false"
Applies only with investigationAction="create". When true, future alerts will not be automatically consolidated into this investigation.
string
Optional analyst justification. Maximum 5,000 characters.

Response

Returns HTTP 201 when the report is created. Repeating the operation returns HTTP 200 with alreadyReported: true and does not duplicate the alert or investigation.
The transaction keeps direct alert and investigation IDs. This prevents a second report and lets the user open the linked case from the transaction detail. The investigation audit can be non-null when the alert is attached to an existing case that already had a risk analysis. The manual alert remains unlinked to any rule or audit. After commit, the operation emits the investigation_created or investigation_updated automation event, plus alert_created. Active organization automations using those triggers therefore process manual reports as well.