# Northdata Company Monitor: Register Notices & Changes (`automatic/northdata-company-monitor`) Actor

Know the day a supplier, customer or borrower changes. Watch European companies on Northdata and get only the new register notices plus officer, address, status and name changes since your last run. Built for KYB, supplier-risk and credit teams.

- **URL**: https://apify.com/automatic/northdata-company-monitor.md
- **Developed by:** [Philip Kirkbride](https://apify.com/automatic) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 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 Company Monitor: Register Notices & Changes

Know the day something changes at a supplier, customer or borrower. Put your European counterparties on a watchlist and hear about new register notices and changes to their name, address, status or management, delivered once and only when something happened. Built for KYB and onboarding teams, supplier-risk and procurement desks, credit analysts and anyone who needs to keep an eye on a counterparty.

**Start with `{}` for a quick sample:** BASF SE and SAP SE, up to 10 records. The Console form is prefilled with BASF SE.

- **Only what is new, never twice.** Schedule it daily or weekly and each run returns just the new notices and company changes since the last one. Records you already received never come back, even after an interrupted run.
- **Corrections arrive as updates.** When a notice is amended or a company changes its name, address, status or officers, you get the record again marked `updated`, with the changed fields named.
- **Quiet days stay quiet.** When nothing changed, the run returns nothing and costs almost nothing, so a large watchlist is cheap to keep on a daily schedule.
- **The right company, or a clear message.** Look companies up by URL, by name or by register number in Germany, Austria, Switzerland, France, the Netherlands, the UK, the Nordics and other countries Northdata covers. A lookup that leads to a different company is reported, never silently swapped in.
- **Company records:** registered name, former names, status, legal form, country, register court and number, LEI and EUID, address, industry code, corporate purpose, founding date, latest public revenue, earnings and total assets with year and currency, named officers with current ones first, and the five newest publications.
- **Publication records:** each register notice, filing or public event with its Northdata ID, date, type, source register and title, including notices that concern a related company.
- **Alerts where you work:** send each run's results to Slack, email or your own webhook with Apify integrations.

### Also available

The company registry suite: pick the job.

| Actor | Use when |
|---|---|
| **Northdata Company Monitor (this Actor)** | European register notices and company changes |
| [Norway Company Registry](https://apify.com/automatic/norway-company-changes-monitor) | Norwegian companies and registry changes |
| [UK Companies House](https://apify.com/automatic/companies-house-scraper) | UK company profiles, officers and filings |
| [France Company Registry](https://apify.com/automatic/france-company-registry-scraper) | French companies with legal notices |
| [BORME Spain Corporate Acts](https://apify.com/automatic/borme-es-scraper) | Spanish incorporations, appointments and capital changes |
| [Sanctions & AML Screener](https://apify.com/automatic/opensanctions-screener) | Screen names and wallets against sanctions lists |

### Watch a portfolio

Schedule this daily or weekly:

```json
{
  "companyUrls": [
    "https://www.northdata.com/BASF%20SE,%20Ludwigshafen%20a%C2%B7%20Rhein/Amtsgericht%20Ludwigshafen%20a.Rhein%20HRB%206000",
    "https://www.northdata.com/Zalando%20SE,%20Berlin/Amtsgericht%20Charlottenburg%20(Berlin)%20HRB%20158855%20B"
  ],
  "registerIds": ["093363z", "CHE-101.602.521"],
  "onlyNewSinceLastRun": true,
  "ledgerName": "key-suppliers",
  "maxItems": 500
}
```

The first run returns each company once plus its publications from the last 7 days. Every later run with the same `ledgerName` returns only new or changed records; an unchanged portfolio returns nothing. To start quietly, set `"bootstrapMode": "baseline"`: the first run saves the current state and returns nothing.

Nothing is ever delivered twice: if a run stops early (time or spending limit, interruption), the next run carries on with the companies and records that were left, and never repeats what you already received.

### One-off company lookup

```json
{"companyNames": ["SAP SE, Walldorf", "Novo Nordisk A/S, Bagsværd"], "registerIds": ["Amtsgericht Charlottenburg (Berlin) HRB 158855 B"], "maxPublicationsPerCompany": 20, "maxItems": 100}
```

A name that matches more than one company is never guessed. The run summary lists up to five possible matches with their URLs so you can pick the right one. When only one active company carries the name and the others are terminated, the active one is used and the summary says so.

### Inputs

| Field | Meaning |
| --- | --- |
| `companyUrls` | Northdata company pages (northdata.com, .de or .fr). |
| `companyNames` | Registered names, ideally with the city, such as `SAP SE, Walldorf`. |
| `registerIds` | Register numbers as Northdata shows them, such as `Amtsgericht Mannheim HRB 719915` (Germany, with the court), `FN 93363 z` (Austria), `CHE-101.602.521` (Switzerland), `CVR 24256790` (Denmark), `BR 923609016` (Norway) or `PRH 0112038-9` (Finland). |
| `onlyNewSinceLastRun` | Monitor mode: only new or changed records since the previous run with the same ledger. |
| `ledgerName` | Name of your saved watchlist state (default `default`). Use one per schedule. |
| `bootstrapMode` | `emit` (default): first run returns each company plus 7 days of publications. `baseline`: first run returns nothing. |
| `overlapHours` | Late publications dated within this many hours before the newest one seen are still reported (default 48). |
| `resetLedger` | Start the ledger over. |
| `includePublications` | Include publications (default on). |
| `includeIpFilings` | Include patent, trademark and design filings (default off). |
| `maxPublicationsPerCompany` | One-off runs: also return this many newest publications per company as separate records (default 0). |
| `publicationSince` | Only publications on or after this date; in monitor mode, the first-run window. |
| `maxItems` | Records per run, 1–2,000 (default 25). In monitor mode anything left over is delivered first next run. |
| `requestIntervalSecs` | Seconds between page requests, 3–30 (default 4). |

Up to 500 companies per run across the three lists. Duplicate entries, and different entries that lead to the same company, are returned once.

### Output example

Every record has `recordType` (`company` or `publication`), `changeType` (`snapshot` in one-off runs; `new` or `updated` in monitor mode), `changedFields` and a stable `idempotencyKey`. Two dataset views show companies and publications as tables; export as JSON, CSV or Excel, or read them through the Apify API.

A real publication record from the `{}` sample run on 13 November 2026:

```json
{
  "recordType": "publication",
  "changeType": "snapshot",
  "changedFields": [],
  "idempotencyKey": "d86a744cd10169c0f7b5563e96a6ac46",
  "companyId": "4615068824240128",
  "companyName": "SAP SE",
  "country": "DE",
  "publicationId": "4510387438485504",
  "publicationDate": "2026-10-21",
  "publicationDatePrecision": "day",
  "publicationType": "register_or_corporate",
  "publicationSource": "Hrcdd",
  "publicationSourceName": "German Trade Register daily updates",
  "publicationTitle": "No longer Authorized signatory (ppa) (7)",
  "topicTypes": ["Role"],
  "isBundle": false,
  "viaCompanyName": null,
  "viaCompanyUrl": null,
  "publicationSourceUrl": "https://www.northdata.com/?id=4510387438485504",
  "relatedCompanyId": "4615068824240128",
  "sourceUrl": "https://www.northdata.com/SAP%20SE,%20Walldorf/Amtsgericht%20Mannheim%20HRB%20719915",
  "input": "SAP SE (sample)",
  "ledgerName": null,
  "scrapedAt": "2026-11-13T22:26:39Z"
}
```

A company record has `companyId`, `companyName`, `formerNames`, `status`, `legalForm`, `country`, `registryName`, `registryNumber`, `registerId`, `lei`, `euid`, `otherIdentifiers`, `city`, `postalCode`, `registeredAddress`, `industry`, `industryCode`, `corporatePurpose`, `foundingDate`, `revenue`, `revenueYear`, `currency`, `earnings`, `earningsYear`, `totalAssets`, `totalAssetsYear`, `employeeCount`, `employeeYear`, `premiumOnlyFields`, `officers` (name, role and `isCurrent`), `authorizedSignatoryCount`, `publicationCount`, `lastPublicUpdate`, `recentPublications` and `sourceUrl`.

### Run summary (OUTPUT)

The `OUTPUT` record in the run's key-value store reports `status`, records delivered by type, `new`, `updated`, `unchanged`, `pending` (kept for the next run), `failedInputs` with a reason and, for ambiguous names, up to five possible matches, `skippedSearches` for company entries that could not be read at all (a typo or a link that is not a Northdata company page), `duplicateInputs`, `companiesUnchecked`, `companyChecksCharged` and `complete`. A skipped entry never stops the other companies from being checked. Input the Actor cannot use at all (an out-of-range limit, conflicting modes, every entry in a list unreadable) ends successfully with `status: "no_results"` and the fix, before any request.

### Pricing

**$0.006 per record plus $0.005 per run start.** A record is one company record or one publication record. The start fee is charged per GB of memory; the default 256 MB run is one start event.

**Monitor mode adds $0.0005 per company checked.** It is charged once per watched company whose page was read and compared in that run, so a quiet watchlist costs a fraction of a cent per company. Companies that could not be read are not charged, and one-off lookups never pay it.

| Run | Records | Cost |
| --- | ---: | --- |
| Sample `{}` | up to 10 | 10 × $0.006 + $0.005 = $0.065 |
| 100 companies, one-off (`maxItems` 100) | 100 | 100 × $0.006 + $0.005 = $0.605 |
| 100-company daily watch (`maxItems` 500), first run | 100 + last week's publications | 100 × $0.006 + 100 × $0.0005 + $0.005 = $0.655, plus $0.006 per publication |
| Same watch, first run with `"bootstrapMode": "baseline"` | 0 | 100 × $0.0005 + $0.005 = $0.055 |
| Same watch, a quiet day | 0 | 100 × $0.0005 + $0.005 = $0.055 |
| Same watch, a day with 3 new publications | 3 | 3 × $0.006 + 100 × $0.0005 + $0.005 = $0.073 |
| Same watch, 30 days with about 3 new records a day | ~90 | 30 × $0.073 ≈ $2.19 a month |

A spending limit on the run is respected exactly: the run stops before a check or record it could not pay for, says how many it allowed, and the next run carries on where it stopped.

### Good to know

- A run checks roughly 6–10 companies per minute; the default one-hour run fits about 400 companies. Companies not reached in time are checked first on the next monitor run.
- Values come from Northdata's free public company pages. Figures Northdata reserves for subscribers (often employee counts, sometimes revenue) stay empty and are named in `premiumOnlyFields`; nothing is estimated.
- `officers` lists people Northdata names with a role on the company page, current officers first. `isCurrent` is `true` when Northdata shows the appointment as running, `false` when it shows it as ended, and empty when the page does not say; Northdata shows this for a limited number of people per company, so an officer with an empty `isCurrent` may have left. Signatories (Prokura) are counted, not listed. No personal contact details are collected.
- `lastPublicUpdate` is the date of the newest publication among the types you include: patent, trademark and design filings count only with `includeIpFilings`.
- Status is `active` unless Northdata marks the company terminated or in liquidation.
- Publication titles are Northdata's short summaries. `isBundle` marks yearly summary entries such as "37 trademark filings"; their title grows during the year and is then reported as an update.
- Monitor mode delivers each record at most once. In the rare case that a run is cut off at the very moment it writes, a record can be skipped rather than repeated. Two runs with the same `ledgerName` never work at once: the second one stops with a message.
- Register numbers work best with their prefix or court as Northdata shows them (`CVR 24256790`, not `24256790`). A number or name that leads to a different company is listed in the run summary with that company's URL instead of being returned.
- This is not an official register extract.

# Actor input Schema

## `companyUrls` (type: `array`):

Company pages on northdata.com (or .de/.fr), for example https://www.northdata.com/BASF SE, Ludwigshafen a. Rhein/Amtsgericht Ludwigshafen a.Rhein HRB 6000. Up to 500 companies per run across all three lists. Leave all three lists empty for a quick two-company sample.

## `companyNames` (type: `array`):

Registered name, ideally with the city, for example 'SAP SE, Walldorf'. A name that matches more than one company is not guessed: the run lists possible matches in OUTPUT so you can pick the right URL.

## `registerIds` (type: `array`):

Court and register number as Northdata shows it, for example 'Amtsgericht Mannheim HRB 719915' (Germany), 'FN 93363 z' (Austria), 'CHE-101.602.521' (Switzerland), 'CVR 24256790' (Denmark), 'BR 923609016' (Norway) or 'PRH 0112038-9' (Finland). Ambiguous numbers, and numbers that lead to a different company, are reported, never guessed.

## `onlyNewSinceLastRun` (type: `boolean`):

Turn on for scheduled watchlists. Each run returns only new or changed publications and company changes since the previous run with the same ledger name. The first run returns each company once plus its last 7 days of publications (see bootstrap).

## `ledgerName` (type: `string`):

Name of the saved watchlist state, for example 'suppliers-de'. Use one ledger per schedule; two runs with the same ledger must not overlap. Monitor mode only (default: 'default').

## `bootstrapMode` (type: `string`):

What the first monitor run does for a company it has not seen before. Monitor mode only (default: emit).

## `overlapHours` (type: `integer`):

Publications that appear late are still reported if they are dated within this many hours before the newest one already seen. Monitor mode only (default: 48).

## `resetLedger` (type: `boolean`):

Forget the saved state of this ledger and start a new baseline. Monitor mode only.

## `includePublications` (type: `boolean`):

Register notices, filings and other public events listed on the company page (default: on). Off returns company records only.

## `includeIpFilings` (type: `boolean`):

Patent, trademark and design filings are skipped by default because large companies have hundreds. Turn on to include them (default: off).

## `maxPublicationsPerCompany` (type: `integer`):

In a one-off run, also return this many of each company's newest publications as separate records (default: 0; every company record already lists its 5 newest). Monitor mode returns every new publication instead.

## `publicationSince` (type: `string`):

Only publications dated on or after this day (YYYY-MM-DD). In monitor mode this sets the first-run window instead of the default 7 days.

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

Stop after this many records (company plus publication records; default 25). In monitor mode anything left over is kept and delivered first next run.

## `requestIntervalSecs` (type: `number`):

Polite pacing between Northdata page requests (default 4). Northdata pages are large; expect roughly 6–10 companies per minute.

## Actor input object example

```json
{
  "companyUrls": [
    "https://www.northdata.com/BASF%20SE,%20Ludwigshafen%20a%C2%B7%20Rhein/Amtsgericht%20Ludwigshafen%20a.Rhein%20HRB%206000"
  ],
  "maxPublicationsPerCompany": 5,
  "maxItems": 10
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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 = {
    "companyUrls": [
        "https://www.northdata.com/BASF%20SE,%20Ludwigshafen%20a%C2%B7%20Rhein/Amtsgericht%20Ludwigshafen%20a.Rhein%20HRB%206000"
    ],
    "maxPublicationsPerCompany": 5,
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("automatic/northdata-company-monitor").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 = {
    "companyUrls": ["https://www.northdata.com/BASF%20SE,%20Ludwigshafen%20a%C2%B7%20Rhein/Amtsgericht%20Ludwigshafen%20a.Rhein%20HRB%206000"],
    "maxPublicationsPerCompany": 5,
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("automatic/northdata-company-monitor").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 '{
  "companyUrls": [
    "https://www.northdata.com/BASF%20SE,%20Ludwigshafen%20a%C2%B7%20Rhein/Amtsgericht%20Ludwigshafen%20a.Rhein%20HRB%206000"
  ],
  "maxPublicationsPerCompany": 5,
  "maxItems": 10
}' |
apify call automatic/northdata-company-monitor --silent --output-dataset

```

## MCP server setup

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

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/8JCQpqzfX39OhEJe5/builds/KgsnaOI1K6bmcIlVH/openapi.json
