Project Entity Supply Chain Screening
Summary
The Sayari API helps you monitor and assess risks in your global supply chain by:
- Matching your suppliers against Sayari’s knowledge graph
- Mapping multi-tier supply chain relationships
- Identifying potential risks (direct, and indirect via upstream network effects)
- Tracking upstream product flows through HS codes and Sayari’s Product Blueprint technology
- Monitoring risk changes over time with notifications for added or removed risks
5-Minute Quick Start
What You’ll Build
A simple supply chain monitor that checks a single supplier for risks.
Prerequisites
- Your API credentials (
client_id
andclient_secret
) - A supplier to check (
name
,address
,country
)
Get Your Access Token
First, authenticate with the Sayari API to get a bearer token.
View API Schema
Request
Response
View Response
Token expires in 24 hours - Store it securely and reuse it
Create a Project
Create a project container to organize your supplier entities.
View API Schema
Request
Response
View Response
Key Response Fields:
id
: this is the project_id we’ll reference this key in the following requests
Add Your First Supplier
Match your supplier against Sayari’s database to identify potential risks.
Read our Understanding Project Entity guide to familiarize yourself with the core concepts of Project Entities.
To retrieve additional risk metadata such as descriptions, utilize the Get Risk Factors endpoint.
View API Schema
Path parameters
Request
Response
View Response
Key Response Fields:
project_entity_id
: Use for supply chain queries and to reference the project entity in other API callsstrength
: Match confidence (strong/partial/no_match)risk_categories
: Array of risk categoriesrisk_factors
: Detailed risk identifiersupstream.products
: HS codes of products handled by supplierhas_upstream
: Boolean indicating whether the supplier has upstream data
View Supply Chain Summary
Get a high-level overview of your supplier’s entire supply chain, including countries, risks, and products.
View API Schema
Path parameters
Query parameters
Response
View Response
Response contains:
upstream.countries
: All countries in supply chainupstream.risk_categories
: Categorized risks with factorsupstream.components
: Product HS codes present
Get Detailed Supply Chain Paths
Retrieve specific supply chain paths with detailed trade relationships, dates, and locations.
View API Schema
Path parameters
Query parameters
Response
View Response
Monitor Risk Changes
Track risk changes on your monitored entities by polling the notifications endpoint.
View API Schema
Path parameters
Query parameters
Response
View Response
Key Response Fields:
resource_id
: This is yourproject_entity_id
risk_notifications.added
: New risks detected for the entityrisk_notifications.removed
: Risks that have been resolved or removedrisk_notifications.date
: When the risk change occurred
Important Notes:
- Parse the
risk_notifications
array, not thenotifications
array - The
resource_id
field corresponds to yourproject_entity_id
- Poll this endpoint on a 24-hour cadence for optimal results
- The notifications endpoint is being enhanced but remains fully functional for production use
Complete API Workflow
View Complete API Workflow Diagram

Phase 1: Authentication & Setup
Phase 2: Entity Matching & Risk Assessment
Match & Resolve Suppliers
POST /v1/projects/{project_id}/entities/create
- Find and match suppliers in Sayari’s knowledge graph
Input Requirements:
name
- Company nameaddress
- Physical addresscountry
- ISO country code (e.g., KHM)identifier
(optional) - Tax ID, registration number
Key Outputs:
project_entity_id
- Unique identifier for API callsstrength
- Match confidence (strong
/partial
/no_match
)risk_categories
- Categorized risk factorsupstream.products
- HS codes of products handled
Phase 3: Supply Chain Analysis
Get Supply Chain Overview
GET /v1/projects/{project_id}/entities/{project_entity_id}/supply_chain/upstream_summary
Returns:
upstream.countries
- All countries across supply tiersupstream.risk_categories
- Risk factors by categoryupstream.components
- Product HS codes present- Aggregated view perfect for dashboards and reporting
Phase 4: Monitoring & Alerts
Poll for Risk Changes
GET /v1/notifications/projects/{project_id}
- Check for risk changes on monitored entities
Polling Cadence:
- Recommended: Every 24 hours
- Maximum: Every hour (respect rate limits)
Response Processing:
resource_id
maps toproject_entity_id
risk_notifications.added
contains new risksrisk_notifications.removed
contains resolved risksrisk_notifications.date
shows when changes occurred
Integration Tips:
- Set up scheduled jobs/cron for automated polling
- Send alerts to compliance teams for new critical risks
- Update internal risk dashboards automatically
- Log all risk changes for audit trails
Understanding the Response Data
Match Confidence Levels
Risk Categories Explained
For a complete list of risk factors and their definitions, see the Risk Factor Table in our library documentation.
Understanding HS Codes
HS Codes are classifications used in international trade to identify specific products and materials. For more details, see the HS Codes endpoint. The endpoint currently accepts HS Codes up to 4 digits at the sub-chapter level.
- 6004: Knitted fabrics with elastane
- 5201: Raw cotton
- 3907: Polyacetals and polyesters
- 5402: Synthetic filament yarn
- 6001: Pile fabrics, knitted or crocheted
Interpreting Supply Chain Paths
Supply chain paths show the specific trade relationships and flow of goods from your supplier up through multiple tiers. Here’s how to read the path structure:
Path Structure Overview
Each path represents a complete supply chain route from your matched supplier to upstream entities:
Understanding Tiers
Supply chain tiers represent the distance from your supplier:
- Tier 1: Your matched supplier (source_entity_id)
- Tier 2: Direct Suppliers to your matched supplier
- Tier 3: Suppliers to your Tier 2 suppliers
- Tier 4: Suppliers to your Tier 3 suppliers
- Tier 5: Suppliers to your Tier 4 suppliers
Component Details
Each component represents a traded product or material:
Key Points:
hs_code
identifies the specific product (e.g., “6004” = knitted fabrics)arrival_countries
shows arrival countries / areas of importdeparture_countries
shows departure countries / areas of export- Date range shows when these trades occurred
Reading Trade Flows
Example Path Interpretation:
This tells us:
- Marvel Garment (e0WEtIhAvDUjWs-hg12jSA) has a complex 5-tier supply chain
- Tier 2: Sources knitted fabrics (HS 6004) from Vietnam to Cambodia
- Tier 3: Vietnamese supplier sources synthetic yarn (HS 5402) domestically
- Tier 4: Japanese supplier provides polyester materials (HS 3907) to Vietnam
- Tier 5: US chemical company supplies raw chemicals (HS 2909) to Japan
- Supply chain spans multiple countries: USA → Japan → Vietnam → Cambodia
Best Practices
Performance Tips
- Batch suppliers - Add multiple suppliers per project
- Filter early - Use parameters to reduce response size
- Store project Entity IDs - Store Project Entity Ids, they are reliable and stable
- Be mindful of rate limits - Utilize rate limiting strategies such as exponential backoff and retry mechanisms
Data Quality
- Provide identifiers - When possible, provide identifiers to return more accurate, precise matches
- Use ISO country codes - KHM not Cambodia
Additional Resources
API Documentation Links
- Authentication: Get Token Endpoint
- Projects: Create Project
- Entity Matching: Create Project Entity
- Supply Chain Analysis:
- Monitoring: Project Notifications
- Risk Definitions: Risk Factor Table
- Rate Limits: Rate Limits
- Response Codes: Response Codes
- Understanding Project Entity: Understanding Project Entity
Last Updated: August 2025