# Northdata Scraper - Company Register, Officers & Financials (`s-r/northdata-company`) Actor

Northdata scraper for company register data from Germany, the Netherlands, Austria, Switzerland and France. Search by company name, North Data URL or register ID and get status, address, LEI, officers, register filings and public financials in one row per company.

- **URL**: https://apify.com/s-r/northdata-company.md
- **Developed by:** [SR](https://apify.com/s-r) (community)
- **Categories:** Lead generation, Business, Developer tools
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 company records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Northdata Scraper - Company Register Data, Officers & Financials

Northdata Scraper collects public company records for Germany, the Netherlands, Austria, Switzerland and France, for B2B sales, KYC, credit checks and private equity research. Find a company by name, Northdata URL or national register ID, then receive its register details, public officers, publication summaries and available financial data in one dataset row.

One input list can mix company names, North Data company URLs and register numbers such as `HRB 42243 München`, `KVK 24330087`, `FN 056247t`, `CHE-106.014.627` or `Siren 919448084`. The scraper returns one structured company row per match, ready for a spreadsheet, a CRM or a data pipeline.

### What Northdata Company Scraper returns

Each company record includes the name used in Northdata's structured metadata, jurisdiction, register ID, company status and retrieval time. Where published, it also includes an address, incorporation date, corporate purpose, previous names, previous addresses, Legal Entity Identifier and European Unique Identifier. The national register number remains a string, preserving leading zeros in Austrian company numbers and the full CHE identifier for Switzerland.

Officers and filings are nested within the company row. This keeps the dataset convenient for CSV exports, CRM enrichment and analysis by company. Officers have their source name and role, plus a known appointment or resignation date when a public dated event states it. Current source members and explicitly reported former mandates are distinguished with the `current` flag. The available history is incomplete; missing dates stay empty rather than being inferred from the company's incorporation date.

| Data group | Fields |
|---|---|
| Identity | `name`, `jurisdiction`, `registry_id`, `register`, `register_court`, `northdata_url`, `lei`, `euid`, `other_ids` |
| Status and history | `status`, `status_raw`, `incorporation_date`, `dissolution_date`, `former_names`, `former_addresses`, `history` |
| Profile | `address`, `corporate_purpose`, `industry` |
| Financials | `financials` (yearly series), `balance_sheet`, `financials_locked` |
| People | `officers` with role, appointment and resignation dates, `officer_count` |
| Register publications | `filings` with normalized `filing_type`, date, description and topics, `filing_count` |

### How to use the Northdata scraper

1. Paste company names, Northdata URLs or register IDs into `queries`, one per line.
2. Optionally pick a `country` to restrict matches to one jurisdiction.
3. Switch off officers, filings or financials if you only need the register identity.
4. Start the run and download the dataset as JSON, CSV, Excel or through the Apify API.

### Input

Enter one or more values in `queries`. The values can be full company names, Northdata company URLs, or supported register IDs. A name search returns up to `max_results` companies per query, with a default of five and a maximum of fifteen. Northdata supplies the relevance order. Short or ambiguous names may return another company first, so use a full legal name or a register identifier when the target entity is already known.

The following input was run against the source and returned Coolblue B.V.:

```json
{"queries":["Coolblue B.V."],"country":"NL","max_results":1,"max_filings":5}
```

Other measured identifiers are `HRB 42243 München` for Bayerische Motoren Werke AG, `056247t` for Red Bull GmbH, `CHE-106.014.627` for Nestlé Nespresso SA and `Siren 919448084` for L'Oreal Europe SAS. `HRA 742098 Stuttgart` returned the limited partnership Lidl 402 GmbH & Co. KG in Bad Wimpfen. German HRA, HRB, GnR, VR, PR and GsR numbers require the court city because the number alone is not unique across German register courts. Austrian identifiers also accept the `FN` prefix and numbers without leading zeros: `FN 93363z` and `FN 93363 z` both return OMV AG with `registry_id: "093363z"`. A space before the final letter is accepted. Dutch identifiers accept the `KVK` prefix.

Swiss CHE identifiers accept digits without dots or with spaces, such as `CHE-106014627`. French SIREN and Dutch KVK numbers accept spaces between digit groups, such as `Siren 919 448 084` and `KVK 24 330 087`. The returned register ID uses the source's canonical form.

An incomplete register number in a mixed list is skipped with a numbered warning. Valid queries still return company rows, and the output has `partial: true`. A list containing only invalid register numbers is rejected without company rows or charges. URLs outside the supported Northdata domains are rejected for the entire list.

Set `country` to `DE`, `NL`, `AT`, `CH` or `FR` to restrict the jurisdiction. An empty value searches the five supported countries. URL and identifier inputs return at most one company each, and the country selection applies to those records as well.

Set `include_officers`, `include_filings` or `include_financials` to false to omit that part of the result. All three default to true. `max_filings` controls the newest publications delivered per company, from zero to two hundred, with a default of twenty-five. Searches copied from other workflows can use `searchQueries`, `search` or `startUrls`; URL entries can be strings or objects with a `url` property. The supported option aliases are `maxResults`, `maxItems`, `includeOfficers` and `includeFinancials`.

| Field | Type | Default | Description |
|---|---|---|---|
| `queries` | list of strings | – | Company names, Northdata URLs or register IDs |
| `country` | `DE`, `NL`, `AT`, `CH`, `FR` or empty | empty (all five) | Restrict results to one jurisdiction |
| `max_results` | integer 1–15 | 5 | Companies per name query |
| `include_officers` | boolean | true | Add officers and dated mandate changes |
| `include_filings` | boolean | true | Add register publication summaries |
| `max_filings` | integer 0–200 | 25 | Newest publications per company |
| `include_financials` | boolean | true | Add public financial series and balance sheets |
| `cursor` | string | – | Continuation token from `next_cursor` |

### Output

The dataset contains one company per row. The measured Coolblue result includes `name: "Coolblue B.V."`, `registry_id: "24330087"`, `jurisdiction: "NL"`, `status: "active"`, `lei: "72450020ONP2TGFMWS03"` and an address in Rotterdam. Its public officer list is empty. The result also contains the requested publication summaries. Full measured examples for all five countries are supplied with the product documentation.

Below is a real result for the input `{"queries":["HRB 42243 München"],"max_filings":5}`. It is shortened for reading: the full row also has four financial metrics with yearly values, a hierarchical balance sheet, 152 officers, five filings and the company history.

```json
{
  "source": "northdata-company",
  "fetched_at": "2026-10-04T22:58:57.405Z",
  "jurisdiction": "DE",
  "registry_id": "HRB 42243",
  "name": "Bayerische Motoren Werke AG",
  "query": "HRB 42243 München",
  "northdata_url": "https://www.northdata.com/Bayerische%20Motoren%20Werke%20AG,%20M%C3%BCnchen/HRB%2042243",
  "register": "District Court of Munich HRB 42243",
  "register_court": "District Court of Munich",
  "status": "active",
  "incorporation_date": "1995-12-12",
  "address": {"street": "Petuelring 130", "postal_code": "80809", "city": "München", "country": "DE"},
  "lei": "YEH5ZCD6E441RHVHD759",
  "euid": "DED2601V.HRB42243",
  "industry": "Manufacture of motor vehicles",
  "financials": [
    {"metric": "Earnings", "values": [
      {"year": 2025, "value": 7294000000, "formatted": "€7.29B", "consolidated": false, "estimate": false,
       "source": "Stock exchange listed companies - Financial Data", "published_on": "2025-12-31"}
    ]}
  ],
  "financials_locked": false,
  "officers": [
    {"name": "Nedeljković, Milan", "role": "CEO", "appointed_on": "2026-05-15", "resigned_on": null,
     "given_name": "Milan", "family_name": "Nedeljković", "country": "DE", "current": true}
  ],
  "officer_count": 152,
  "filings": [
    {"filing_type": "officer_change", "date": "2026-09-10", "description": "Authorized signatory (ppa): Christian Hochapfel",
     "topics": ["Role"], "register_source": "Hrcdd"}
  ],
  "filing_count": 5
}
```

Financial series contain a metric name, reporting year, numeric value, formatted source value and the available publication reference. A balance sheet contains hierarchical items with numeric values and source information. Only publicly visible metrics are returned. Many privately held companies have no public revenue, earnings or employee values. `financials_locked` indicates that the source displays restricted metrics, while warnings explain requested data that was unavailable. A restricted metric is never supplied as an estimated number.

Status is `active` when the source shows no status marker, `in_liquidation` for a liquidation marker, and `dissolved` for termination. Other source markers produce `unknown`, preserving their text in `status_raw`. `dissolution_date` comes from a termination event for a dissolved company. Liquidation dates remain in `history` while the company is still in liquidation.

Publication records retain the source date, description, raw topics and Northdata document reference. They also receive a normalized `filing_type`, such as address change, capital change, officer change or annual accounts. Unknown topics are retained and classified as `other`. Year bundles retain the date supplied by Northdata; these are not necessarily individual register notices. Referenced documents are not downloaded, and access to them may require separate source permissions.

Use jurisdiction and register ID to match a record to national registers. For German matching, include `register_court`. Use a populated `lei` to join Legal Entity Identifier records. These keys support entity matching; they do not establish that information from different sources is current or identical.

### Use cases for Northdata company data

- **B2B sales and lead enrichment**: add register ID, legal address, industry and current managing directors to an account list before outreach.
- **KYC and supplier onboarding**: confirm that a counterparty exists, is active and is registered under the number it supplied, and keep the LEI and EUID for later checks.
- **Credit and risk monitoring**: rerun a portfolio and compare status, insolvency and capital change filings, and officer changes, between runs.
- **Private equity and M\&A screening**: collect public revenue and earnings series and balance sheets for listed or disclosing companies across five countries in one format.
- **Data joins**: link Northdata records to the German Handelsregister, the Dutch KVK, the Austrian Firmenbuch, the Swiss register or the French SIREN database through the register ID, and to GLEIF through the LEI.

### Northdata Scraper compared with other options

| Option | What you get | Limits |
|---|---|---|
| Northdata website | Rich company pages for manual lookups | One company at a time; no bulk export without a paid plan |
| Northdata Data API | Official bulk access | Separate contract and subscription with the source |
| National registers (Handelsregister, KVK, Firmenbuch, Zefix, SIRENE) | Official, sometimes certified, data per country | Five different interfaces, formats and identifier schemes |
| This Northdata scraper | One schema across DE, NL, AT, CH and FR, officers, filings and public financials in one row, pay per company | Public data only; restricted metrics are flagged, not filled in |

Compared with a single-country Handelsregister or KVK scraper, one run covers five jurisdictions and returns the same field names for each, so a mixed European prospect list needs one actor instead of five.

### Pricing

The billing unit is one delivered company record. Its included officers, publication summaries and public financial metrics are part of that company result. Empty results do not incur a company event. There is no separate actor-start event in this product's charge configuration. The current rate is the rate displayed on this actor's Apify pricing tab; review it when setting your run budget.

Free users receive up to ten company records per run. Paid runs can process larger query lists. Large inputs are collected in bounded pages, and the actor follows continuation tokens automatically. When working with the API response directly, send `next_cursor` as `cursor` together with the same original input until no continuation token remains. Always inspect `partial` and `warnings` before treating a collection as complete.

### FAQ

#### Does every company have financial data?

No. Availability depends on what Northdata publishes publicly for that company. Listed companies may have financial series and balance sheets, while private companies may have no metrics or display restricted values. This scraper preserves that distinction and does not supply missing revenue or earnings.

#### Why are there no officers for a Dutch company?

Public officer information can be absent for Dutch records. An empty list means the retrieved company page did not expose those members. It does not imply that the company has no directors, and it should not be used as evidence about governance.

#### Can I retrieve an exact company by register number?

Yes, for supported identifier formats. Include the court city with German HRA/HRB/GnR/VR/PR/GsR numbers; register codes are case-insensitive. A complete company URL is another precise input. Unknown identifiers return a no-result error rather than a row containing unrelated search hits.

#### Is this a certified register extract?

No. The records reproduce public information available through Northdata and include retrieval times and source references. Obtain official extracts from the relevant authority when your workflow requires certified evidence. Source publication dates and retrieval times describe different moments and should both be considered when assessing a record.

#### Is this the same as a North Data scraper?

Yes. North Data and Northdata are the same source, written with and without a space. This actor reads the public company pages and search results of that source.

#### Are company names returned as plain text?

Yes. Names, addresses and officer names are delivered as readable text, so a German limited partnership arrives as `Lidl 402 GmbH & Co. KG` and not with HTML escape codes. The `northdata_url` is a working link to the same company page, which makes the row safe to match on name, register ID or URL.

#### Which countries are supported?

Germany, the Netherlands, Austria, Switzerland and France. Set `country` to one of `DE`, `NL`, `AT`, `CH` or `FR`, or leave it empty to search all five.

#### Can I export the results to CSV or Excel?

Yes. Every company is one dataset row, so the Apify dataset export gives CSV, Excel, JSON or XML directly. Nested officers and filings stay attached to their company and can be flattened in the export settings.

# Actor input Schema

## `queries` (type: `array`):

Company names, Northdata company URLs or register IDs. German HRA/HRB/GnR/VR/PR/GsR IDs require the court city; register codes are case-insensitive.

## `country` (type: `string`):

Restrict companies to this jurisdiction. Empty selects all five supported countries.

## `max_results` (type: `integer`):

Companies per name query, in Northdata relevance order. URL and register-ID queries return at most one.

## `include_officers` (type: `boolean`):

Include publicly visible officers and dated mandate changes. Dutch companies may have no public officers.

## `include_filings` (type: `boolean`):

Include public register publication summaries and Northdata document references.

## `max_filings` (type: `integer`):

Newest publications per company, including year bundles. Zero returns no publication rows.

## `include_financials` (type: `boolean`):

Include public numeric series and balance sheets. Locked Premium values are never collected.

## `cursor` (type: `string`):

Continuation token from next_cursor. Send it with the original input unchanged.

## `searchQueries` (type: `array`):

Alternative input name for queries; combines with other supplied query lists.

## `search` (type: `array`):

Alternative input name for queries; combines with other supplied query lists.

## `startUrls` (type: `array`):

Northdata company URLs as strings or objects with a url property; combines with query lists.

## `maxResults` (type: `integer`):

Alternative input name for max_results. The snake_case field takes precedence when both are supplied.

## `maxItems` (type: `integer`):

Alternative input name for max_results. The snake_case field takes precedence when both are supplied.

## `includeOfficers` (type: `boolean`):

Alternative input name for include_officers. The snake_case field takes precedence when both are supplied.

## `includeFinancials` (type: `boolean`):

Alternative input name for include_financials. The snake_case field takes precedence when both are supplied.

## Actor input object example

```json
{
  "queries": [
    "Coolblue B.V."
  ],
  "max_results": 5,
  "include_officers": true,
  "include_filings": true,
  "max_filings": 25,
  "include_financials": true
}
```

# Actor output Schema

## `results` (type: `string`):

One row per company with nested officers and filings.

## `output` (type: `string`):

Returned counts, partial status and warnings.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "Coolblue B.V."
    ],
    "country": "",
    "max_results": 5,
    "include_officers": true,
    "include_filings": true,
    "max_filings": 25,
    "include_financials": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("s-r/northdata-company").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "queries": ["Coolblue B.V."],
    "country": "",
    "max_results": 5,
    "include_officers": True,
    "include_filings": True,
    "max_filings": 25,
    "include_financials": True,
}

# Run the Actor and wait for it to finish
run = client.actor("s-r/northdata-company").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "Coolblue B.V."
  ],
  "country": "",
  "max_results": 5,
  "include_officers": true,
  "include_filings": true,
  "max_filings": 25,
  "include_financials": true
}' |
apify call s-r/northdata-company --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,s-r/northdata-company"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/eX7oZd2kYMfNw5jL5/builds/AThNBiuTG9VSFzOxg/openapi.json