Coverage guide
Global screening starts with explicit coverage
Choose named jurisdictions and versioned source packages without assuming one universal sanctions list exists.
On this page
Define the sources your decision needs
Different authorities publish different subjects, restrictions, and effective dates. Combining selected sources can support a broader review, but it does not create a universal legal clearance service. Your policy should identify which authorities and list categories apply to the activity.
SanctionsKit accepts an explicit sources array or a versioned package. Package membership is fixed by its version. A new package version can add a source without silently changing what an earlier version means. Read the API response coverage alongside the requested package.
Keep a missing source visible
A required source that is disabled, unqualified, or too stale prevents a successful screening. SanctionsKit does not substitute a smaller set and label the result no match. Your integration should route a coverage error to an operational hold or another approved review process.
Package membership is fixed by version, while current availability comes from source discovery and freshness checks. Consult current coverage for records and successful check times, then inspect the selected sources in the returned result. A request cannot complete if a required member is unavailable; use a different selection only through an explicit decision under your policy.