North Data Company Search Scraper avatar

North Data Company Search Scraper

Pricing

Pay per event

Go to Apify Store
North Data Company Search Scraper

North Data Company Search Scraper

Extract public North Data company search results and profile details for B2B enrichment, compliance checks, and due diligence.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Extract public North Data company search results and profile details for B2B enrichment, compliance checks, and due-diligence workflows.

The actor searches northdata.com, follows public company profile pages, and exports structured company records with registry identifiers, address data, visible financial snippets, and source links.

What does North Data Company Search Scraper do?

North Data Company Search Scraper turns public North Data pages into a clean dataset. You can enter company names, register numbers, or direct North Data URLs and receive normalized company records ready for spreadsheets, CRMs, enrichment pipelines, or compliance review.

It is designed for public information only. It does not log in, download premium dossiers, bypass paywalls, or extract export-only data.

Who is it for?

  • 🧲 B2B sales teams enriching German and European account lists.
  • 🧾 Compliance analysts checking register references before onboarding vendors.
  • 🔎 Due-diligence teams collecting profile links, addresses, identifiers, and financial snippets.
  • 🏢 RevOps teams validating company names and locations before CRM import.
  • 📊 Market researchers building lists of visible North Data company records by keyword.

Why use this actor?

North Data pages are useful for company verification, but manual lookup is slow. This actor automates repetitive public searches, keeps a source URL for every row, and produces consistent JSON/CSV/Excel exports from Apify datasets.

What data can you extract?

FieldDescription
querySearch phrase that produced the company
nameCompany name from search/profile page
profileUrlNorth Data public profile URL
registerInfoVisible register/court text
registerCourtParsed court or registry source when available
registerNumberParsed register number when available
city, countryLocation inferred from North Data title
addressPublic address on profile pages
identifiersVisible identifiers such as KBO, LEI, EUID, CVR, etc.
previousNamesAlso/previously names shown publicly
corporatePurposeVisible public purpose/activity text
financialMetricsLatest visible financial chart snippets
latitude, longitudeCoordinates from search result metadata when present
fetchedAtISO timestamp of extraction

How much does it cost to scrape North Data company search results?

The actor uses pay-per-event pricing: a small $0.005 run start fee plus a per-company fee. You only pay the item fee for records produced, and the Apify run page shows charged events after each cloud run.

Per-company pricing is tiered by your Apify plan. The validated prices are:

Apify planPrice per company record
FREE$0.000037102
BRONZE$0.000032262
SILVER$0.000025165
GOLD$0.000019357
PLATINUM$0.000012905
DIAMOND$0.000010000

Example costs before Apify platform fees: a FREE user extracting 100 companies pays about $0.0087 ($0.005 start + 100 × $0.000037102), while a BRONZE user extracting 1,000 companies pays about $0.0373 ($0.005 start + 1,000 × $0.000032262). Larger batches become cheaper per record on higher tiers.

Input options

queries

Enter one or more company names, register numbers, cities, or prospecting keywords. Examples:

["Siemens", "Bosch", "München GmbH"]

startUrls

Use direct North Data profile URLs or search URLs when you already have source links.

maxItems

Controls the maximum number of company records saved across all inputs. Keep this small for initial tests and increase for production batches.

includeDetails

When enabled, the actor opens each profile page and enriches results with public profile fields. Disable it for faster lightweight search-result exports.

requestDelayMillis

Adds a polite delay between requests. Increase it if the target responds slowly or if you want a gentler crawl pattern.

Example input

{
"queries": ["Siemens", "Bosch", "SAP"],
"maxItems": 50,
"includeDetails": true,
"requestDelayMillis": 250
}

Example output

{
"query": "Siemens",
"name": "Siemens AG",
"profileUrl": "https://www.northdata.com/Siemens%20AG,%20M%C3%BCnchen/HRB%206684",
"registerInfo": "District Court of Munich HRB 6684",
"registerCourt": "District Court of Munich",
"registerNumber": "HRB 6684",
"city": "Munich",
"country": "Germany",
"address": "Werner-von-Siemens-Str. 1, 80333 München, Germany",
"identifiers": ["DED2601V.HRB6684"],
"financialMetrics": [{ "title": "Revenue", "latestYear": "2025", "latestValue": "€78.9B" }],
"fetchedAt": "2026-07-09T00:00:00.000Z"
}

