Read the source registry
GET /api/v1/sources requires sources:read. Use its source IDs, supported subject types, availability, and current version information to build your selection. Check the jurisdiction and category as well as the name: an enforcement register is not interchangeable with a financial sanctions list.
Use the available sources and current version timestamps returned for your environment. The dataset directory explains each source and links to its public records; the coverage guides explain scope. A list entry, a regulatory action, and a public-office record have different meanings. Choose coverage that fits your workflow.
curl --fail-with-body https://www.sanctionskit.com/api/v1/sources \
-H "Authorization: Bearer $SANCTIONSKIT_API_KEY"Choose one selection method
A screening supplies sources, an array of stable IDs, or package, an exact versioned package identifier. Do not send both. Package membership belongs to its version; adding a source requires a new package version. Sandbox requests use sandbox@1.
The us-enforcement@1 package covers OCC enforcement actions and the two FTC debt-industry ban lists, supporting person and organization requests. BIS boycott requesters and FDIC failed banks remain separately selectable reference sources with their own supported entity types. The us-healthcare@1 package covers HHS-OIG and the seven implemented state exclusion feeds. These sources have different meanings: reference data, enforcement actions and program exclusions do not all impose financial sanctions. Check current availability before requesting a package.
Unknown source IDs and packages are rejected. Required sources that are disabled, unqualified, absent from the active release, or outside the freshness policy cause an error. The server does not silently omit a member to return no_match. Keep a distinct coverage-unavailable state in your application.
KEEP BUILDING