Filter OFAC Sanctions Data by Program and Entity Type

Broad sanctions searches are useful for discovery, but program and entity filters make recurring research easier to review. The OFAC Sanctions Scraper can apply those filters while retaining each row's official program tags and list origin.

Choose the dimension first

For program research, leave keyword queries empty and filter the program text. For a vessel inventory, select the SDN list and published vessel type. Combining too many filters at once can hide relevant records, so test each dimension independently before creating a production Task.

{
  "queries": [],
  "listType": "sdn",
  "entityTypes": ["vessel"],
  "programs": ["IRAN"],
  "maxResults": 500
}

Program matching is case-insensitive and partial. That is convenient for related tags, but it also means a short word may match more programs than intended. Inspect the distinct programs values returned by a pilot run, then replace an ambiguous search with a more specific tag.

Measure coverage, not just matches

Record the input, run time, selected list, and number of results. If you compare programs, use the same list selection and cap. A result cap reached at exactly the configured maximum indicates truncation, not a complete census.

Missing entity types are legitimate source nulls. Do not automatically classify them as entities or individuals. Vessel-specific attributes likewise appear only where published. For analysis, group by list type and program, preserve rows with missing classifications, and link every aggregate back to the underlying UIDs.

Filters are most valuable as a reproducible collection rule. They do not change the need to verify records or apply qualified judgment when data is used in a compliance process.