How to scrape North Data company profiles

  1. Open the actor on Apify.
  2. Add company names to queries or paste direct North Data URLs into startUrls.
  3. Set maxItems to the number of companies you need.
  4. Keep includeDetails enabled for enriched profiles.
  5. Run the actor.
  6. Export results from the dataset as JSON, CSV, Excel, XML, or via API.

Search workflow ideas

  • Search for a target company name before vendor onboarding.
  • Search broad German legal-form terms such as GmbH with a low item limit to sample public records.
  • Feed North Data URLs from a CRM enrichment queue into startUrls.
  • Run multiple brand names in one batch and deduplicate by profileUrl.

Due-diligence workflow

Use this scraper as the first step in a lightweight due-diligence checklist:

  1. Verify the company name and register number.
  2. Save the North Data profile URL as evidence.
  3. Compare the address with vendor-provided onboarding forms.
  4. Review visible identifiers and financial snippets.
  5. Hand the source URL to a human analyst for deeper review if needed.

CRM enrichment workflow

Export CSV or connect the dataset API to your CRM enrichment process. Map name, address, city, country, registerNumber, lei, and profileUrl to custom account fields.

Tips for best results

  • Use specific company names when possible.
  • Use register numbers for exact-match verification.
  • Keep maxItems low during tests.
  • Enable details only when you need address, identifiers, purpose, or financial snippets.
  • Use profileUrl as your durable deduplication key.

Integrations

  • Google Sheets: export dataset rows into a spreadsheet for analysts.
  • HubSpot or Salesforce: import profileUrl, register info, and address into account records.
  • Data warehouses: send JSON results to BigQuery, Snowflake, or S3 through Apify integrations.
  • Compliance queues: trigger follow-up checks when registerNumber or address is missing.

API usage with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/northdata-company-search-scraper').call({
queries: ['Siemens', 'Bosch'],
maxItems: 25,
includeDetails: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/northdata-company-search-scraper').call(run_input={
'queries': ['Siemens', 'Bosch'],
'maxItems': 25,
'includeDetails': True,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~northdata-company-search-scraper/runs?token=$APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"queries":["Siemens"],"maxItems":10,"includeDetails":true}'

MCP usage

Use the Apify MCP server with Claude Desktop, Claude Code, or another MCP client:

https://mcp.apify.com/?tools=automation-lab/northdata-company-search-scraper

Claude Code CLI setup:

$claude mcp add apify-northdata "https://mcp.apify.com/?tools=automation-lab/northdata-company-search-scraper"

Claude Desktop JSON config:

{
"mcpServers": {
"apify-northdata": {
"url": "https://mcp.apify.com/?tools=automation-lab/northdata-company-search-scraper"
}
}
}

Example prompts:

  • "Run the North Data scraper for Siemens and summarize register details."
  • "Find public North Data profile URLs for these companies and return a CSV."
  • "Check whether these vendor names have visible register identifiers."

Data quality notes

North Data aggregates many registries and countries. Field availability varies by company and jurisdiction. Some records show rich financial data, while others only include a name and profile link. Optional fields may be absent when North Data does not show them publicly.

Legality

This actor extracts public web pages and stores source URLs for review. Use it responsibly, respect North Data terms, and do not use it to bypass premium features, privacy controls, or access restrictions. For compliance decisions, treat the dataset as a starting point and review official registry records where required.

Use the actor only for lawful enrichment, research, and due-diligence workflows. Do not scrape personal data unnecessarily, and verify material compliance decisions against official registry records.

Limitations

  • It does not access paid dossiers or export-only data.
  • Search pages typically expose a limited number of top results per query.
  • Public profile field availability differs by country and company.
  • Target page layout changes can require extractor updates.

FAQ

Can this scraper access North Data premium dossiers?

No. It only extracts public HTML that is visible without login. Premium dossiers, paid exports, and account-only watchlists are out of scope.

Can I use direct North Data URLs?

Yes. Paste profile URLs into startUrls and keep includeDetails enabled to extract the public profile page.

Troubleshooting

Why did I get fewer rows than maxItems?

North Data may show fewer public results for a query, or duplicate profile URLs may be skipped. Add more specific queries or more direct profile URLs.

Why are some fields empty?

The public North Data profile may not expose that field for the selected company. Disable includeDetails only if you intentionally want lightweight search results.

Why is a profile not exact?

Search terms can match related companies, former names, or similarly named entities. Use register numbers or direct URLs for exact verification.

Other automation-lab actors that can complement this workflow:

Changelog

Initial version extracts North Data public search results and profile details using HTTP + Cheerio.

Support

If a page structure changes or a public field is missing, open an Apify issue with the input you used and a sample North Data URL.