Signals & Attributes
The RiskOS™ data taxonomy — attributes, signals, reason codes, tags, and derived values — and where each appears in the API response.
RiskOS™ workflows process five distinct types of data during an evaluation. Each has a precise definition, a distinct runtime role, and a specific location in the API response.
Data taxonomy
| Term | Definition | Set by | API response location |
|---|---|---|---|
| Attribute | A normalized input field describing the entity being evaluated | Your application (via API request) | Request payload (data.*) |
| Signal | A discrete data point returned by an enrichment or external data service | Enrichment step | data_enrichments[].response.* |
| Reason code | A human-readable code explaining why a specific outcome occurred | Enrichment response or Reason Code step | data_enrichments[].response.reason_codes[] |
| Tag | A metadata label conditionally attached to an evaluation | Tag step | tags[] |
| Derived value | A value computed by a workflow step from attributes, signals, or other derived values | Transformation or Rule Scorecard step | computed.* |
Attributes are the input data your application sends — name, DOB, SSN, email, phone, device data, and custom fields. The Input step of a workflow defines which attributes are required and optional.
Signals are the evidence used by rules and conditions to reach a decision. Each enrichment produces multiple signals — risk scores, match results, fraud flags, and validation results.
Reason codes provide explainability. They answer "why did this evaluation receive this decision?" Reason codes are decision explanations, not decision inputs.
Tags classify evaluations for operational purposes — filtering cases, triggering automation, and segmenting analytics. Tag steps assign tags when their conditions evaluate to true.
Derived values are intermediate computations produced by Transformation steps and Rule Scorecards. They feed into downstream rules and conditions.
Related topics
- Enrichments — The data services that produce signals
- Rules & Conditions — The logic layer that consumes signals
- Reason Codes & Score Interpretation — Reading reason codes and scores
- Entities and Aggregations — Entity tracking and aggregation functions
Updated about 1 month ago