Identity & Verification

Sanctions screening API

Screen customers, suppliers and counterparties at onboarding and before payouts. One request searches five official sanctions lists and returns each potential match with the list entry, programs, countries, dates of birth and a match score.

View documentation Try the free tool Explore all APIs

Endpoints Active

POST /v1/sanctions/screen

Example request

curl -X POST -H "X-API-Key: $DOMSCAN_API_KEY" -H "Content-Type: application/json" \
  -d '{"name": "Banco Nacional de Cuba"}' \
  "https://domscan.net/v1/sanctions/screen"

Example response 200 OK

{
  "status": "potential_match",
  "matches": [
    {
      "list": "ofac_sdn",
      "entry_id": "306",
      "name_score": 1,
      "match_type": "exact",
      "matched_name": "BANCO NACIONAL DE CUBA",
      "entity_type": "organization",
      "programs": ["CUBA"],
      "aliases": ["BNC", "NATIONAL BANK OF CUBA"],
      "signals": { "date_of_birth": "no
...

Example request POST /v1/sanctions/screen

Key Features 4

Frequently asked questions 4

HTTP status codes 200 / 400 / 401 / 402 / 409 / 422 / 429

Category Identity & Verification

Endpoints 1

Key Features 4

Frequently asked questions 4

Used by people at these companies

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose domain intelligence to AI agents and internal assistant workflows.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

nametypecountrydate_of_birthliststhresholdlimit

Response fields

Example response

statusmatchestotal_matcheslists

Status coverage

HTTP status codes

200400401402409422429

Endpoints

POST /v1/sanctions/screen

Credits: 2Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

Key Features

Five official lists, refreshed daily

US OFAC SDN and consolidated (non-SDN), UN Security Council, EU financial sanctions and UK sanctions lists, with each list's publication date in every result.

Fuzzy matching built for names

Word order, accents, transliteration, aliases, initials, typos and sound-alike spellings, plus original Cyrillic and Arabic script names.

Signals that never hide a match

A date of birth and country rank matches and are reported as match or mismatch, but the threshold applies to the name alone.

No false all-clear

no_match is returned only when every list was confirmed in the last 72 hours. Otherwise the result is unknown and not charged.

Example request

POST /v1/sanctions/screen bash

curl -X POST -H "X-API-Key: $DOMSCAN_API_KEY" -H "Content-Type: application/json" \
  -d '{"name": "Banco Nacional de Cuba"}' \
  "https://domscan.net/v1/sanctions/screen"

Example response

200 OK json

{
  "status": "potential_match",
  "matches": [
    {
      "list": "ofac_sdn",
      "entry_id": "306",
      "name_score": 1,
      "match_type": "exact",
      "matched_name": "BANCO NACIONAL DE CUBA",
      "entity_type": "organization",
      "programs": ["CUBA"],
      "aliases": ["BNC", "NATIONAL BANK OF CUBA"],
      "signals": { "date_of_birth": "not_provided", "country": "not_provided" }
    }
  ],
  "total_matches": 1,
  "lists": [
    { "id": "ofac_sdn", "status": "checked", "entries": 19457, "published_at": "2026-10-16" },
    { "id": "un", "status": "checked", "entries": 1010 },
    { "id": "eu", "status": "checked", "entries": 6234 },
    { "id": "uk", "status": "checked", "entries": 6408 }
  ]
}

Frequently asked questions

Is a potential match a determination?

No. It is a lead that needs human review against the list entry. DomScan does not decide whether a person or company is the sanctioned party.

Does it cover politically exposed persons (PEPs)?

No. The API screens official sanctions lists only. It does not include PEP, adverse media or watchlists from other sources.

Are screened names stored?

Screening requests are not kept in your request logs. Only usage and billing records are kept.

How many credits does it cost?

Two credits per name. Results that are unknown because a list is out of date or unavailable are not charged.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

HTTP 409 409

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

HTTP 422 422

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

Too Many Requests 429

Rate limit exceeded

Screen a name

Start free View documentation Try the free tool