Screening against OFAC SDN and other U.S. lists
What it does
POST /v1/compliance/restricted-party-screening screens names against the U.S. Consolidated Screening List using fuzzy name matching with alias resolution, then reports potential matches for human review.
Request
curl -X POST https://api.compliancegrid.ai/v1/compliance/restricted-party-screening \
-H "x-api-key: $CG_API_KEY" -H "Content-Type: application/json" \
-d '{"parties": [{"name": "Huawei Technologies", "country": "CN", "type": "CONSIGNEE"}]}'Reading the result
overallResult:CLEARorPOTENTIAL_MATCH. A potential match is a lead, not a verdict: compare country, address and identifierstotalMatches: number of list entries that matched- each match:
listName,matchedName,matchScore(0 to 1),matchType,programs,addresses,ids(for a vessel, the IMO number is inids) listsScreened,listVersion,listRetrievedAt: exactly which lists, and which version, the answer is based on
Lists screened
The 12 lists of the U.S. Consolidated Screening List: OFAC SDN, Sectoral Sanctions Identifications (SSI), Non-SDN Menu-Based Sanctions (NS-MBS), Non-SDN Chinese Military-Industrial Complex Companies (CMIC), Capta List (CAP) and Palestinian Legislative Council (PLC); BIS Entity List, Denied Persons List, Unverified List and Military End User List; State Department ITAR Debarred (DTC) and Nonproliferation Sanctions (ACN).
Not screened: the EU consolidated list, the UN Security Council list and other non-U.S. lists. Screen those separately if your program requires them.
Sensitivity
There is no threshold parameter. Review every potential match, using matchScore and the other match fields to prioritize. Generic industry words in a name are ignored so that unrelated companies do not match.
Record keeping
Each screening is recorded with its list version and can be listed with GET /v1/screenings and read with GET /v1/screenings/{id}; you can set a decision on it. Keep your own copy if your retention rules require a specific period.
Was this article helpful?