Global Sanctions & Banned Persons Screening

Search people and companies across 5 official sanctions and banned-persons sources in one run.

This Actor is built for fast sanctions-list screening and public restricted-party checks before onboarding, payments, supplier setup, counterparty review, or periodic re-screening. Instead of manually searching several government lists one by one, you can run a single query and get back normalized results with source tags, match categories, and retrieval timestamps.

It currently covers:

• OFAC SDN
• EU Financial Sanctions
• Canada Autonomous Sanctions
• AU ASIC Banned Persons
• AU ASIC Banned Organisations

If you need a quick answer to questions like:

• Does this person or entity appear on a major public sanctions list?
• Does this name appear in Australia banned or disqualified registers?
• Which public list produced the match?

this Actor is the right starting point.

---

Who is this for?

• Compliance, AML, and onboarding teams screening counterparties before activation
• Fintech and payments teams checking names before processing funds or opening accounts
• Procurement and operations teams screening suppliers and partners
• Due-diligence researchers adding sanctions checks to a broader company or person review
• Investigative journalists and analysts checking public restricted-party records
• Developers and automation teams building public sanctions screening into workflows

This Actor is most useful when you want the public-list screening layer without manually visiting several government sources.

---

What this Actor does

This Actor queries the enabled sanctions and banned-persons sources in parallel and returns a unified dataset.

1. Sanctions-list screening

With includeSanctionsLists enabled, the Actor searches:

• OFAC SDN
• EU Financial Sanctions
• Canada Autonomous Sanctions

Typical use cases:

• pre-onboarding checks for a person or company
• basic restricted-party review before payment or procurement
• periodic re-screening of an existing customer or supplier list

2. Banned and disqualified persons screening

With includeBannedPersons enabled, the Actor searches:

• AU ASIC Banned Persons
• AU ASIC Banned Organisations

Typical use cases:

• checking whether a person appears in Australian banned or disqualified registers
• adding public banned-person signals to a cross-border diligence workflow

3. Batch screening

You can submit multiple search terms in one run. This is useful for:

• vendor or supplier screening
• internal portfolio re-checks
• periodic database re-screening

Each hit is returned as a separate record with source attribution.

---

Default example

This example matches the Actor's default input:

{
  "searchTerms": ["Rosneft"],
  "includeSanctionsLists": true,
  "includeBannedPersons": true,
  "maxResultsPerSource": 50
}

This means the default run:

• screens the term Rosneft
• searches all enabled sanctions lists
• searches all enabled Australian banned-persons sources

---

Example use cases

New counterparty screening

Before onboarding a company or individual, run the name through the enabled public sanctions and banned-persons sources and review any returned matches.

Supplier review

Before issuing a purchase order or starting a commercial relationship, search the supplier name and relevant principals against public sanctions and banned-persons sources.

Payment or transfer control

Before releasing funds or approving an account workflow, screen the relevant person or entity name across the enabled sources.

Periodic re-screening

Run a fresh search across an existing list of customers, suppliers, or partners to identify newly surfaced public-list matches.

Research and investigations

Use the Actor as a structured public-list lookup when researching companies, groups, or individuals appearing in sanctions-related contexts.

---

What you get back

Each result includes source-specific fields plus normalized metadata so you can inspect mixed-source results in one table.

Common fields include:

• name
• type
• status
• country
• authority
• _product_id
• _source
• _source_list
• _match_category
• _search_term
• _collected_at

Depending on the source, records may also include fields such as:

• entity_type
• program
• nationality
• other_names
• sanctions_programme

The Actor also writes a RUN_SUMMARY record to the default Key-Value Store with:

• per-source status
• per-source result counts
• per-source duration
• error information where applicable

This is useful when a source is slow or temporarily unavailable and you want to retry with visibility into what succeeded.

---

Data sources

The current source set is explicit and fixed.

Source	Authority	Category
OFAC SDN	US Treasury	sanctions_list
EU Financial Sanctions	European Commission	sanctions_list
Canada Autonomous Sanctions	Global Affairs Canada	sanctions_list
AU ASIC Banned Persons	ASIC	banned_person
AU ASIC Banned Organisations	ASIC	banned_person

