North Data Company Records Scraper

Export public company and person profile information displayed by North Data, with source links for registry research and business-data enrichment. Supply known public profile URLs or search terms, then review resolved identity, available public financial context and selected relationship sections. This does not independently verify a company or replace official registry checks.

Quick start

Begin with the existing Volkswagen name search and a two-record cap. Clear the other source prefill if you only want this query, then inspect the resolved profile URL and displayed identity before exporting:

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

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

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

What you get

One row for a resolved public profile, with its canonical source link, displayed name and available registry identifiers, address and public financial series. Optional officers, related-company links, events and news provide source-dependent research context. Missing sections remain empty rather than being independently completed or verified.

Who is it for?

• Registry researchers checking displayed company identities against source references.
• Business-data teams enriching exact known profiles with public identifiers.
• Due-diligence analysts collecting traceable evidence for further official checks.
• Relationship researchers reviewing available officer, network and event context.

How you can use the data

• Check a known Volkswagen profile's displayed identity. Use the existing exact profile URL with a one-record cap and compare registerNumber, name, address and sourceLinks. Confirm material decisions against an official register rather than treating this export as verification.
• Resolve a company-name candidate carefully. Use Volkswagen AG with a small cap and inspect the returned canonical URL. A search resolves the first exposed profile result, not a complete match list or a guarantee of the intended legal entity.
• Review available Siemens relationships. Use the existing Siemens recipe with selected officer, related-company, event and news sections. Preserve public source links and empty collections when not exposed, without claiming a complete ownership network or private records.
• Enrich and compare your own retained profiles. Join canonical URLs and registry identifiers to your records with collection timestamps. Enable financial series only when needed and review their source context. Scheduling and change comparisons are separate work in your destination, not built-in monitoring.

Input settings

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.

Existing input recipes follow:

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
}

Supply at least one public URL or search term. URLs are processed before generated searches. Search pages resolve the first exposed profile candidate rather than returning every matching company or person. Use a known exact profile URL when identity matters. The input form prefills both a Volkswagen query and profile URL, so clear the unwanted source when requesting just one.

Output data

One dataset row represents one unique resolved public profile. Optional public sections are arrays and can be empty when the profile does not display that section. The run's Run summary and target outcomes output links to RUN-SUMMARY, which lists saved, unavailable, no-match and failed targets. An unavailable URL is not proof that an entity is private or deleted.

Field	Description
recordType, url, name	Entity type, canonical source URL, and displayed name.
status, foundingDate, corporatePurpose	Public corporate purpose when displayed. Status and founding date are currently null.
registerNumber, nationalIds, leiCode, companyId	Registry identifiers displayed on the profile. CompanyId is currently null.
address, city, country	Public address and location text.
revenue, earnings, employees	Latest public summary values when available.
financials, balanceSheets	Public financial series when displayed. BalanceSheets is currently empty.
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.

Existing illustrative row shape, not a new extraction or verified current company record:

{
  "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"
}

Status, foundingDate and companyId are currently always null, and balanceSheets is always empty. The table names these compatibility fields without promising populated values. Financial summaries require numeric values in the exposed financial series. Officer roles are inferred from displayed labels rather than independently verified registry decisions. Person profiles are recognized from their displayed person heading and matching public structured identity. When related companies are requested, displayed person memberships are included; membership links remain null when the page provides only a name. SourceLinks is limited to at most one hundred displayed publication and identity references.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once before fetching profiles when the run has enough event budget to begin. The item event charges each unique profile after it is saved. Unavailable targets, confirmed no matches and empty optional sections do not create separate result charges. A started run can still incur the start charge without producing profiles.

Begin with one or two targets. See the live Pricing tab for current rates and discounts rather than relying on copied price tables.

Tips for best results

• Prefer an exact public profile URL. A name search chooses a candidate rather than proving entity identity.
• Clear unused source prefills. URLs and searches are processed together with URLs first.
• Keep sourceLinks with important identity fields. They support your own official-source review.
• Enable only the public relationship sections you need. Missing or disabled sections can be empty.
• Inspect the run summary when a target is absent. Confirmed no matches and unavailable URLs are distinguished from failed extraction. Saved rows remain available if another target fails.

Limits and caveats

Only public northdata.com and northdata.de URLs are accepted. No North Data account is required and login-only or premium content is not bypassed. Public person records require appropriate handling, and displayed information is not an independent credential, identity or financial verification.

Searches resolve the first exposed profile result rather than every matching entity. Country and result-type filters are not supported. The saved-record cap is between one and one hundred and is not a promise of that many valid profiles. Known exact URLs provide stronger target binding than name searches.

Displayed financials, officer links, networks, events, news and publication references vary by profile and selected options. Numeric summary values depend on available numeric source series. Empty arrays can reflect unavailable or disabled sections. Status, foundingDate, companyId and balanceSheets currently have the empty values described in Output, and inferred roles or entity types are not official registry decisions.

Confirmed no matches and unavailable targets can finish successfully with an empty dataset and truthful summary reasons. Challenges, failed requests and incomplete extraction fail the run while preserving any useful rows already saved. Saving or billing failures also remain failures. Review the summary and final status before claiming complete coverage.

Provide at most 1,000 combined URL and query entries. Processing is limited to four minutes and the record and event-budget caps. Large or unexpected responses can fail safely rather than consume unbounded resources. Restarting a previous run does not resume extraction. Start a new run with the targets you still need.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~north-data-company-records-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"searchQueries":["Volkswagen AG"],"maxItems":2}'

Node.js

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);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/north-data-company-records-scraper').call(run_input={
    'searchQueries': ['Volkswagen AG'],
    'maxItems': 2,
})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with North Data Company Records Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's North Data Company Records Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/north-data-company-records-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use North Data Company Records Scraper by Fetch Cat, or give it the identifier fetch_cat/north-data-company-records-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s North Data Company Records Scraper to retrieve https://www.northdata.com/Volkswagen+AG,+Wolfsburg/HRB+100484 with search queries cleared and a one-record cap. Keep displayed registry identity and source links for my own official-register check.”
• “Collect up to 2 public North Data records for Volkswagen AG with start URLs cleared. Inspect the resolved profile link and name as a search candidate, without claiming every company match or verified legal identity.”
• “Retrieve the public North Data profile for Siemens AG with a one-record cap, financials, officers, related companies, events and news enabled. Keep available source links and empty sections without claiming a complete ownership network or private financial records.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

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. An empty optional array can mean that the section was unavailable or disabled. An empty dataset can also mean no matching profiles, unavailable targets or an exhausted event budget. Check the run summary and final status to distinguish these from extraction failures.

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.

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.
• GLEIF LEI Records Scraper — Look up public LEI records by legal name or LEI code, with names, addresses and registration status, for company-reference enrichment.
• LinkedIn Company Profiles Scraper — public company profile enrichment.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