Choose your runtime
Start with the API quickstart. Create a live key, choose an available source and send one request. The response gives you a screening ID and a result to inspect. The optional sandbox uses made-up source records. Then choose the guide for your application.
For Node.js or TypeScript, you can install the official sanctionskit SDK from npm. See the JavaScript and TypeScript examples, or follow the Node.js tutorial to call the API with built-in fetch. The Python tutorial uses Python's standard library and needs no extra API client package.
For Go 1.26 or later, use the official Go SDK. Its screening example runs an invented screening and retrieves that result's evidence. Follow the Go setup steps to install it, then use the package reference for each method.
For a workflow in n8n, follow the n8n screening tutorial. It covers installing the SanctionsKit community node, connecting a sandbox key, and running a sample workflow that screens an invented person and retrieves the evidence.
To give an AI SDK tool one retained result for human review, follow the AI SDK sanctions evidence tutorial. The tool preserves source evidence without starting a new screening.
Using another language? The OpenAPI specification describes the requests, responses, and authentication under /api/v1. Use it to generate a client or write the HTTPS calls in your backend. Keep the API key on your server. Give each environment and workload its own key.
Connect the result to your workflow
Send the person's or company's details with one coverage choice: source IDs or a versioned package. The successful response puts the screening inside a data object. Save the screening ID, selected sources, and source versions with the business record your team is allowed to keep.
Send a potential match to review. Record a no-match only when the selected check completed without candidates. Keep errors as unfinished work. Save the later review decision separately from the screening status. The screening reference explains each field.
Next, add the parts your workflow needs. Batch screening handles lists of subjects. Monitoring saves subjects for repeated checks. Signed webhooks notify your application about events. Test expired keys, usage limits, and unavailable sources before release. Use the rollout guide to check the full flow.
Frequently asked questions
Which languages can call the SanctionsKit API?
Any backend that can send HTTPS requests can use the API. SanctionsKit provides official Node.js and Go SDKs, a complete Python standard-library example, and tutorials for other languages. Use the OpenAPI document to check the request and response fields when building your own client.
Should I use an SDK or call the screening API directly?
Use an SDK if its supported runtime and methods fit your application. Direct HTTP calls are useful when you want to use your existing request library or another language. Both approaches use the same API contract, source selection, and key scopes. The TypeScript tutorial includes both starting points.
Can I use SanctionsKit without writing a custom API client?
Yes. The n8n integration lets you add a SanctionsKit node to a workflow. Start with its sample screening and evidence steps, then add the branches your process needs. You still choose coverage, handle failures, and send possible matches to a reviewer.
How does an API result reach a human reviewer?
Keep the returned screening ID with your customer or supplier reference. Retained results appear in your SanctionsKit workspace, where the team can inspect the evidence and work on related cases. Your application should show the original screening status separately from the later review decision.
KEEP BUILDING