Alert Review
This guide demonstrates how to triage and resolve AML alerts through the API. You will list open alerts by priority, inspect a specific alert, trigger AI-powered research, review the AI assessment, and resolve the alert.Prerequisites
- A valid API key (see Authentication)
- At least one case with open alerts (see End-to-End Onboarding)
List open alerts by priority
Retrieve all open alerts sorted by priority score (highest first). This mirrors the analyst inbox view.Response:
Filtering options
| Parameter | Type | Description |
|---|---|---|
status | string | Filter by status: Open, Acknowledged, Resolved, False Positive, Escalated |
category | string | Filter by category: PEP Match, Sanctions Hit, Adverse Media, etc. |
type | string | Filter by type: Screening, Identity, Company, Document, Financial |
priority | string | Filter by priority: Critical, High, Medium, Low |
case_token | string | Filter alerts belonging to a specific case |
sort | string | Sort field with optional - prefix for descending |
limit | number | Results per page (default 25, max 100) |
cursor | string | Pagination cursor from previous response |
Get alert details
Retrieve the full details of the highest-priority alert, including screening match data and AI fields.Response:
Trigger AI research
Request AI-powered analysis of the alert. The AI reviews the screening match against public sources to assess whether it is a true positive or false positive.Response:
AI research runs asynchronously. Typical completion time is 10-30 seconds. You will receive a
alert.ai_research_completed webhook event when results are ready, or you can poll the endpoint below.Resolve the alert
Based on the AI assessment and your review, resolve the alert with an action and notes.Response:
Resolution actions
| Action | When to use |
|---|---|
Approve | Alert reviewed, no issues found or risk accepted |
Decline | Confirmed compliance issue, reject the entity |
Escalate | Uncertain or complex, route to senior reviewer |
Request Document | Additional evidence needed from the client |
Approve with Conditions | Approved with caveats (e.g., enhanced monitoring) |
Alert lifecycle
Alerts move through a defined set of statuses from creation to resolution:| Status | Description |
|---|---|
Open | Alert created, awaiting analyst review |
Acknowledged | Analyst has claimed and is reviewing the alert |
Resolved | Alert reviewed and resolved with an action |
False Positive | Confirmed as a false positive match |
Escalated | Escalated to a senior reviewer or manager |
Priority scoring
Every alert receives a composite priority score (0-290 points) calculated from five components. The priority score drives the default sort order in the analyst inbox: highest-score alerts appear first.| Component | Max Points | Calculation |
|---|---|---|
| SLA urgency | 100 | Breached = 100, linear decay from due date |
| Risk tier | 100 | Critical = 100, High = 75, Medium = 50, Low = 25 |
| Category weight | 60 | Sanctions = 60, PEP = 45, Adverse Media = 30 |
| Match score | 10 | Screening confidence / 10 |
| Case risk | 20 | Parent case risk score / 5 |
Priority labels
| Priority | Score Range |
|---|---|
Critical | 200+ |
High | 120-199 |
Medium | 60-119 |
Low | 0-59 |
Bulk operations
For high-volume alert processing, use the bulk endpoints. See Bulk Operations Guide for details.Next steps
- Alert Management Guide. Deep dive into the alert lifecycle and priority scoring.
- AI Research Guide. Learn about AI-powered analysis and auto-disposition.
- Bulk Operations Guide. Process alerts at scale.
- Pagination Guide. Navigate large result sets efficiently.