Skip to main content
POST
Execute Risk Matrix

Overview

Manually triggers risk matrix analysis for an entity using configured rules. The risk matrix evaluates the entity against all active rules and calculates a risk score. Optionally enriches the entity before analysis. This is the same endpoint used for Analyze Entity, but documented here for convenience when specifically working with risk matrices.

Endpoint

Authentication

Requires a valid API key in the Authorization header:

Path Parameters

string
required
UUID of the entity (company or person) to analyze

Request Body

string
required
Type of entity to analyze
  • person - Individual/person entity
  • company - Company/business entity
  • transaction - Transaction entity
boolean
default:"false"
Whether to run data enrichment before analysis. If true, will execute all active enrichment integrations configured for this organization.
array<string>
Specific enrichment provider codes to execute before analysis. Only used when enrichIfNeeded is true. See Provider Codes Reference.
object
Per-run rules engine behavior. See Analyze Entity β€” rulesEngineConfig (partialCoverage, omitCoverage; both default false).

Response

boolean
Whether the analysis was successful
object
Analysis result data:
  • id (string) - Audit ID for this analysis
  • entityId (string) - Entity that was analyzed
  • entityType (string) - Type of entity
  • overallRiskScore (number) - Overall risk score (0-100)
  • riskLevel (string) - Risk level: LOW, MEDIUM, HIGH, CRITICAL
  • confidence (number) - Confidence level of the analysis (0-100)
  • rulesTriggered (number) - Number of rules that matched
  • rulesExecuted (number) - Total number of rules evaluated
  • executionTimeMs (number) - Total execution time in milliseconds
  • riskFactors (array) - Rules that matched/triggered
  • recommendations (array) - Recommended actions
  • analyzedAt (string) - ISO timestamp of analysis
  • triggeredBy (string) - Who/what triggered the analysis
  • metadata (object) - Additional metadata including matrix info
object
Full rules execution result when analysis ran: success, executed, result, rulesTriggered, executionTimeMs, auditId, isNewAudit, rulesExecutionSummary (same as root field below).
object
At the root of the response (same as transactions API). Same value as rulesResult.rulesExecutionSummary. Only present when rules ran. Summary of which rules matched (hit) vs did not (no hit), executed actions, and total score. Structure: rulesHit, rulesNoHit, actionsExecuted (includes alerts, suggestion, status, assignedUser, customKeys β€” array of custom action keys from matched rules, for integrations/workflows), totalScore.

Examples

Basic Risk Matrix Execution

Execute with Auto-Enrichment

Execute with Specific Enrichments

Response Example

Successful Analysis

No Active Rules Warning

Incomplete Data Coverage

Risk Levels

The system calculates risk levels based on the overall risk score:
  • LOW (0-29): Minimal risk, standard processing
  • MEDIUM (30-59): Moderate risk, standard monitoring required
  • HIGH (60-79): Elevated risk, enhanced monitoring required
  • CRITICAL (80-100): Severe risk, immediate action and enhanced due diligence required

Rule Actions

When rules match, they can trigger automatic actions:
  • createAlert - Creates an alert for manual review
  • updateEntityStatus - Changes entity status (e.g., to under_review)
  • addTag - Adds tags to the entity for categorization
  • sendEmail - Sends email notification
  • webhook - Triggers webhook for external integration

Error Responses

404 Not Found - Entity Not Found

401 Unauthorized

422 Unprocessable Entity - Incomplete Data

Real-Time Notifications

When risk matrix execution completes, a real-time notification is sent via WebSocket:

Best Practices

  1. Enrich First: For best results, enrich entity data before analysis using enrichIfNeeded: true
  2. Handle Warnings: Check for NO_RULES_FOUND warning and configure rules if needed
  3. Data Coverage: Ensure required fields are populated to avoid INCOMPLETE_DATA_COVERAGE errors
  4. Monitor Actions: Review actionsExecuted to understand what automated actions were taken
  5. Caching: Results are cached for performance - use cached field to check if analysis is fresh

Use Cases

Onboarding Risk Assessment

Periodic Re-assessment

Transaction Risk Scoring

Next Steps