Sanctions screening API integrations: Node.js, TypeScript and Python

Start with the API quickstart to create a sandbox key and make one request. Then follow the Node.js and TypeScript tutorial or the Python tutorial. Each uses its runtime’s built-in HTTP library, with complete code you can copy into a new file. No SanctionsKit package or private repository is required.

The OpenAPI specification describes requests, responses and authentication under /api/v1. Use it to generate a client for another language or implement the same HTTPS calls in your existing backend. Keep the API key on your server and use a separate key for each environment and workload.

Send the subject and one explicit coverage selection. A successful response wraps the screening in data. Retain its ID, selected coverage, source versions and review outcome with your authorized business record. A potential match should enter your review process; an error must not become a no-match result. The screening reference explains the fields.

When the first request works, add the pieces your application needs: batch screening for portfolios, monitoring for retained subjects, and signed webhooks for asynchronous events. Test expired keys, quota limits and unavailable coverage as carefully as successful responses. The rollout guide provides a practical checklist.