Toggle mapping

Toggle	Sources
includeSanctionsLists	OFAC SDN, EU Financial Sanctions, Canada Autonomous Sanctions
includeBannedPersons	AU ASIC Banned Persons, AU ASIC Banned Organisations

---

Input reference

Parameter	Type	Default	Description
searchTerms	array of strings	["Rosneft"]	One or more person, company, or entity names to screen
includeSanctionsLists	boolean	true	Include OFAC, EU, and Canada sanctions sources
includeBannedPersons	boolean	true	Include AU ASIC banned and disqualified records
maxResultsPerSource	integer	50	Maximum results per source; valid range is 1 to 200

Practical guidance

• Use specific names for cleaner results
• Run alternate spellings when you need broader coverage
• Split very large name lists into smaller runs for easier retries and review

---

Sample output patterns

Sanctions-list result

{
  "name": "ROSNEFT OIL COMPANY",
  "type": "Entity",
  "status": "UKRAINE-EO13662",
  "country": "Russia",
  "authority": "OFAC SDN",
  "_source_list": "OFAC SDN",
  "_match_category": "sanctions_list",
  "_search_term": "Rosneft"
}

Banned-persons result

{
  "name": "Example Name",
  "type": "Individual",
  "status": "Disqualified",
  "country": "Australia",
  "authority": "AU ASIC Banned Persons",
  "_source_list": "AU ASIC Banned Persons",
  "_match_category": "banned_person",
  "_search_term": "Example Name"
}

The exact fields vary by source, but the normalized metadata makes it easier to review everything together.

---

Pricing

This Actor uses pay-per-event pricing.

Event	Price
Actor start	$0.005
Each matched result	$0.003

This model works well for:

• one-off screening
• batch sanctions checks
• recurring portfolio re-screening

---

How to use it

In Apify Console

1. Open the Actor
2. Enter one or more values in searchTerms
3. Decide whether to include sanctions lists, banned persons, or both
4. Set maxResultsPerSource
5. Start the run and review the Dataset output

In automation tools

You can run this Actor from:

• Make
• n8n
• Zapier
• LangChain
• Apify MCP-compatible agent workflows

Python example

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run = client.actor("lentic_clockss/global-sanctions-screening").call(
    run_input={
        "searchTerms": ["Rosneft"],
        "includeSanctionsLists": True,
        "includeBannedPersons": True,
        "maxResultsPerSource": 50,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item.get("_source_list"), item.get("name"))

---

When to use this Actor vs something else

Use this Actor when you want:

• public sanctions-list and banned-person screening
• simple multi-source restricted-party checks
• a structured public-list dataset for downstream review

Use something else if you need:

• adverse media
• PEP screening
• fuzzy matching and alias scoring
• enterprise case-management workflows
• broader multi-jurisdiction screening beyond the current covered lists

This Actor is best used as a public-list screening layer inside a wider diligence workflow.

---

FAQ

Does this cover all sanctions lists globally?

No. It covers the currently listed public sources: OFAC, EU Financial Sanctions, Canada Autonomous Sanctions, and the two AU ASIC banned-persons sources.

Does it do fuzzy matching?

No. It performs source searches against the enabled public datasets. If you need broader name expansion, run alternate spellings or add a matching layer downstream.

How fresh is the data?

Freshness depends on the upstream source. Results include _collected_at, which shows when the Actor retrieved the record.

What happens if one source is unavailable?

The Actor continues per source where possible, and the RUN_SUMMARY shows which source succeeded, returned empty, or errored.

Can I screen large lists?

Yes. For large jobs, split name lists into smaller runs so errors are easier to inspect and retry.

Does it deduplicate the same name across lists?

No. Matches from different sources are returned as separate rows with full source attribution.

---

Related Actors

• Global Company Search
• Regulatory Compliance Search
• US Government Contracts Search
• Stealth Web Scraper

Browse more Actors from this publisher at apify.com/lentic_clockss.