Sanctions Update Alert — Watchlist Change Monitor avatar

Sanctions Update Alert — Watchlist Change Monitor

Pricing

Pay per event

Go to Apify Store
Sanctions Update Alert — Watchlist Change Monitor

Sanctions Update Alert — Watchlist Change Monitor

Watch a list of names against OFAC SDN and EU consolidated sanctions lists and get ONLY the changes since your last check — a new hit, a hit that disappeared, or an existing hit's details (score, program, alias) shifting.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Tim Zinin

Tim Zinin

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Watch a list of names against OFAC SDN and EU consolidated sanctions lists and get only the CHANGES since your last check — a brand-new hit, an existing hit's details shifting (score, program, alias), or a hit that disappeared. Runs on our own live sanctions screening engine under the hood.

What you get

  • A named "watch" (a list of names) that remembers what it has already shown you.
  • Every scheduled run reports ONLY what changed — a new sanctions hit, an existing hit's score/program/matched-alias drifting, or a hit that no longer matches.
  • Run several independent watches from one Actor (e.g. one for vendors, one for new hires) — each has its own memory.
  • The very first run for a new watch tells you honestly that it's establishing a baseline, not hiding a "no changes" run as if it found something.
  • Runs on Apify: schedule it daily, monitor it, call it from the API, export to JSON/CSV/Excel or push straight into your own pipeline.

How to run it

  1. Click Try for free — no card needed on the free plan.
  2. Paste the names you want watched into Names, optionally a name for this watch.
  3. Hit Start. The first run creates the baseline; schedule it to run again to get a stream of only the CHANGES each time.

Pricing

Pay-per-event: $0.005 per run start + $0.01 per new/changed hit / baseline created. A hit DISAPPEARING (delisted, or dropped below your score threshold) is reported for visibility but never charged — it's the absence of new risk, not a new finding. The "no changes" notice on a quiet run and any error/notice row are also never charged. 10 new/changed hits cost about $0.11 (the one-time start fee plus 10 billed rows).

Input

FieldRequiredWhat it does
namesyesPerson or company names to watch, one per row. Up to 100.
minScorenoMinimum match score to consider (0-1, default 0.5).
baseline_keynoName for this watch, so you can run several independent watches.
max_itemsnoMax new/changed-hit rows delivered (and charged) per run (1-200, default 20).
{
"names": ["Yevgeniy Prigozhin", "Acme Trading LLC"],
"baseline_key": "vendor-list"
}

Output

Baseline-created row (first run for a watch — real output, live run 30.07.2026):

{
"baselineKey": "selftest-sanctions-2",
"found": true,
"changeType": null,
"baselineCreated": true,
"name": null,
"entityName": null,
"listName": null,
"entityType": null,
"program": null,
"matchedName": null,
"score": null,
"currentHitsCount": 50,
"changedHitsCount": null,
"disappearedHitsCount": null,
"error": "",
"summary": "First check for \"selftest-sanctions-2\" — baseline created with 50 current sanctions hit(s). Future runs report only NEW or CHANGED hits against this baseline.",
"checkedAt": "2026-07-30T08:54:19.175Z"
}

New-hit and changed-hit rows (real output, live run 30.07.2026):

{
"baselineKey": "selftest-sanctions-2",
"found": true,
"changeType": "new-hit",
"name": "Yevgeniy Prigozhin",
"entityName": "Yevgeniy Viktorovich LEBEDEV",
"listName": "EU Consolidated",
"program": "UKR",
"score": 0.5,
"error": "",
"summary": "New sanctions hit for \"selftest-sanctions-2\": \"Yevgeniy Prigozhin\" now matches Yevgeniy Viktorovich LEBEDEV [EU Consolidated], program UKR (score 0.5)."
}
{
"baselineKey": "selftest-sanctions-2",
"found": true,
"changeType": "changed-hit",
"name": "Acme Trading LLC",
"entityName": "ACS TRADING LLC",
"listName": "OFAC SDN",
"program": "SDGT",
"score": 0.667,
"error": "",
"summary": "Sanctions hit changed for \"selftest-sanctions-2\": \"Acme Trading LLC\" vs ACS TRADING LLC [OFAC SDN] — score 0.222 -> 0.667."
}
FieldMeaning
baselineKeyWhich watch this row belongs to.
foundtrue for a real result row (a hit or baseline-created); false for a notice/error row.
changeType"new-hit", "changed-hit", or null for a notice row.
baselineCreatedtrue only on the first-ever run for this watch.
nameThe screened name this hit belongs to.
entityName, listName, program, matchedName, scoreThe sanctioned entity's own fields.
currentHitsCountOnly set on the baseline-created row.
disappearedHitsCountOnly set on a "hits disappeared" notice row.
errorEmpty string when the check completed cleanly (including "nothing changed" and "a hit disappeared"); non-empty only on a real problem.
summaryHuman-readable one-liner.

Other tools we built

Related tools for adjacent workflows in compliance and public procurement.

ActorWhat it does
Sanctions Screening APIPair it in the compliance and public procurement workflow: Screen names against the live OFAC SDN and EU consolidated sanctions lists
Tender Alert — New EU Tender WatchPair it in the compliance and public procurement workflow: Watch EU public-sector tenders (TED Europa) matching your keywords/CPV codes and get ONLY the new ones...
Counterparty Risk Rollup — Sanctions, Courts, Registry, HiringPair it in the compliance and public procurement workflow: One call, one row per counterparty: sanctions screening (OFAC + EU), legal-entity registry (GLEIF),...
Company Registry EnricherPair it in the compliance and public procurement workflow: Turn a company name, LEI or UK company number into an official registry card: legal name, status,...
Gov Tender RadarPair it in the compliance and public procurement workflow: Search EU public-sector tenders (TED Europa) by keyword or CPV code, optionally filtered by buyer country

FAQ / Limitations

Is this a legal or compliance determination? No. This is a screening SIGNAL only — verify any hit against official OFAC/EU sources before acting on it. Matching is soft on purpose (a missed hit is worse than a false one), so expect some noise on common names.

What happens if a source list fails to load mid-run? The run reports it honestly and does not touch your baseline or charge you — a "no changes" read off an incomplete list would be a guess, not a real answer.

What this is NOT. Not a substitute for your compliance team's own due diligence process, and not a guarantee of completeness — sanctions lists change on their own schedule, independent of this Actor's run schedule.

Found a bug or need a custom watch? Issues on the Actor's page.