Run your first live check
Start with 250 free live checks. Use the OpenAPI reference and TypeScript or Python examples. You can also test with made-up records in the optional sandbox.
Sanctions screening for developers
Add sanctions checks to your app. Send the known details and the lists to check. Get a clear result with source facts. Your team can review saved matches in the included dashboard. Start with 250 free live checks.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
subjectPerson or organizationcoverageNamed sources or packageresultOutcome + matched evidenceBuilt around your work
The first API call is only the start. Your integration needs a clear path for a possible match, a no-match, and an error. It also needs a way for a reviewer to find the evidence behind the right customer record.
Start with 250 free live checks. Use the OpenAPI reference and TypeScript or Python examples. You can also test with made-up records in the optional sandbox.
Choose named sources or a package version. If a required source cannot be checked, you get an error. Keep the check open while you fix the cause.
Save the screening ID with your own record. Reviewers can open the same result in the dashboard. There is no need to build a review tool first.
Put it into practice
A developer needs to connect a customer record, an API response, and the reviewer’s next step. A result ID provides the link, while explicit outcomes keep each branch of the app clear.
Engineering owns safe requests and error handling. Analysts use the same saved evidence to explain their decisions. Your app keeps control of its customer workflow.
Create a live key and check available sources, or choose a sandbox key for made-up test records. Keep the key on your server. Send one request and save its result ID with your own reference.
Route possible matches to review. Continue the rest of your policy process after no-match. Handle errors separately and retry an unchanged request with the same body and key.
Choose retention before relying on case history. Confirm live sources, scopes, and expected volume, then connect your app to the team that owns review decisions.
Evaluate the fit
Yes. Your first workspace gets 250 free live screenings, shared by the API and dashboard. This is one lifetime allowance, with no monthly reset or credit card needed. The optional sandbox uses made-up records to test matches, no-matches and errors. The quickstart and language guides show complete requests.
Save the returned screening ID with your own customer or supplier reference. Do not rely on the create response to echo every submitted field. Your app needs its own link between the intended operation and the saved result.
Create an Idempotency-Key for a new request. Reuse it only when retrying the same body. A replay of an accepted screening returns the original operation without another completed-screening unit. Changed subject details need a new request.
No. It means the selected check completed without a possible match. Your app must still follow other checks and approvals required by its policy. An error is different again: it means the screening is incomplete.
Saved API results appear in the included dashboard. Possible matches enter the review queue with source facts. Give the team the screening reference so they can find the same result and record their review. Keep the app’s business decision separate from the original API outcome.
See SanctionsKit in action
Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.