Updated as published
The lists are updated whenever the relevant authorities do so, on average every 15 minutes, and new lists are added to the feed as they become available, which means that the coverage expands without any action on your part.
Data · Sanctions
Screen against the world's lists as they change
A single feed consisting of sanctions, watchlists, and wanted lists from authorities worldwide, with new lists being added as they are published so that the dataset continues to grow, and with the records being updated on average every 15 minutes; each screening, whether carried out via the SaaS platform or through the API, is based on the most current data and makes use of the original source content stored on each record.
3,000+
Data Points
220+
Countries covered
15 min
Average refresh interval
Versioned
Every record, every change
Why this matters
Your screening is only as current as the data underneath it
A screening engine's quality depends entirely on the data it compares against; if new designations take days to reach your system, or if someone has to manually check the new lists, your AML process is already lagging. Regulators expect you to act on changes as soon as they occur. Most programs currently assemble lists from the original regulator files, each with its own format, and none are versioned; complead handles this and provides a single, normalized, versioned feed.
Deduplicated into one profile
The same individual can be found on a number of the lists, listed under different spellings and aliases. Before the records reach you, we deduplicate and merge them into a single profile, so one person corresponds to one review.
Versioned and logged
The old version is retained whenever a record is altered and all the updates are visible and can be shown to an auditor.
How it works
Scroll to advance
Four steps, from the official source to your screening
-
Step 01
Collect at source
complead obtains each list directly from the issuing authority in its original format, whether that format is a structured file, a published notice or a web page, and new lists are added to the feed when the authorities publish them.
-
Step 02
Normalize and deduplicate
All sources use the same schema for names, aliases, identifiers, programs, and risk categories, and duplicate records are combined so a person who appears on five lists is represented by a single profile with five linked sources.
-
Step 03
Version every change
Each record keeps a version history. Whenever an authority makes an update or removes a designation, the previous state is retained together with the time at which the change took place, and the difference between the versions can be seen.
-
Step 04
Deliver over SaaS or API
You will receive the feed either via the complead platform or through the API, with the source text included on each record, and in each case the screening is carried out using the most up-to-date version of the data.
complead / ingest
- OFAC✓
- EU✓
- UN✓
- UK HMT✓
- data points3000+
- collected atsource
complead / normalise
- oneschema
- duplicatesmerged
- aliases and identifiersaligned
complead / version
- Doev2024.03.18
- priorv2022.06.01
- diffavailable
complead / deliver
- GET/data/sanctions
- record + source text +version
Ingest
Normalise
Version
Deliver
Capabilities
What the data gives you
Full source coverage
Sanctions issued by OFAC, the EU, the UN, and the UK HM Treasury, plus national regimes' regulatory watchlists and wanted lists from more than 150 countries. There is one feed containing over 1,600 such lists, with additional lists being added as they are published.
One profile per person or entity
All sources are converted to the same field format, and duplicate records are combined. If a person occurs on more than one list, they are counted as a single profile with all the source lists attached to it.
Record versioning
The changes, along with their timestamps, are kept for previous states, and since you can compare any two versions of a record side by side, you can see exactly what an authority changed and when.
Original material retained
The original designation text remains on all records and, when explaining a match to a regulator, should be given in the issuing authority's own words, not in summary form.
15-minute refresh
The feed is generally updated every 15 minutes, and any new or amended designations appear in your screening on the same day that they are published, rather than in the following overnight file.
Change feed
A stream of additions, modifications and deletions was created for the purpose of delta screening. Only customers affected by a change are rescreened, not all of them.
Data tour
Three views: the profile, its history and the sources behind it
The whole designation, in one profile
In any standardized profile, the alias, identifier, program, risk category and source text appear on each of the lists.
- All identifiers in one place
- Every source list attached
- Program and risk category
- Source text retained
complead / record
- queryJohn Doe
- listsOFAC SDN, EU, UK HMT
- aliases4
- riskHIGH
What changed, and when
Each record has a versioned history, along with the differences between any two versions.
- Version list per record
- Diff between any two versions
- Change time
- Source of each change
complead / change-log
- change-logv2026.09.01
- nationalityadded
- aliasadded
Every source, listed
A complete list of sources, sorted by type and region, including each source's refresh status.
- Lists by type and region
- Last refresh per list
- Risk category per list
- New lists flagged
complead / coverage
- sanctions130+
- wachlists1.200+
- wanted240+
- new lists added this month3
- allcurrent
Data coverage
Where the data comes from, and what it covers
All entries come from the issuing authority and include version numbers; coverage includes sanctions, regulatory watchlists, and wanted lists from both national and international authorities.
Sanctions
Sanctions, Watchlists, Wanted lists and PEP
Fields
Name, aliases, date of birth, nationality, program, list type, risk category, country, source text
Versioning
Each record has a versioned history
Freshness
Refreshed on average every 15 minutes, with a change feed
Runs on Fusion
The data under every complead screening
This feed powers Client Screening, Payment Screening and KYB. You can use it in complead or obtain the data separately to feed into your own screening engine; in either case, you'll work with the same versioned source.
This product
Sanctions Data
one normalized, versioned feed of sanctions, watchlists and wanted lists
Powers
Fusion engine
the list side of every screening decision
You get
One source
current, citable and consistent across products
Integration
Pull the full feed, or subscribe to the changes
You can retrieve any record via the API, along with its source text and version, or subscribe to the change feed and rescreen only the items that have changed.
// fetch a sanctions record
GET /v1/data/sanctions/records/JohnDoe_ofac
200 OK · record + source_text + version v2024.03.18
// subscribe to the change feed
PUT /v1/data/sanctions/changes "since": "v2024.03.18", "webhook": "https://you.example/list-change"
FAQ
Before you ask us
Which lists are included in the feed?
Sanctions from OFAC, the EU, the UN, and UK HM Treasury, plus national regimes, regulatory watchlists and wanted lists. That's over 3.000 data points in one feed. New lists are added as authorities publish them, with no setup on your side.
How often is the data refreshed?
On average, every 15 minutes. A new or amended designation reaches your screening on the day it is published, not in the next overnight file.
What happens when the same person appears on several lists?
We merge the records before they reach you. Aliases, spellings, and identifiers are aligned into one profile, with every source list attached. One person means one review, not five.
Is the original designation text kept?
Yes. Every record carries the issuing authority’s own text, so you can explain a match to a regulator in the source’s words rather than in a summary.
Which fields does each record include?
Name, aliases, date of birth, nationality, program, list type, risk category, country and source text, in the same schema across every source.
Can we use the data in our own screening engine?
Yes. The feed is available through the API. You can pull any record with its source text and version, or subscribe to the change feed and work from the same versioned source complead uses.
Which complead products run on this data?
Client Screening, Payment Screening and KYB all screen against this feed through the Fusion engine, so a match is the same match in every product.
How is a delisting handled?
A removal is recorded as a new version, not as a deletion. The last listed state stays on the record with the date it was lifted. The removal also appears in the change feed, so affected customers can be rescreened and cleared.
Does the feed include PEP data?
Politically exposed persons are covered in the PEP Database, which is versioned and refreshed the same way. Sanctions and PEP checks can then run against one consistent source.
What if an authority publishes in its own format?
That is the normal case. We collect each list from the issuing authority as it is published, whether that’s a structured file, a notice, or a web page. It is then mapped to one schema, so every source arrives in the same shape.
Testimonials
All case studies
What compliance teams say
We went from checking customers one by one to a single platform that screens more than 3,000 of them around the clock, so our analysts can finally focus on real risk.
We moved from screening customers one by one to a unified platform where our analysts can focus on what actually matters.
We focus on real risks, not false positives, meeting our AML obligations and our customers' expectations.
Screen against the live feed
Provide us with a set of names. During a 30-minute session, we will check them against the current feed and display each match along with its source text and version.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data