North Data Company Records Scraper

Export public North Data company and person records for registry research, due diligence, and business-data enrichment. Start from a public profile URL or a company/person search term, then receive one structured record per resolved public profile.

The actor works with publicly displayed North Data pages only. It does not require a North Data account and does not bypass login-only or premium content.

What you get

Each record keeps the source URL alongside public identity and registry context:

• Registered name, entity type, register number, identifiers, address, city, and country
• Public corporate purpose, LEI code, financial series, latest revenue, earnings, and employee count when displayed
• Officer links, related-company links, events, news, and public source/publication links when displayed
• A timestamp and the canonical North Data profile URL for traceability

sourceLinks is especially useful for research workflows: it preserves displayed publication and identity references instead of leaving a result as an untraceable summary.

Ready-to-run examples

• Look up a company by name
• Enrich a known company profile
• Research relationships and events

Input recipes

Look up a company by name

{
  "searchQueries": ["Volkswagen AG"],
  "maxItems": 2
}

Export known public profile URLs

{
  "startUrls": [
    { "url": "https://www.northdata.com/Volkswagen+AG,+Wolfsburg/HRB+100484" },
    { "url": "https://www.northdata.com/Siemens+AG,+München/HRB+6684" }
  ],
  "maxItems": 2,
  "includeFinancials": true,
  "includeOfficers": true
}

Include optional public relationship context

{
  "searchQueries": ["Siemens AG"],
  "maxItems": 1,
  "includeFinancials": true,
  "includeOfficers": true,
  "includeRelatedCompanies": true,
  "includeEvents": true,
  "includeNews": true
}

Input reference

Input	Type	Default	Description
startUrls	array	—	Public North Data company, person, or search URLs.
searchQueries	array	—	Company names, people, or registry terms to resolve on North Data.
maxItems	integer	10	Maximum number of records saved in a run (1–100).
includeFinancials	boolean	true	Keep public financial series and summary figures where displayed.
includeOfficers	boolean	true	Keep public officer/relationship links where displayed.
includeRelatedCompanies	boolean	false	Keep public network links where displayed.
includeEvents	boolean	false	Keep public history/register events where displayed.
includeNews	boolean	false	Keep public marketing/news links where displayed.

Output

One dataset row represents one resolved public profile. Optional public sections are arrays and can be empty when the profile does not display that section.

Field	Description
recordType, url, name	Entity type, canonical source URL, and displayed name.
status, foundingDate, corporatePurpose	Public lifecycle and identity text when displayed.
registerNumber, nationalIds, leiCode, companyId	Registry identifiers displayed on the profile.
address, city, country	Public address and location text.
revenue, earnings, employees	Latest public summary values when available.
financials, balanceSheets	Public financial series or balance-sheet data when displayed.
officers, relatedCompanies	Public person and network links.
events, news	Public history and marketing/news entries.
sourceLinks	Displayed publication and identity/source links.
scrapedAt	ISO timestamp for the extraction.

Example row shape:

{
  "recordType": "company",
  "url": "https://www.northdata.com/Volkswagen+AG,+Wolfsburg/HRB+100484",
  "name": "Volkswagen AG",
  "registerNumber": "Wolfsburg HRB 100484",
  "city": "Wolfsburg",
  "country": "DE",
  "financials": [],
  "officers": [],
  "sourceLinks": [],
  "scrapedAt": "2026-09-03T00:00:00.000Z"
}

Use cases

• Verify a company identity, registry number, and public address before onboarding.
• Build a traceable research dataset with source URLs and publication links.
• Add public financial or officer context to a business-research workflow where the profile displays it.
• Monitor a known list of public profile URLs and retain only the relationship sections you need.

Pricing

Charge event	Unit	FREE	BRONZE	SILVER	GOLD	PLATINUM	DIAMOND
Item processed	Per 1 output record (rounded up)	$0.0035	$0.0032	$0.0029	$0.0026	$0.0026	$0.0026
Start	Per run	$0.005	$0.005	$0.005	$0.005	$0.005	$0.005

A record is charged only after it is written to the dataset. Check the actor's Pricing tab for current rates before running at scale.

API and MCP

Run through the Apify API with the same input object used in the Console. Dataset items can then be downloaded in JSON, CSV, Excel, XML, or RSS.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/north-data-company-records-scraper').call({
  searchQueries: ['Volkswagen AG'],
  maxItems: 2,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

For an MCP client, add this actor as an Apify tool and use the same supported input keys. Keep maxItems low when first validating a workflow.

Related actors

• UK Companies House Scraper — UK company registry lookups.
• Poland KRS Company Registry Scraper — Polish registry records.
• SEC EDGAR Company Filings Scraper — US public filings.
• Crunchbase Company Search Scraper — company discovery and profiles.
• LinkedIn Company Profiles Scraper — public company profile enrichment.

Tips and limits

• Use an exact public profile URL when you already know the entity; it provides the strongest target binding.
• Start with maxItems: 1 or 2, then increase only after checking the returned fields for your target.
• Financials, balance sheets, officers, events, news, and source links are source-dependent. The actor never invents missing values.
• Only public northdata.com and northdata.de URLs are accepted. Login-only and premium-only scopes are excluded.
• Search filters such as country and result-type selection are not part of this version.

FAQ

Can I scrape a company by name?

Yes. Use searchQueries with a company, person, or registry term. Use a direct public profile URL when you need to target an exact known profile.

Why is a collection empty?

North Data does not display every public section for every profile. Empty arrays mean that optional displayed section was unavailable or disabled in the input.

Does the actor provide official registry data?

The actor exports public information displayed by North Data and preserves source URLs. Validate material decisions against the relevant official registry or filing.

Can I use it in an automated workflow?

Yes. Use the Apify API, dataset exports, webhooks, or an MCP client. Keep public-data and applicable privacy obligations in mind when handling person records.

Support

For a reproducible problem, include the public source URL, the input (without secrets), and the run ID in an Apify issue. Do not send credentials or private account data.