Skip to main content
POST
Analyze Entity

Overview

Manually triggers risk analysis for an entity using the configured risk matrix and rules. Optionally enriches the entity before analysis.

Endpoint

Path Parameters

string
required
UUID of the entity to analyze

Request Body

string
required
Entity type: person, company, or transaction
boolean
default:"false"
Whether to run enrichment before analysis
array
Specific provider codes to execute for enrichment
object
Per-run rules engine behavior. All fields optional; omitted fields default to false.
  • partialCoverage (boolean, default false): With multiple assigned risk matrices, validate data coverage per matrix. Matrices without coverage are skipped; others still run. If none have coverage, returns 422.
  • omitCoverage (boolean, default false): Skip data coverage gates entirely (main entity pre-check and shareholder coverage). Takes precedence over partialCoverage when both are true.
Does not change org-level shareholderCoverageMode.

Example Requests

Basic Analysis

Analysis with Enrichment

Analysis with Specific Providers

Multi-Matrix Analysis with Per-Matrix Coverage

Use when an entity has several risk matrices but you want matrices with sufficient data to run even if others are missing enrichments:

Response - Success

The response includes data (analysis details), and when rules ran also rulesResult and rulesExecutionSummary at the root (same as create, enrich, refresh).
object
Full rules execution result when analysis ran: success, executed, result, rulesTriggered, executionTimeMs, auditId, isNewAudit, rulesExecutionSummary (same object 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, totalScore.

Response - Partial matrix execution (rulesEngineConfig.partialCoverage: true)

When some assigned matrices lack data coverage but at least one matrix can run, the request succeeds (200). Skipped matrices are listed at the root:
The audit row stores executed matrix IDs in risk_matrix_ids; skipped matrices appear in analysisResult.matricesSkippedForCoverage.

Response - No Rules Configured

Response - Incomplete Data

Risk Levels

  • LOW: 0-29 - Minimal risk
  • MEDIUM: 30-59 - Moderate risk, standard monitoring
  • HIGH: 60-79 - Elevated risk, enhanced monitoring required
  • CRITICAL: 80-100 - Severe risk, immediate action required

Use Cases

Analyze After Data Update

Batch Analysis

See Also