Sanctions Change Tracker avatar

Sanctions Change Tracker

Pricing

from $8.00 / 1,000 results

Go to Apify Store
Sanctions Change Tracker

Sanctions Change Tracker

Automate OFAC compliance checks by extracting daily additions and removals from the SDN list. Generate precise JSON diffs for counterparty screening.

Pricing

from $8.00 / 1,000 results

Rating

0.0

(0)

Developer

太郎 山田

太郎 山田

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

OFAC Sanctions List Change Watch Scraper

Use this actor to monitor public OFAC sanctions list changes and configured watch-term matches for internal review workflows. Input OFAC program/type filters or watch terms, then receive source-linked JSON digest rows for additions, removals, and matches. This actor is informational only and is not an OFAC clearance, customer-due-diligence, legal determination, or certification product.

Store Quickstart

  • Start with store-input.example.json for a two-watch (SDGT entities + Cuba programs) dataset run.
  • If that matches your workflow, switch to store-input.templates.json and pick one of:
    • SDGT Quickstart (2-program starter) for first-run validation
    • Named Entity Watch for counterparty name-screening against the SDN list
    • Russia & Iran Program Digest for geo-targeted sanctions tracking
    • Individuals-Only Watch for people-focused screening
    • Webhook Upgrade for compliance automation with action-needed handoff

Key Features

  • 📋 Summary-first output — 1 watch = 1 digest row; raw SDN entries nested under entries
  • 🔄 Change detection — snapshot-backed diff flags new additions and list removals between runs
  • 🔍 Watch-term matching — watch-term matching across SDN entry names and all aliases (case-insensitive)
  • 🗂️ Program & type filtering — scope any watch to OFAC program codes or entity types
  • 🪝 Webhook delivery — route action-needed digests to Slack, compliance tools, or any HTTP endpoint
  • No auth required — OFAC publishes the SDN XML as a public feed

Use Cases

WhoWhy
Compliance teamsDaily/weekly digest of SDN additions for public list-change review
Compliance operationsWatch-term alerting for public OFAC list changes
Risk systemsTrack geo-targeted programs (Russia, Iran, Cuba) for jurisdictional exposure
Procurement & financeReview whether watched vendor or supplier names appear in public OFAC list changes

Input

