Primary names and aliases
Use the shared engine’s normalized names, aliases, fuzzy candidates and token comparisons.
"listedName": "…", "aliases": ["…"]THE MATCHAUDIT SANCTIONS API
Sanctions screening, from your own systems.
Screen a person or company against supported sanctions and restricted-party lists. Get potential matches, source references and a timestamped receipt in one JSON response.
JSON over HTTPS
x-api-key or Bearer tokenPOST
/api/v1/sanctions/screenJSONcurl -X POST https://matchaudit.io/api/v1/sanctions/screen \
-H "content-type: application/json" \
-H "x-api-key: $MATCHAUDIT_API_KEY" \
-d '{"names": ["Sandbox Test Person Alpha", "Example Customer Name"]}'Examples use synthetic names. A live key searches the supported source catalogue; the public sandbox uses invented fixtures only.
37supported screening sources
100names per request
Point-in-timescreening request
A RESPONSE YOU CAN WORK WITH
The detail behind every potential match.
Build review into your workflow with source context, visible coverage and results you can interpret.
Similarity scores
Inspect a 0–1 similarity score. It is not a probability of identity; no custom threshold is accepted.
"score": 0.98Batch screening
Submit up to 100 names in one request. Each submitted name uses one monthly check.
{"names": ["Person name", "Company name"]}API reference
Understand what came back.
Each response separates potential matches from source availability. Keep the receipt in your system and review the underlying record before acting.
results[]- One result per input, in the same order.
potentialMatch- A signal to review, rather than a finding about identity.
lists[].status- See which sources were searched and which were unavailable.
receipt- A screening ID, timestamp, source versions and engine version.
{
"results": [
{
"input": "Sandbox Test Person Alpha",
"potentialMatch": true,
"lists": [
{
"key": "sandbox_fixture",
"name": "Synthetic sandbox test list",
"status": "searched",
"dataDate": "2026-11-13T00:00:00.000Z",
"version": "sandbox-fixture-v1",
"matches": [
{
"listedName": "Sandbox Test Person Alpha",
"programme": ["SANDBOX-TEST"],
"reference": "SBX-0001",
"officialUrl": "https://matchaudit.io/sanctions/api/docs#sandbox",
"score": 1
}
]
}
]
},
{
"input": "Example Customer Name",
"potentialMatch": false,
"lists": [
{ "key": "sandbox_fixture", "name": "Synthetic sandbox test list", "status": "searched",
"dataDate": "2026-11-13T00:00:00.000Z", "version": "sandbox-fixture-v1", "matches": [] }
]
}
],
"receipt": {
"screeningId": "6f1c2b9e-0000-4000-8000-000000000000",
"timestamp": "2026-11-13T12:00:00.000Z",
"lists": [
{ "key": "sandbox_fixture", "name": "Synthetic sandbox test list",
"dataDate": "2026-11-13T00:00:00.000Z", "version": "sandbox-fixture-v1" }
],
"engineVersion": "matchaudit-screening@3f2a9c1d0b7e"
}
}Coverage
All supported screening lists. One response.
Published source statistics from the Data sources catalogue, filtered to name-screening datasets supported by this API. Catalogue rows can combine related sources. Each API response shows the actual per-list availability, index data date and version. A scheduled refresh is not a freshness guarantee.
View the full data sources catalogueBrowse published source coverage32 catalogue rows
| List | Jurisdiction | Scheduled refresh | Records | Last source update (UTC) |
|---|---|---|---|---|
| U.S. Consolidated Screening List (CSL) | United States | Every 6 hours | 26,087 | |
| U.S. Consolidated Sanctions (Treasury) | United States | Every 6 hours | 20,052 | |
| Australia — DFAT Consolidated | Australia | Every 6 hours | 11,431 | |
| Switzerland (SECO) — Sanctions | Switzerland | Every 6 hours |
FROM FIRST REQUEST TO YOUR WORKFLOW
From your system to a reviewable result.
- 01
Arrange access
Contact us to confirm your API subscription and account setup. Once access is assigned, generate your key in the API workspace.
- 02
Call the endpoint
POST one name or a batch of up to 100 names. Send your key from your server.
- 03
Act on the result
Review potential matches against the official source and retain the receipt in your own system. Each call is a point-in-time check.
PLAN YOUR SCREENING VOLUME
Choose your monthly screening volume.
One check is one name. All configured tiers include the same full source catalogue, batch screening and receipts. Monthly prices in EUR; B2B service.
View API plansStarter
€29per month
2,500 included checks / monthGrowth
€99per month
15,000 included checks / monthScale
€349per month
75,000 included checks / monthRequest rate is shared across all requests for a key. A separate service-wide public cap also applies. Limits are configurable; your deployment’s settings are shown here. 60 requests / key / minute. Shared cap: 600 requests/minute.
All prices in EUR. No VAT is charged: MatchAudit applies the German small-business exemption (§ 19 UStG).
Live API access is arranged with our team; paid checkout is not enabled on this website.
Before you integrate.
Where does the data come from?
The API attempts all supported name-searchable sanctions and restricted-party lists, including OFAC SDN and Non-SDN, EU consolidated, UK Sanctions List, UN, Swiss SECO, Canadian, Australian and national sources, plus export-control, terrorism and debarment lists. Each result links to its official source and shows per-list availability. Coverage is limited to supported named-party datasets that can be loaded for the request. Country/sector policy rules, PEP data, adverse media and ongoing monitoring are not included. Sources can overlap, and a record's restrictions depend on its source; a match is not automatically an asset-freeze designation.
How accurate is matching?
The shared engine normalizes names and compares primary names, aliases and name tokens, using fuzzy candidate retrieval. Scores describe similarity, not the probability that identities are the same. False positives and missed entries are possible. No measured accuracy benchmark is published for this API.
What about GDPR and retention?
The screening route processes names in memory and does not write names or receipts to its database or application logs. Retain receipts in your own system. Account processing, infrastructure metadata and service providers are described in the site-wide Privacy Notice and DPA.
Do you offer an SLA?
No numerical availability, latency or support-response SLA is included unless expressly agreed. Agree any service commitments in writing before relying on them.
START BUILDING
Your account. Your API workspace.
Discuss your API subscription through our contact form. Once we confirm your plan and assign access, use your MatchAudit account to generate and manage credentials.
A public sandbox key is not configured on this deployment. Read the docs or request live access.
Read the documentationResults are indicative, not legal advice. A name match does not confirm identity or a designation; compare details with the official source.