Risk factors

Learn how to succesfully implement Sayari Risk Factors via API

Risk factors

Learn how to succesfully implement Sayari Risk Factors via API

Overview

Sayari has three methods for determining Risk Factors. This guide details how to properly identify and implement each.

Review our Risk Factor Documentation for the full list of risk factors and their visibility method: (seed, network, psa)

Seed Risk

Direct associations between entities and authoritative risk sources.

Network Risk

Risk exposure through business relationships, ownership structures, and trading activity.

PSA Risk

Risk propagation through possibly-same-as entity groups.

Getting Started

Every Risk Factor object in the API response follows a consistent structure:

Entity Response - Risk - Field Descriptions

1 {
2     "risk": {
3         "some_risk_factor_name": {
4             // The unique identifier for this risk factor
5             "value": true,
6             // Boolean for Seed/PSA risks, numeric for Network risks
7             "metadata": {
8             // Additional context about the risk factor
9                 "source": ["..."],
10             },
11             "level": "critical"
12             // Risk severity: critical, high, or elevated
13         }
14     }
15 }

Seed Risk

Seed Risk Factors identify direct connections between entities and authoritative risk sources like sanctions lists, regulatory databases, or adverse media records.

Identify Seed Risk

The values for Seed Risk are returned as booleans

Entity Response - Seed Risk

1 {
2     "risk": {
3         "wro_entity": {
4             "value": true,
5             "metadata": {
6                 "source": ["USA CBP Withhold Release Orders and Findings List"]
7             },
8             "level": "critical"
9         }
10     },

Review Risk Intelligence on the Entity Profile

Each Seed Risk Factor includes a matching risk_intelligence object that contains detailed metadata about the source generating the risk.

Entity Response - Risk Intelligence

1   "risk_intelligence": {
2       "data": [{
3           "properties": {
4               "type": "wro_entity",
5               "authority": "USA Department of Homeland Security",
6               "list": "USA CBP Withhold Release Orders and Findings List",
7               "status": "Active",
8               "from_date": "1995-10-06"
9           },
10           "record": ["b222c03b9eb324d0969f40af61bb4e36"]
11       }]
12   }
13 }

While therisk_intelligence object is only available for Seed Risk factors; each Target entity associated with a Network Risk Factor will have an associated Seed Risk. From that Seed Risk, the risk_intelligence object can be obtained.

Best Practices

Always check the risk_intelligence object for complete context
Review all metadata fields including authority, list, status, and dates
Track the source lists generating each Risk Factor

Network Risk

Network risk factors analyze entity relationships to detect indirect risk exposure through business networks, ownership structures and trading relationships throughout the Sayari Knowledge Graph.

Identify Network Risk

Network risk values are numeric and represent the distance (“hops”) between an entity and its nearest risk target through the network of relationships. The number indicates how many edges or relationships exist in the chain linking source to target.

Entity Response - Network Risk

