A contract your code can follow
Use a versioned REST API with OpenAPI documentation and complete TypeScript and Python HTTP examples. Model potential matches, no matches, and errors as distinct application paths.
Sanctions screening REST API
Screen through the API. Get the evidence behind each match.
Screen people and organizations from your application. Receive matched evidence and explicit coverage in a structured response, with an included dashboard for the people reviewing potential matches.
API and compliance dashboard included in every plan.
SanctionsKitIllustrative workflow
POST /api/v1/screenings
subjectPerson or organizationcoverageNamed sources or packageresultOutcome + matched evidence1Potential matchInvestigate the evidence
2No matchContinue your own decision process
3Coverage unavailableResolve the incomplete check
What this helps your team do
Build the paths your screening integration actually needs.
Coverage you select explicitly
Request named sources or a versioned package. Unavailable requested coverage returns an error so your integration never treats an incomplete check as a successful no-match result.
A handoff your team can use
Retained API results appear in the included dashboard. Potential matches enter the review queue with supporting fields, conflicts, and source references attached.
A practical use case
A customer reaches the screening step in your application.
Your application stays responsible for the onboarding decision. SanctionsKit gives it the screening result and the context needed for the next step.
- 01
Submit the known identity
Send the subject and selected coverage to the versioned screening endpoint. Keep the API key in your server environment.
- 02
Handle the outcome deliberately
Route a potential match to investigation, continue your own policy process for a completed no-match result, and resolve errors separately.
- 03
Keep the review connected
Store the screening reference with your internal record. Your team can open retained evidence and record decisions in the dashboard.
For the people behind the process
One capability. Useful to the whole team.
Developers
Less ambiguity in the integration
Explicit outcomes and idempotent retries give each branch of your application a defined behavior.
Explore your workflowCompliance teams
The original evidence reaches review
Investigate API matches in the same workspace as dashboard screenings, with no separate review product to connect.
Explore your workflowOperations
One plan across API and dashboard
Track completed subject screenings against the shared allowance. Looking up a retained result adds no screening unit.
Explore your workflowEvaluate the details
Screening API: practical questions.
Can I explore the sanctions screening API before integrating?
Yes. The public demo uses synthetic subjects and the API quickstart explains the request and response contract. The TypeScript and Python integration guides provide complete HTTP examples using built-in language libraries.
How do retries affect the screening allowance?
Use an Idempotency-Key for a new request and reuse it only to retry that same request. Replaying an accepted screening does not consume another completed-screening unit.
Does a no-match response approve a customer?
No. It means the completed check found no potential match in the selected sources. Your application must keep that screening outcome separate from its onboarding decision and other required checks.
See SanctionsKit in action
Try the result format your application will work with.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.