North Data Company Register Extractor (KYB) avatar

North Data Company Register Extractor (KYB)

Pricing

from $13.33 / 1,000 results

Go to Apify Store
North Data Company Register Extractor (KYB)

North Data Company Register Extractor (KYB)

Scrape European company register data - founding date, address, former names, LEI code, and the full executive/officer list - for Know-Your-Business and compliance research. No login, no API key.

Pricing

from $13.33 / 1,000 results

Rating

0.0

(0)

Developer

Axery

Axery

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 hours ago

Last modified

Share

Scrapes European company register data — founding date, registered address, former names, LEI code, and the full executive/officer list. No login, no API key.

Useful for Know-Your-Business (KYB) compliance checks, counterparty due diligence, and corporate structure research.

What makes this different

Scoped for KYB, not just general company lookup. lei_code and has_lei are first-class fields rather than buried in a raw data dump — a Legal Entity Identifier is a regulator-issued, globally unique ID that many compliance workflows specifically check for, and this Actor surfaces it (and its absence) as a direct flag rather than something you'd have to dig for.

The full officer list, structured. Every executive/board member comes through as their own record — name, job title, and a link to that person's own North Data profile — not flattened into a single text blob. That's what makes a "who actually runs this company" check a filter instead of a manual read.

Former names are kept. former_names (e.g. a company's prior legal name after a rebrand) matters for due diligence — a counterparty check that only looks up the current name can miss history tied to an old one.

A nonexistent entity is reported clearly, not silently. A company path that doesn't resolve to a real register entry still returns HTTP 200 from North Data — the tell is that the embedded structured data becomes a generic site-search schema instead of a business entity, and the page title becomes Search for "..." rather than a company name. Both are checked explicitly, so a bad input path fails with a clear message instead of returning a hollow row.

Input

FieldTypeNotes
companiesarrayFull North Data URLs, or the path after northdata.com/.
proxyConfigurationobjectDefaults to Residential.

Finding the right input

Search the company on northdata.com yourself once, then copy the path from its URL — e.g. SAP+SE,+Walldorf/HRB+719915 from northdata.com/SAP+SE,+Walldorf/HRB+719915. This Actor doesn't search by name alone; it needs the specific register entry.

Output

{
"name": "SAP SE",
"former_names": ["SAP AG"],
"founding_date": "1988-08-04",
"lei_code": "529900D6BF99LW9R2E68",
"has_lei": true,
"street_address": "Dietmar-Hopp-Allee 16",
"city": "Walldorf",
"country_code": "DE",
"officer_count": 80,
"officers": [
{"name": "Asam, Dominik Christian Wolfgang", "job_title": "Member of the Executive Board"}
]
}

Each run also writes a RUN_COVERAGE record to the key-value store with what was requested, what came back, and any per-company failures.

Local development

pip install -r requirements.txt
python test_local.py "SAP+SE,+Walldorf/HRB+719915" --out sample_output.json
python test_local.py "https://www.northdata.com/SAP+SE,+Walldorf/HRB+719915"

sample_output.json is real output from a live run.