Monitor OFAC Sanctions List Changes on a Schedule

A one-time sanctions export becomes stale. A useful operational feed needs a stable query, predictable schedule, retained snapshots, and a clear change-review rule. The OFAC Sanctions Scraper supplies the structured rows; an Apify Task supplies the repeatability.

Define the monitored population

Avoid changing filters between runs unless you intentionally create a new baseline. This example monitors records associated with Russia-related program text across both official datasets.

{
  "queries": [],
  "listType": "both",
  "programs": ["RUSSIA"],
  "maxResults": 1000
}

Run it once, inspect the rows, and save the input as a Task. Attach a daily or weekly schedule based on your policy. Send successful datasets to durable storage before the platform retention window expires.

Compare identifiers and fields

Treat list_type + uid as the natural record key. Records in the new snapshot but not the prior one are additions. Missing keys may represent removal or a source change and deserve confirmation. For keys present in both snapshots, compare name, programs, title, vessel fields, and remarks.

Do not alert on row order. Downloaded files can be reordered without a substantive change. Normalize arrays before comparing them, and retain the official source URL and run timestamp in every audit record.

A practical review queue separates new records, removed records, and modified records. Analysts can then prioritize program additions or meaningful remark changes instead of rereading the entire list. If a source request fails, keep the prior successful baseline and flag the monitoring gap; never interpret a failed or empty run as proof that records disappeared.