API & engineering
Alex
Alex writes SanctionsKit guides on API integration and screening engineering, including client implementations, matching behavior, testing, and reliable data workflows.
Articles by Alex
Browse 40 articles by topic.
Watchlists & coverage 1
Sanctions data freshness: check the source and screening versions
Distinguish source imports, active versions, and completed customer screenings so a recent timestamp does not hide an outdated check.
OFAC screening 1
Move from OFAC list downloads to a screening API
Plan an OFAC API migration that preserves customer references, checks source availability and connects results to review, evidence and monitoring.
Industry workflows 1
Fintech AML screening API integration: requests, results and review
Implement the sanctions-screening step in fintech onboarding with a synthetic request, safe retries, retained results and a clear analyst handoff.
Matching & case review 4
Sanctions name matching: understand fuzzy matches and evidence
Learn how sanctions name matching finds candidates, why a score is not proof of identity, and which facts help a reviewer resolve a match.
Sanctions screening testing: build useful acceptance cases
Test API results, failed checks, analyst review, monitoring, and evidence with synthetic cases, then record exactly what each test proves.
Sanctions screening thresholds: compare Standard and Focused
Evaluate matching sensitivity with the same labeled cases. Compare missed candidates and extra alerts before changing a SanctionsKit policy.
Sanctions screening false negatives: trace a missing match
Find why an expected sanctions candidate did not reach review by checking submitted facts, source versions, matching policy, and the handoff.
Ongoing monitoring 1
Sanctions monitoring webhooks: verify, store, and process events
Build a webhook receiver that checks signatures, handles duplicate deliveries, retrieves current evidence, and keeps human review separate.
API integration 6
Sanctions screening API integration: a rollout checklist
Connect a sanctions screening API to real review work. Test result handling, retries, source failures, monitoring, and evidence before Production.
OFAC API: add sanctions screening to your application
Connect to the OFAC screening API, choose SDN or non-SDN coverage, and send matches to your review team. Start with a working sandbox example.
Sanctions screening API cost: estimate your usage
Estimate sanctions screening API cost with worked examples for check volume and review time. Count completed checks, batch subjects and repeat monitoring.
Sanctions screening API tutorials by language and source
Build a screening integration with language examples, source discovery, result handling and a clear handoff to dashboard review.
Build vs buy sanctions screening: compare the ongoing work
Compare building a sanctions screening system with buying one, including data upkeep, matching tests, analyst review, evidence and operating cost.
Integrate SanctionsKit with an AI coding agent and MCP
Connect your coding agent, sign in, and ask it to build a SanctionsKit integration. Start with these three steps.
Language tutorials 25
OFAC API in Node.js: backend customer screening
Build a Node.js OFAC API check with native fetch. Keep keys on the server, retry one saved operation, and send SDN matches to review.
OFAC API in Python: customer screening workers
Run an OFAC API check in Python without extra packages. Use the standard library, preserve retry keys, and save SDN evidence for customer review.
OFAC API in PHP: onboarding with cURL
Add an OFAC API check to a PHP onboarding form with cURL. Keep the key on the server and link SDN results to the customer’s review.
OFAC API in Ruby: background screening jobs
Use the OFAC API in a Ruby background job with Net::HTTP. Save the screening ID and reuse the same operation key when retrying a customer check.
OFAC API in Go: screening services
Build a Go service for OFAC API checks using the standard HTTP client. Select SDN coverage, handle failed requests, and save results for review.
OFAC API in Rust: screening workers
Call the OFAC API from a Rust worker with a blocking HTTP client. Keep request failures separate from SDN matches and completed no-match results.
OFAC API in Swift: trusted backend screening
Connect a Swift backend to the OFAC API. Keep secret keys out of distributed apps and route SDN matches into a saved review record.
OFAC API in Java: customer onboarding
Add OFAC API checks to a Java onboarding service. Run the Java 21 example with Jackson, then save SDN results and handle retries without duplicate checks.
OFAC API in C# / .NET: ASP.NET onboarding
Connect an ASP.NET service to the OFAC API with C# and HttpClient. Run a sandbox check, preserve retry keys, and link SDN evidence to review.
UK sanctions API in Node.js: FCDO coverage and customer checks
Call the UK sanctions API from Node.js with native fetch. Select the FCDO UK Sanctions List and keep source references with each customer check.
UK sanctions API in Python: customer portfolio checks
Build a Python worker for UK sanctions API checks. Screen a customer portfolio against the FCDO list and retain partial dates for review.
UK sanctions API in Go: explicit source selection
Select the FCDO list in a Go UK sanctions API request. Keep the source ID explicit and treat missing required coverage as a failed check.
Canadian sanctions API in Python: autonomous list customer screening
Use the Canadian sanctions API in Python for the autonomous list. Check customer records and preserve the cited regulation with each possible match.
Canadian sanctions API in Swift: identity review in a backend
Add Canadian autonomous sanctions checks to a Swift backend. Keep API keys on the server and link source records to your identity review.
Canadian sanctions API in PHP: company screening
Screen suppliers with the Canadian sanctions API in PHP. Select the autonomous list and keep bilingual names and company IDs with the result.
Australian sanctions API in Node.js: onboarding with DFAT data
Add Australian sanctions API checks to Node.js onboarding. Select the DFAT list and retain its record references when aliases produce a possible match.
Australian sanctions API in Ruby: DFAT screening jobs
Run Australian sanctions API checks in a Ruby background job. Use DFAT source IDs and save alias evidence with the customer’s review.
Australian sanctions API in C# / .NET: DFAT data in ASP.NET
Call the Australian sanctions API from an ASP.NET service. Use C# to select DFAT coverage, inspect errors, and retain evidence for review.
U.S. CSL API in Java: screen shipment parties
Screen shipment parties through the U.S. CSL API in Java. Keep each candidate’s originating list and restriction with the review evidence.
U.S. CSL API in Rust: review component list evidence
Use the U.S. CSL API in a Rust trade-screening service. Preserve the component list behind each candidate so reviewers can check the actual restriction.
U.S. CSL API in Go: screen trading partners
Build a Go worker for U.S. CSL API checks on trading partners. Link results to local records and keep the originating list visible during review.
EU sanctions API in Node.js: customer screening
Use the EU sanctions API from Node.js to check financial-sanctions records. Preserve source IDs, partial dates and regulation references for review.
EU sanctions API in Python: customer screening workers
Build a Python worker for the EU sanctions API’s financial list. Save each screening ID and compare the listed party with known customer details.
UN sanctions API in Node.js: screen and review UN candidates
Use the UN sanctions API in Node.js for listed people and entities. Keep UN references and aliases with results; vessels need separate coverage.
UN sanctions API in Python: customer screening workers
Use the UN sanctions API in a Python worker for people and entities. Save screening IDs and preserve weak-alias labels for review.
Research 1
Read sanctions screening evidence with the AI SDK
Give an AI SDK tool one retained sanctions screening result for human review. Preserve source records and retention limits without starting a new screening.