OFAC SDN Monitor
Pricing
Pay per usage
OFAC SDN Monitor
Screen names against official OFAC SDN and Consolidated Sanctions data. The Actor calls the OFAC SDN Monitor API and writes one screening response per name to the default dataset.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
jts
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
16 minutes ago
Last modified
Categories
Share
OFAC SDN Monitor
What this Actor does
Screen names against official OFAC SDN and Consolidated Sanctions data. The Actor calls the OFAC SDN Monitor API and writes one screening response per name to the default dataset.
What data can you get?
Each run writes structured Screening response item rows to the Apify dataset. Common fields include:
| Field | What it means |
|---|---|
kind | screening. |
input | Original submitted name. |
result | Full screening response. |
How to use OFAC SDN Monitor
- Open this Actor in Apify Console.
- Paste the input JSON below or fill the form fields in the Input tab.
- Click Start and wait for the run to finish.
- Open the Dataset tab to preview rows, then export JSON, CSV, Excel, XML, or HTML.
- For production, schedule the Actor or call it from the Apify API, SDKs, webhooks, or MCP server.
When to use this
- Monitor OFAC SDN Monitor API signals in compliance or risk workflows
- Enrich internal records with official/public data linked to this source
- Trigger alerts when new records match your watch criteria
When NOT to use this
- Not a legal determination or official certification document
- Not a replacement for human review of high-stakes decisions
- Not for bypassing source system terms or access controls
Input example
{"names": ["Rosoboronexport"],"limit": 10}
Input fields
Provide one or more names to screen against OFAC sanctions lists.
names(array, user input): Individual or entity names to screen against official OFAC SDN and Consolidated Sanctions data. Use this shortcut when the same country, DOB, ID, alias, strictness, and program options apply to every name.country(string, user input): Optional country hint applied to every name. This improves review precision when the OFAC record includes country or address data.dob(string, user input): Optional date of birth or year applied to every name. Use YYYY, YYYY-MM-DD, or the format already present in your screening workflow.idNumber(string, user input): Optional passport, tax ID, vessel, aircraft, website, or other OFAC identifier to use as an additional match signal.aliasMatch(string, user input): How aliases are compared. Use exact for strict legal-name checks, fuzzy for normal operational screening, or phonetic when names may be transliterated.strictness(string, user input): Match threshold. Higher strictness reduces weak-alias and fuzzy false positives; lower strictness is broader and better for alert triage.programs(array, user input): Optional OFAC program tags to filter by, such as CUBA, SDGT, or RUSSIA-EO14024.limit(integer, user input): Maximum candidate matches returned per screening request.screenings(array, user input): Optional batch mode for per-name options, for example [{"name":"Banco Nacional de Cuba","country":"Cuba","aliasMatch":"fuzzy","strictness":"medium"}]. If present, each object is screened independently.watchlistEntries(array, user input): Optional stateless watchlist preview entries. Use when you want one run to screen recurring counterparties and return a grouped watchlist-style response.apiBaseUrl(string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.
Output dataset
Each dataset item is one sanctions screening response from the upstream API.
kind: screening.input: Original submitted name.result: Full screening response.
Sample output
How can you use the OFAC SDN Monitor data?
- Screen customer, vendor, or counterparty names during onboarding
- Check entity aliases and program tags before payments or shipments
- Run batch sanctions checks from procurement and CRM workflows
- Monitor a small watchlist for daily sanctions-list changes
- Build a human-review queue with explainable match fields and scores
- Normalize upstream compliance data into one Apify dataset contract.
API, integrations, and MCP
- Run this Actor from Apify Console, schedules, webhooks, REST API, or the Apify SDKs.
- Connect the Actor to AI agents through the Apify MCP server.
- Export dataset items to JSON, CSV, Excel, XML, HTML, Google Sheets, S3, or downstream BI tools.
- Use the generated
INPUT.example.jsonas the baseline payload for API calls and scheduled runs.
FAQ
How much does it cost to use this Actor?
Screen names, aliases, identifiers, countries, and DOBs against official OFAC SDN and Consolidated Sanctions XML data. One missed hit can cost far more than monthly API usage, so the tier is priced to recover cost on the first actionable match.
Can I use this Actor with the Apify API?
Yes. Use the same input JSON shown above with Apify's REST API, JavaScript SDK, Python SDK, schedules, or webhooks.
Can I use this Actor through an MCP server?
Yes. Add this Actor to the Apify MCP server so AI agents can run it and consume the resulting dataset.
Is it legal to use this data?
Use this Actor only for the allowed use cases: AML, sanctions, restricted-party, export-compliance, vendor-risk, counterparty-risk, and onboarding screening workflows with appropriate human review of potential matches. Do not use it for prohibited workflows: Harassment, doxxing, unlawful surveillance, FCRA-regulated eligibility decisions, fully automated adverse action without human review, or representing API output as legal advice or an official OFAC determination.
Pricing
Screen names, aliases, identifiers, countries, and DOBs against official OFAC SDN and Consolidated Sanctions XML data. One missed hit can cost far more than monthly API usage, so the tier is priced to recover cost on the first actionable match.
Developer notes
Set OFAC_SDN_MONITOR_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API.
Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json.
For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.
Run locally
$apify run
Deploy
$apify push
Changelog
- 0.1.0 (2026-04-30) — Initial release: OFAC SDN Monitor API marketplace sidecar content.