← Back to all docs
sanctions.io

Sanctions.io API

Sanctions.io provides up-to-date global sanctions and politically exposed person (PEP) lists you can search via API to check whether people or companies appear on watchlists. An unofficial API from Supergood lets you trigger screenings, tune match logic, subscribe entities to ongoi

By Alex KlarfeldJanuary 23, 2026
Sanctions.io API

What is Sanctions.io?

Sanctions.io is a RegTech data provider focused on financial crime compliance. It aggregates and maintains global sanctions and PEP datasets—such as OFAC SDN, EU Consolidated, UN Security Council, UK HMT, and additional national lists—and exposes them through a developer-friendly API. Teams use Sanctions.io to run KYC/AML checks, screen counterparties and beneficiaries, enable continuous monitoring, and document compliance decisions.

Common data entities:

  • Subjects (persons and organizations)
  • Screening checks and results
  • Watchlist hits (sanctions and PEP matches)
  • Source lists and dataset versions
  • Monitoring subscriptions and alerts
  • Exported screening reports (PDF/JSON)

The Sanctions.io Integration Challenge

Sanctions.io offers powerful data and an API, but production-grade automation still poses challenges:

  • Matching nuance: Fuzzy scores, transliteration, diacritics, and alias handling must be tuned per workflow to balance false positives and misses
  • Monitoring at scale: Keeping subscriptions current, de-duplicating alerts, and aligning processing to rate limits and licensing is non-trivial
  • Audit readiness: Consistently packaging evidence (subject input, list versions, hit rationales) for audits and retention is time-consuming
  • Multi-provider orchestration: Many teams blend Sanctions.io with other vendors; normalizing schemas and scores across systems is tedious
  • Operational reliability: Retries, backoff, and schema change detection are required to keep pipelines stable as datasets and portals evolve

How Supergood Creates Sanctions.io APIs

Supergood wraps authenticated API and portal workflows to deliver a resilient endpoint layer tailored to your entitlements.

  • Secure credential handling: We operate with customer-managed credentials or API keys and rotate sessions automatically
  • Session continuity and health checks: Built-in token refresh, request hedging, and adaptive backoff
  • Normalized objects: Consistent subjects, checks, hits, and reports across Sanctions.io and other providers
  • Entitlement alignment: Enforces your licensing, dataset coverage, and usage limits programmatically
  • Monitoring orchestration: Subscription management, alert fan-out, dedupe, and idempotent processing

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your dataset coverage, licensing, and authentication model.

  • Supergood Builds and Validates Your API

We deliver a hardened Sanctions.io adapter tailored to your workflows and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Sanctions.io evolves.

API Endpoints

Authentication

POST/sessions

Establish a session using an API key or account credentials. Supergood securely stores secrets and maintains session continuity. Returns a short-lived auth token managed by the platform.

Screening

POST/checks

Create a new screening check for a person or company. Configure fuzzy match behavior, list filters, and optional monitoring.

Screening

GET/checks

List checks with filters and summary results.

Reports

GET/reports/{reportId}

Retrieve an audit-ready report for a screening (inputs, list versions, matches, and rationales). Returns metadata and a time-limited signed URL.

Use Cases

KYC/AML Screening Automation

- Trigger person or company screenings during onboarding - Tune fuzzy thresholds and alias handling to your risk appetite - Retrieve normalized hits with source list, program, and match rationale

Transaction and Counterparty Screening

- Screen beneficiaries, vendors, and counterparties pre- or post-transaction - Enrich internal records with list identifiers and entity metadata - Route outcomes to auto-approve, review, or block queues

Continuous Monitoring and Alerting

- Subscribe high-risk customers to ongoing list updates - Receive alert payloads with deltas (new/removed hits, list version changes) - Maintain suppression rules and escalation paths programmatically

Compliance Archival and Audit Trails

- Export complete screening packets with subject inputs, list versions, and evidence - Timestamp and store artifacts for auditability and regulatory retention - Prove coverage with machine-readable, consistent records

Technical Specifications

Authentication

API key or customer-managed credentials; optional SSO/portal flows supported where applicable

Response format

JSON with consistent resource schemas and pagination

Rate limits

Tuned for enterprise throughput while honoring licensing and usage controls

Session management

Automatic token refresh, retries with backoff, and health checks

Data freshness

Near real-time retrieval of checks, hits, and report artifacts

Security

Encrypted transport, scoped tokens, field-level redaction, and audit logging; respects Sanctions.io entitlements

Webhooks

Optional asynchronous delivery for monitoring alerts and long-running report generation

Latency

Sub-second responses for list and detail queries under normal load

Throughput

Designed for high-volume onboarding and batch screening pipelines

Reliability

Idempotency keys, retry logic, and circuit breaking minimize duplicate actions and timeouts

Adaptation

Continuous monitoring for UI and schema changes with rapid adapter updates

Frequently asked questions

Subject to your licensing, we can screen against major global sanctions lists (e.g., OFAC SDN, EU Consolidated, UN SC, UK HMT) and PEP data. We confirm coverage during integration assessment.

You can configure match thresholds, transliteration, and diacritic handling per request. We return detailed scores and rationales and can maintain provider-specific tuning profiles per workflow.

Yes. Enable monitoring at creation or later. Receive alerts via webhooks or polling endpoints, with deduplication, suppression lists, and escalation routing.

Ready to get a real API?