# North Data Company Register Extractor (KYB) (`axery/northdata-company-register-kyb`) Actor

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.

- **URL**: https://apify.com/axery/northdata-company-register-kyb.md
- **Developed by:** [Axery](https://apify.com/axery) (community)
- **Categories:** Business, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $13.33 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## North Data Company Register Extractor (KYB)

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

| Field | Type | Notes |
|---|---|---|
| `companies` | array | Full North Data URLs, or the path after `northdata.com/`. |
| `proxyConfiguration` | object | Defaults to Residential. |

#### Finding the right input

Search the company on [northdata.com](https://www.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

```json
{
  "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

```bash
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.

# Actor input Schema

## `companies` (type: `array`):

Full North Data URLs, or the path after northdata.com/ (company name + registration ID as North Data formats it). Find this by searching the company on northdata.com and copying its URL path.

## `proxyConfiguration` (type: `object`):

Apify Proxy settings. Defaults to Residential - Apify's own container IP range can be rate-limited or blocked by services that treat cloud IPs as suspicious regardless of any WAF.

## Actor input object example

```json
{
  "companies": [
    "SAP+SE,+Walldorf/HRB+719915"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `companies` (type: `string`):

One row per company: register data, LEI code, and the full officer list.

# 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 = {
    "companies": [
        "SAP+SE,+Walldorf/HRB+719915"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("axery/northdata-company-register-kyb").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 = { "companies": ["SAP+SE,+Walldorf/HRB+719915"] }

# Run the Actor and wait for it to finish
run = client.actor("axery/northdata-company-register-kyb").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 '{
  "companies": [
    "SAP+SE,+Walldorf/HRB+719915"
  ]
}' |
apify call axery/northdata-company-register-kyb --silent --output-dataset

```

## MCP server setup

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

```

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/gopJo3yhhhXgL6OhG/builds/ux2445c1MMYQIfdZ5/openapi.json