🚨 US OFAC Sanctions Action Watch

OFAC Recent Actions as they are posted: the action's own identifier, its date, its headline and its category (Sanctions List Updates, Regulations and Guidance, and so on). ACTION-LISTING SCOPE: this watches the published actions themselves. It is not the SDN list and it does not enumerate designated parties.

Output is one sanctions_action_record row per result; billing is pay-per-event, the value event being one sanctions action delta (a $0.02 start fee per run, then $0.30 per sanctions action delta plus one $0.10 source check per run that reads the source). Source: ofac.treasury.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run YkfAmZR6lSnBN2HWe on build 0.1.20 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

action_id	title	action_date_text	action_date	category
20260917	Iran-related Designations; Cuba Designations; Belarus-related Designat	September 17, 2026	2026-09-17	Sanctions List Updates
20260916	Russia-related Designations Removals; Counter Narcotics Designation Re	September 16, 2026	2026-09-16	Sanctions List Updates
20260914	Iran-related Designation; Issuance of Amended Venezuela-related Genera	September 14, 2026	2026-09-14	Sanctions List Updates
20260910	Iran-related and Counter Terrorism Designations; Licensing Policy Upda	September 10, 2026	2026-09-10	Sanctions List Updates
20260909	Transnational Criminal Organizations Designations; Counter Terrorism D	September 09, 2026	2026-09-09	Sanctions List Updates
20260908	Iran-related Designations; Counter Terrorism Designations; Updates to	September 08, 2026	2026-09-08	Sanctions List Updates
20260904	Iran-related Designations; Issuance of Iran-related General License	September 04, 2026	2026-09-04	Sanctions List Updates
20260903	Cuba Designations; Russia-related Designation Removal; Issuance of Ame	September 03, 2026	2026-09-03	Sanctions List Updates

The run finished with the status message: NORMAL: emitted 10 item(s)

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_key (string/null) — e.g. ofac:20260917
• action_id — e.g. 20260917
• title — e.g. Iran-related Designations; Cuba Designations; Belarus-related Designations Remov
• action_date_text — e.g. September 17, 2026
• action_date — e.g. 2026-09-17
• category — e.g. Sanctions List Updates
• source_url — e.g. https://ofac.treasury.gov/recent-actions/20260917
• scope_note — e.g. action listing only; designated parties are not enumerated
• record_type (string) — e.g. sanctions_action_record
• delta_type (string/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "pages": 1,
  "category_contains": [],
  "title_contains": [],
  "watch_mode": false,
  "baseline_id": "default",
  "max_items": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.30 sanctions-action-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "pages": 1,
  "category_contains": [],
  "title_contains": [],
  "watch_mode": false,
  "baseline_id": "default",
  "max_items": 5
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
  "pages": 1,
  "category_contains": [],
  "title_contains": [],
  "watch_mode": true,
  "baseline_id": "default",
  "max_items": 10
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.30 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run YkfAmZR6lSnBN2HWe, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "ofac:20260917",
  "action_id": "20260917",
  "title": "Iran-related Designations; Cuba Designations; Belarus-related Designations Removals",
  "action_date_text": "September 17, 2026",
  "action_date": "2026-09-17",
  "category": "Sanctions List Updates",
  "source_url": "https://ofac.treasury.gov/recent-actions/20260917",
  "scope_note": "action listing only; designated parties are not enumerated",
  "record_type": "sanctions_action_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 0
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each sanctions action delta is charged at the moment it is pushed (sanctions-action-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

Source

US Treasury OFAC Recent Actions (public, logged-out)

• https://ofac.treasury.gov/recent-actions

Public, logged-out only — no API key, login, cookie or CAPTCHA.

Snapshot mode is a PREVIEW

watch_mode: false returns at most 25 records, hard-capped in code regardless of max_items, labeled output_mode: "preview". This cell sells change detection, not bulk record export.

Watch semantics

First watch run stores a private baseline and emits zero deltas. Later runs emit NEW / CHANGED / REMOVED keyed on the source-native id with before / after and changed_fields.

Source cadence

OFAC posts actions on business days, often several on one date. Action keys are opaque and same-day actions are distinguished by a suffix, so a date is never used as the key.

Terminal states

NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED. A zero with no evidence FAILS loud rather than exiting 0 quietly.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.07
Sanctions Action Delta (sanctions-action-delta)	$0.30	$0.27	$0.24	$0.20

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 sanctions action deltas: $0.02 start + $0.10 source check + 8 × $0.30 = $2.52
• 25 sanctions action deltas: $0.02 start + $0.10 source check + 25 × $0.30 = $7.62
• 300 sanctions action deltas: $0.02 start + $0.10 source check + 300 × $0.30 = $90.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: emitted 10 item(s). max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by ofac.treasury.gov. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (ofac.treasury.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to max_items (default 300); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other enforcement and sanctions watches actors?
A: Same output shape and billing model; this one covers ofac.treasury.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (max_items) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• India SEBI Enforcement Order Watch — SEBI enforcement orders as they are listed: adjudication orders, Chairman/Member orders, settlement orders and insider-trading orders, keyed on the s…
• US FDIC Bank Status Event Watch — Institution status as published by FDIC BankFind: active flag and end-of-existence date, so a change in standing is observable
• US HHS-OIG Exclusion Change Watch — Monthly additions to and reinstatements from the HHS-OIG List of Excluded Individuals and Entities (LEIE). OIG publishes the change files monthly and…
• EU Consolidated Sanctions Change Watch — Entity-level changes to the EU consolidated financial sanctions list (FSD): primary name, subject type, the regulation programmes an entity sits unde…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.