Evaluations
An evaluation is a single execution of a RiskOS™ workflow — the runtime unit of work that turns a request into a decision.
An evaluation is a single execution of a workflow in RiskOS™. When your application sends a POST request to the /api/evaluation endpoint with user, business, or device data, RiskOS™ runs the specified workflow and returns a decision along with enrichment data, risk scores, and reason codes.
Every interaction with the RiskOS™ decisioning engine — whether identity verification, fraud screening, or compliance check — is an evaluation. It is the canonical runtime entity in RiskOS™.
Evaluation lifecycle
| Phase | What happens | Output |
|---|---|---|
| Request | Your application sends a POST to /api/evaluation with a payload containing PII and a workflow name | eval_id assigned |
| Execution | RiskOS™ runs the workflow: Input → Enrichments → Conditions → Rules → Decision | Step-by-step processing |
| Decision | The workflow reaches a terminal step (Decision or Manual Review) | ACCEPT, REJECT, or REVIEW |
| Response | RiskOS™ returns the decision, enrichment data, tags, reason codes, and scores | JSON response or webhook |
Evaluations can execute synchronously (completing in a single API response) or asynchronously (pausing for user action and delivering results via webhook). See Synchronous vs Asynchronous Evaluations for the full execution model.
Related topics
- Statuses & Lifecycle — Evaluation states, case creation, and lifecycle diagrams
- Workflows — The configurable sequence of steps an evaluation runs
- Decisions — The outcome an evaluation returns
- Synchronous vs Asynchronous Evaluations — Real-time vs deferred execution
- POST /api/evaluation — Request and response specification
- Integrating with RiskOS™ — Send your first evaluation
Updated about 1 month ago