FieldTypeDefaultDescription
watchesarrayOne entry per watch target. Each watch produces one summary digest row. Set programs and/or sdnTypes to narrow the scope
sdnXmlUrlstring"https://www.treasury.gov/ofac/downloads/sdn.xml"Override the OFAC SDN XML feed URL. The default legacy URL (https://www.treasury.gov/ofac/downloads/sdn.xml) redirects t
maxEntriesPerWatchinteger50Default upper bound on SDN entries in the nested output per watch. Can be overridden per-watch with the maxEntries field
requestTimeoutSecondsinteger60Timeout for the SDN XML fetch. The file is several MB so allow at least 60 seconds.
deliverystring"dataset"dataset stores results in the Apify dataset. webhook posts the digest JSON to webhookUrl.
webhookUrlstringPOST target for the digest payload. Leave empty for dataset delivery.
datasetModestring"all"all emits every watch digest row. action_needed emits only watches with name-match hits. new_only emits only watches wit
snapshotKeystring"sanctions-change-digest-state"Stable key used to persist seen SDN entry UIDs across recurring runs so new_only and action_needed modes stay comparable

Input Example

{
"watches": [
{
"id": "sdgt-entities",
"name": "SDGT Entities",
"programs": "SDGT",
"sdnTypes": "Entity",
"maxEntries": 20
},
{
"id": "name-screen",
"name": "Counterparty Screen",
"watchTerms": "Acme Corp,Example Bank",
"maxEntries": 10
}
],
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "sanctions-change-digest-state"
}

Input Examples

Example: Single-target audit

{
"targets": [
"example-target-1"
],
"maxResultsPerTarget": 30
}

Example: Bulk portfolio

{
"targets": [
"target-1",
"target-2",
"target-3"
],
"maxResultsPerTarget": 50,
"snapshotKey": "sanctions-change-digest-state"
}

Example: Recurring delta watch

{
"targets": [
"target-1"
],
"snapshotKey": "sanctions-change-digest-state",
"emitChangedOnly": true
}

Output

FieldTypeDescription
metaobject
errorsarray
digestsarray
digests[].watchIdstring
digests[].watchNamestring
digests[].programsarray
digests[].sdnTypesarray
digests[].watchTermsarray
digests[].checkedAttimestamp
digests[].statusstring
digests[].newEntryCountnumber
digests[].removedEntryCountnumber
digests[].totalMatchCountnumber
digests[].changedSinceLastRunboolean
digests[].actionNeededboolean
digests[].recommendedActionstring
digests[].signalTagsarray
digests[].watchTermHitsarray
digests[].typeBreakdownobject
digests[].programBreakdownobject
digests[].removedUidsarray
digests[].entriesarray
digests[].errornull

Output Example

{
"meta": {
"generatedAt": "2026-04-03T12:00:00.000Z",
"sdnPublishDate": "04/03/2026",
"sdnRecordCount": 18698,
"newEntries": 3,
"actionNeededCount": 0,
"executiveSummary": {
"overallStatus": "watch",
"brief": "3 new SDN addition(s) and 0 removal(s) detected across 2 watch(es)."
}
},
"digests": [
{
"watchId": "sdgt-entities",
"status": "watch",
"newEntryCount": 3,
"removedEntryCount": 0,
"totalMatchCount": 1847,
"entries": [...]
}
]
}

API Usage

Run this actor programmatically using the Apify API. Replace YOUR_API_TOKEN with your token from Apify Console → Settings → Integrations.

cURL

curl -X POST "https://api.apify.com/v2/acts/taroyamada~sanctions-change-digest/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "watches": [ { "id": "sdgt-entities", "name": "SDGT Entities", "programs": "SDGT", "sdnTypes": "Entity", "maxEntries": 20 }, { "id": "name-screen", "name": "Counterparty Screen", "watchTerms": "Acme Corp,Example Bank", "maxEntries": 10 } ], "delivery": "dataset", "datasetMode": "all", "snapshotKey": "sanctions-change-digest-state" }'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("taroyamada/sanctions-change-digest").call(run_input={
"watches": [
{
"id": "sdgt-entities",
"name": "SDGT Entities",
"programs": "SDGT",
"sdnTypes": "Entity",
"maxEntries": 20
},
{
"id": "name-screen",
"name": "Counterparty Screen",
"watchTerms": "Acme Corp,Example Bank",
"maxEntries": 10
}
],
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "sanctions-change-digest-state"
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor('taroyamada/sanctions-change-digest').call({
"watches": [
{
"id": "sdgt-entities",
"name": "SDGT Entities",
"programs": "SDGT",
"sdnTypes": "Entity",
"maxEntries": 20
},
{
"id": "name-screen",
"name": "Counterparty Screen",
"watchTerms": "Acme Corp,Example Bank",
"maxEntries": 10
}
],
"delivery": "dataset",
"datasetMode": "all",
"snapshotKey": "sanctions-change-digest-state"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Tips & Limitations

  • Run daily for active watchlists; weekly for passive monitoring.
  • Webhook delivery works well for compliance team Slack channels — include docket URL for 1-click access.
  • Use watchKeywords generously — false positives are cheap to triage, false negatives miss filings.
  • Pair with regulatory-change-monitor for cross-agency coverage.
  • Archive Dataset rows weekly for long-term compliance evidence retention.

FAQ

How far back does history go?

This actor monitors forward-only — new items since first run. For historical data, use the agency's own search tool.

What timezones are used?

All timestamps are UTC. Use your downstream pipeline to convert to agency-local time if needed.

Does it translate non-English content?

No — original language is preserved. Use downstream translation services if needed.

Is the data official?

Yes — sourced directly from official government websites and feeds. Not a third-party aggregator.

Can I use this for legal research?

For alerting and monitoring, yes. For litigation research, cross-verify with primary sources (agency websites) — this actor is a monitoring tool, not a legal database.

Government & Regulatory cluster — explore related Apify tools:

Cost

Pay Per Event:

  • actor-start: $0.01 (flat fee per run)
  • dataset-item: $0.003 per output item

Example: 1,000 items = $0.01 + (1,000 × $0.003) = $3.01

No subscription required — you only pay for what you use.

⭐ Was this helpful?

If this actor saved you time, please leave a ★ rating on Apify Store. It takes 10 seconds, helps other developers discover it, and keeps updates free.

Bug report or feature request? Open an issue on the Issues tab of this actor.

Compliance Guardrails

This actor is independently operated and has no source-agency affiliation, sponsorship, or approval. It uses public data from OFAC Sanctions List Service and public OFAC sanctions list downloads (https://ofac.treasury.gov/sanctions-list-service). Results are informational only and may be delayed, incomplete, amended, withdrawn, or superseded by the source. Verify all records with the linked official source before relying on them.

  • Use only public OFAC list/download/search surfaces.
  • Do not market as an OFAC clearance, customer-due-diligence, legal determination, or certification product.
  • Output source URLs, retrieval timestamps, list names, and watch-term match context; users must verify records with OFAC.