Start with a concrete contract
Use the OpenAPI reference, complete TypeScript and Python HTTP examples, and a versioned REST endpoint. Explore synthetic subjects before connecting a production workflow.
Sanctions screening for developers
Add sanctions screening to your application.
Get structured sanctions screening results inside your application. Your plan also includes a compliance dashboard where your team can investigate potential matches from the API and record decisions.
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
Built around your work
Your application needs more than a yes or no.
A screening integration has to handle potential matches, retries, coverage gaps, and human review. SanctionsKit gives those paths explicit contracts, so your team can make each outcome part of the application instead of burying it in a support queue.
Handle coverage deliberately
Request explicit sources or a versioned package. Unavailable requested coverage produces an error, so your application can distinguish an incomplete check from a completed result.
Give reviewers an included dashboard
Potential API matches enter your dashboard review queue. Retained history, source evidence, and analyst decisions give your team a shared place to investigate.
A practical use case
An onboarding check that has a review path.
Your application submits a customer identity. A potential match needs a different next step from an unavailable source or a completed no-match result.
The review challenge
A single boolean forces your code to treat an incomplete check and a completed screening alike.
How SanctionsKit helps
Use explicit outcomes, preserve the screening reference, and let the compliance team investigate the same result in the dashboard.
- 01
Explore the sandbox contract
Use the public demonstration and quickstart to understand subjects, coverage selection, and the shape of a screening response.
- 02
Connect your decision paths
Handle potential_match, no_match, and API errors separately. Reuse an idempotency key when retrying the same screening request.
- 03
Give reviewers useful context
Open retained API results in the dashboard and record an analyst decision. Keep secrets and identity inputs out of application logs.
Evaluate the fit
Questions from your team.
Can I explore the sanctions API for free?
Yes. The public demonstration is free and uses synthetic subjects without an account. The quickstart and API reference explain the integration contract. Production screening uses a paid plan and available, qualified coverage.
Does a no-match response mean a customer is cleared?
It means no potential match was found in the selected sources for that completed screening. Keep this outcome separate from your own onboarding decision and other required checks.
How should my integration handle retries?
Send an Idempotency-Key for a new screening and reuse it only when retrying that same request. Replaying an accepted request does not add another completed-screening unit.
See SanctionsKit in action
Explore the request. Then try the review workflow.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.