EU Financial Sanctions Tracker avatar

EU Financial Sanctions Tracker

Pricing

Pay per usage

Go to Apify Store
EU Financial Sanctions Tracker

EU Financial Sanctions Tracker

Provide a name, country, or program filter. The Actor writes one normalized dataset item per matching designated person or entity from the EU Financial Sanctions Database.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

What this Actor does

Provide a name, country, or program filter. The Actor writes one normalized dataset item per matching designated person or entity from the EU Financial Sanctions Database.

Input example

{
"name": "Wagner",
"legalEntity": false,
"countries": [
"RU"
],
"programs": [
"EU.RUSSIA"
],
"sinceDate": "2024-01-01",
"maxResults": 100
}

Input fields

Provide a name, country, or program filter plus an optional listing-date filter.

  • name (string, user input): Substring match against entity name and aliases.
  • legalEntity (boolean, user input): When true, only legal entities; when false, only natural persons. Omit to include both.
  • countries (array, user input): ISO2 country codes to filter on.
  • programs (array, user input): EU sanction programs (EU.RUSSIA, EU.SYRIA, EU.IRAN, EU.NORTH_KOREA, etc.).
  • sinceDate (string, user input): ISO date (YYYY-MM-DD). Only listings on or after this date are returned.
  • maxResults (integer, user input): Maximum sanction rows to return.
  • apiBaseUrl (string, optional override): Optional upstream API base URL override for local or staging QA.

Output dataset

Each successful upstream response is written to the default dataset.

  • input: Original input value submitted to the upstream API.
  • result: Full upstream API response.

Developer notes

Set EU_FINANCIAL_SANCTIONS_TRACKER_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