1 {
2 "ofac_50_percent_rule": {
3     "value": 3,
4     "metadata": {},
5     "level": "high"
6 },

Identify traversal parameters to create paths to Target Entities

Network risk parameters can be obtained in two ways:

Reference the Risk Factor Documentation for parameter specifications
Programmatically parse them from the Sayari ontology endpoint

These parameters define the methodology for calculating network risk by specifying relationship types, traversal depth, and risk factor combinations.

Network Risk Params

1   -max_depth: 6
2   -PSA: True
3   -Seed Risk: ['ofac_sdn']
4   -Relationships: ['subsidiary_of', 'has_shareholder']

Call the Traversal Endpoint

Query the /traversal endpoint pairing the entity_id from step #1 with the Network Risk Params obtained in Step #2. This will return the complete risk path from source to targets.

Traversal - Network Risk

1 # Base URL
2 GET api.sayari.com/v1/traversal/:id
3 
4 # Query Parameters
5 relationships:
6   - has_shareholder
7   - subsidiary_of
8 psa: true
9 max_depth: 6
10 ofac_sdn: true
11 export_controls: true
12 
13 # Example curl command
14 curl -X GET "api.sayari.com/v1/traversal/123?relationships=has_shareholder&relationships=subsidiary_of&psa=true&max_depth=6&ofac_sdn=true&export_controls=true"

Network analysis can be computationally intensive. Modify the max_depth parameter judiciously to balance thoroughness with performance.

Best Practices

Reference and Monitor the Risk Factor Documentation or ontology endpoint for accurate traversal parameters.
Monitor response times for deep traversals and consider reducing max_depth if performance is a concern.

PSA risk factors

PSA (Possibly-Same-As) risk factors identify potential risk through entity similarities that suggest a relationship but lack definitive proof for merging via Entity Resolution.

Identify PSA Risk

Similar to Seed Risk, the values for PSA Risk are returned as booleans. Each PSA Risk will reference the associated entity in the PSA group carrying the risk.

Entity Response - PSA Risk

1 {
2     "risk": {
3         "psa_export_controls": {
4             "value": true,
5             "metadata": {
6                 "export_controls_entity": [
7                     "uiLYAQIp356DCBA9DNz3jQ"
8                 ]
9             },
10             "level": "critical"
11         }
12     }
13 }

Call the Entity Endpoint

Query the /entity endpoint using the entity_id returned in the metadata from Step #1.

GET api.sayari.com/v1/entity/{entity_id}

Review Enity Risk

Entity Response - PSA Risk

1 {
2     "risk": {
3         "export_controls": {
4             "value": true,
5             "metadata": {
6                 "source": ["USA Consolidated Screening List"]
7             },
8             "level": "critical"
9         }
10     }
11 }

Evaluate risk intelligence

Review detailed metadata about the source generating the risk:

Entity Response - Risk Intelligence

1 {
2     "risk_intelligence": {
3         "data": [{
4             "properties": {
5                 "type": "export_controls",
6                 "list": "Entity List (EL)",
7                 "License Policy": "Case-by-case basis"
8             }
9         }]
10     }
11 }

Best Practices

Always retrieve and review the referenced entity profile
Evaluate the risk_intelligence data for PSA-connected entities

FAQ

What do the risk factor values represent?

Seed and PSA Risk factors return boolean values indicating presence/absence of risk. Network Risk returns numeric values showing the number of relationship “hops” to the nearest risk target.

How can I get network risk parameters?

Network risk parameters can be obtained either from the Risk Factor Documentation or programmatically from the Sayari ontology endpoint

Where can I find the complete list of risk factors?

The complete list of risk factors and their visibility methods (seed, network, psa) can be found in the Risk Factor Documentation

How frequently are existing Risk Factors updated?

Sayari provides (24 hour) updates for sanctions list and watchlist data. Network Risk Factors are refreshed approximately every two weeks in coordination with our Knowledge Graph Data Builds to ensure comprehensive risk assessment across entity relationships.

How frequently are new Risk Factors added?

New Risk Factors are continuously evaluated and added to enhance Sayari’s risk coverage. Follow our Sayari Product Change Log for announcements about newly introduced risk factors and coverage expansions.

How can I provide feedback about risk?

For questions or feedback about risk factors, contact your Sayari Representative. We actively incorporate user feedback to improve our risk methodology and data sources.

Overview

Sayari has three methods for determining Risk Factors. This guide details how to properly identify and implement each.

Review our Risk Factor Documentation for the full list of risk factors and their visibility method: (seed, network, psa)

Seed Risk

Direct associations between entities and authoritative risk sources.

Network Risk

Risk exposure through business relationships, ownership structures, and trading activity.

PSA Risk

Risk propagation through possibly-same-as entity groups.

Getting Started

Every Risk Factor object in the API response follows a consistent structure:

Entity Response - Risk - Field Descriptions

1 {
2     "risk": {
3         "some_risk_factor_name": {
4             // The unique identifier for this risk factor
5             "value": true,
6             // Boolean for Seed/PSA risks, numeric for Network risks
7             "metadata": {
8             // Additional context about the risk factor
9                 "source": ["..."],
10             },
11             "level": "critical"
12             // Risk severity: critical, high, or elevated
13         }
14     }
15 }

Seed Risk

Seed Risk Factors identify direct connections between entities and authoritative risk sources like sanctions lists, regulatory databases, or adverse media records.

Identify Seed Risk

The values for Seed Risk are returned as booleans

Entity Response - Seed Risk

1 {
2     "risk": {
3         "wro_entity": {
4             "value": true,
5             "metadata": {
6                 "source": ["USA CBP Withhold Release Orders and Findings List"]
7             },
8             "level": "critical"
9         }
10     },

Review Risk Intelligence on the Entity Profile

Each Seed Risk Factor includes a matching risk_intelligence object that contains detailed metadata about the source generating the risk.

Entity Response - Risk Intelligence

1   "risk_intelligence": {
2       "data": [{
3           "properties": {
4               "type": "wro_entity",
5               "authority": "USA Department of Homeland Security",
6               "list": "USA CBP Withhold Release Orders and Findings List",
7               "status": "Active",
8               "from_date": "1995-10-06"
9           },
10           "record": ["b222c03b9eb324d0969f40af61bb4e36"]
11       }]
12   }
13 }

Best Practices

Always check the risk_intelligence object for complete context
Review all metadata fields including authority, list, status, and dates
Track the source lists generating each Risk Factor

Network Risk

Network risk factors analyze entity relationships to detect indirect risk exposure through business networks, ownership structures and trading relationships throughout the Sayari Knowledge Graph.

Identify Network Risk

Entity Response - Network Risk

1 {
2 "ofac_50_percent_rule": {
3     "value": 3,
4     "metadata": {},
5     "level": "high"
6 },

Identify traversal parameters to create paths to Target Entities

Network risk parameters can be obtained in two ways:

Reference the Risk Factor Documentation for parameter specifications
Programmatically parse them from the Sayari ontology endpoint

These parameters define the methodology for calculating network risk by specifying relationship types, traversal depth, and risk factor combinations.

Network Risk Params

1   -max_depth: 6
2   -PSA: True
3   -Seed Risk: ['ofac_sdn']
4   -Relationships: ['subsidiary_of', 'has_shareholder']

Call the Traversal Endpoint

Query the /traversal endpoint pairing the entity_id from step #1 with the Network Risk Params obtained in Step #2. This will return the complete risk path from source to targets.

Traversal - Network Risk

1 # Base URL
2 GET api.sayari.com/v1/traversal/:id
3 
4 # Query Parameters
5 relationships:
6   - has_shareholder
7   - subsidiary_of
8 psa: true
9 max_depth: 6
10 ofac_sdn: true
11 export_controls: true
12 
13 # Example curl command
14 curl -X GET "api.sayari.com/v1/traversal/123?relationships=has_shareholder&relationships=subsidiary_of&psa=true&max_depth=6&ofac_sdn=true&export_controls=true"

Network analysis can be computationally intensive. Modify the max_depth parameter judiciously to balance thoroughness with performance.

Best Practices

Reference and Monitor the Risk Factor Documentation or ontology endpoint for accurate traversal parameters.
Monitor response times for deep traversals and consider reducing max_depth if performance is a concern.

PSA risk factors

PSA (Possibly-Same-As) risk factors identify potential risk through entity similarities that suggest a relationship but lack definitive proof for merging via Entity Resolution.

Identify PSA Risk

Similar to Seed Risk, the values for PSA Risk are returned as booleans. Each PSA Risk will reference the associated entity in the PSA group carrying the risk.

Entity Response - PSA Risk

1 {
2     "risk": {
3         "psa_export_controls": {
4             "value": true,
5             "metadata": {
6                 "export_controls_entity": [
7                     "uiLYAQIp356DCBA9DNz3jQ"
8                 ]
9             },
10             "level": "critical"
11         }
12     }
13 }

Call the Entity Endpoint

Query the /entity endpoint using the entity_id returned in the metadata from Step #1.

GET api.sayari.com/v1/entity/{entity_id}

Review Enity Risk

Entity Response - PSA Risk

1 {
2     "risk": {
3         "export_controls": {
4             "value": true,
5             "metadata": {
6                 "source": ["USA Consolidated Screening List"]
7             },
8             "level": "critical"
9         }
10     }
11 }

Evaluate risk intelligence

Review detailed metadata about the source generating the risk:

Entity Response - Risk Intelligence

1 {
2     "risk_intelligence": {
3         "data": [{
4             "properties": {
5                 "type": "export_controls",
6                 "list": "Entity List (EL)",
7                 "License Policy": "Case-by-case basis"
8             }
9         }]
10     }
11 }

Best Practices

Always retrieve and review the referenced entity profile
Evaluate the risk_intelligence data for PSA-connected entities

FAQ

What do the risk factor values represent?

Seed and PSA Risk factors return boolean values indicating presence/absence of risk. Network Risk returns numeric values showing the number of relationship “hops” to the nearest risk target.

How can I get network risk parameters?

Network risk parameters can be obtained either from the Risk Factor Documentation or programmatically from the Sayari ontology endpoint

Where can I find the complete list of risk factors?

The complete list of risk factors and their visibility methods (seed, network, psa) can be found in the Risk Factor Documentation

How frequently are existing Risk Factors updated?

How frequently are new Risk Factors added?

How can I provide feedback about risk?

For questions or feedback about risk factors, contact your Sayari Representative. We actively incorporate user feedback to improve our risk methodology and data sources.

1	{
2	"risk": {
3	"some_risk_factor_name": {
4	// The unique identifier for this risk factor
5	"value": true,
6	// Boolean for Seed/PSA risks, numeric for Network risks
7	"metadata": {
8	// Additional context about the risk factor
9	"source": ["..."],
10	},
11	"level": "critical"
12	// Risk severity: critical, high, or elevated
13	}
14	}
15	}

1	{
2	"risk": {
3	"wro_entity": {
4	"value": true,
5	"metadata": {
6	"source": ["USA CBP Withhold Release Orders and Findings List"]
7	},
8	"level": "critical"
9	}
10	},

1	"risk_intelligence": {
2	"data": [{
3	"properties": {
4	"type": "wro_entity",
5	"authority": "USA Department of Homeland Security",
6	"list": "USA CBP Withhold Release Orders and Findings List",
7	"status": "Active",
8	"from_date": "1995-10-06"
9	},
10	"record": ["b222c03b9eb324d0969f40af61bb4e36"]
11	}]
12	}
13	}

1	{
2	"ofac_50_percent_rule": {
3	"value": 3,
4	"metadata": {},
5	"level": "high"
6	},

1	-max_depth: 6
2	-PSA: True
3	-Seed Risk: ['ofac_sdn']
4	-Relationships: ['subsidiary_of', 'has_shareholder']

1	# Base URL
2	GET api.sayari.com/v1/traversal/:id
3
4	# Query Parameters
5	relationships:
6	- has_shareholder
7	- subsidiary_of
8	psa: true
9	max_depth: 6
10	ofac_sdn: true
11	export_controls: true
12
13	# Example curl command
14	curl -X GET "api.sayari.com/v1/traversal/123?relationships=has_shareholder&relationships=subsidiary_of&psa=true&max_depth=6&ofac_sdn=true&export_controls=true"

1	{
2	"risk": {
3	"psa_export_controls": {
4	"value": true,
5	"metadata": {
6	"export_controls_entity": [
7	"uiLYAQIp356DCBA9DNz3jQ"
8	]
9	},
10	"level": "critical"
11	}
12	}
13	}

1	{
2	"risk": {
3	"export_controls": {
4	"value": true,
5	"metadata": {
6	"source": ["USA Consolidated Screening List"]
7	},
8	"level": "critical"
9	}
10	}
11	}