What does the risk_type field represent in Resilinc APIs, and how should its values be interpreted?

Created by Rohit Sawant, Modified on Mon, 18 May at 7:47 AM by Rohit Sawant

The risk_type field in Resilinc APIs indicates how the risk score for a given entity (such as site, product, part, or category) has been determined. It helps distinguish whether the score is system-generated, manually adjusted, or derived from default settings.
This field is commonly available across multiple API domains, including:
- site_risks
- product_risks
- part_risks
- category_risks
Each risk_type value represents a specific source or condition of the risk score:
- CALCULATED
  The risk score is automatically computed by the system based on configured risk factors such as location risk, supplier financial health, survey responses, and other weighted components. This reflects the platform’s standard risk assessment.
- OVERWRITTEN
  The risk score has been manually updated by a user through the UI. This value takes precedence over all other types and indicates a deliberate override of the system-calculated score.
- DEFAULT
  This value is used when neither a calculated nor an overwritten score is available. In such cases, the system applies a default risk value configured in the risk settings (typically within a range of 1 to 10). If no default value is set, the score may appear as blank.
- NO_WEIGHT
  This indicates that a risk factor exists in the configuration, but no weight has been assigned to it. Since weights are required for risk calculation, the system cannot compute a score for that factor.
Priority Hierarchy:
When determining which score to display, the system follows this order:
- OVERWRITTEN (highest priority)
- CALCULATED
- DEFAULT (fallback option)

The risk_type field is particularly useful for understanding whether a risk score is automatically generated, manually influenced, or dependent on configuration settings, enabling better transparency and control in risk analysis and decision-making.