Handelsregister Germany Scraper [Just 💰$0.9] avatar

Handelsregister Germany Scraper [Just 💰$0.9]

Pricing

from $0.90 / 1,000 results

Go to Apify Store
Handelsregister Germany Scraper [Just 💰$0.9]

Handelsregister Germany Scraper [Just 💰$0.9]

Search the German commercial register (handelsregister.de) by company name, city or register number. Each record has legal form, registered address, share capital and directors. Ready to import into a CRM or a spreadsheet for KYC checks.

Pricing

from $0.90 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 hours ago

Last modified

Share

What does Handelsregister Germany Scraper do?

Handelsregister Germany Scraper extracts structured company data from handelsregister.de — including location data. It supports keyword search, location filters, and controllable result limits, so you can run the same query consistently over time. The actor also offers detail enrichment (company metadata) where the source provides them.

How to use this actor

  • 👉 Register for a free Apify account — no credit card required.
  • 🎉 Just click Sign up free on Apify → and complete a quick signup.
  • 💰 A free Apify account includes $5 in monthly credits — enough to test this actor.
  • ⏳ Scrape during the free trial, with no commitment or upfront payment required.

Key features

  • 🔍 Keyword search: search handelsregister.de by keyword with the query input, in the place you name in location.
  • 🔗 Paste-mode: paste handelsregister.de URLs into startUrls to scrape exactly the pages you picked in the browser.
  • 📋 Detail enrichment: toggle two-stage scraping: first collect listings, then enrich each with full description + detail-page-only fields. Off by default to keep runs fast; flip on when you need the deep payload.
  • 🏛️ Official register identity: every record carries company_name, legal_form, status and the full register reference — register_id, registry_court, registry_court_code, register_type, hr_number and state — ready to match against your CRM.
  • 📍 Split registered address: the registered office comes as registered_address and already split into address_street, address_house_number, address_postal_code and address_city, plus the registered_seat.
  • 👤 Directors and authorised signatories: officers lists every registered person or organisation with role and city; managing_directors and prokura_holders give the signatories with first and last name, and representation_rule states who may sign for the company.
  • 📑 Capital, purpose and key dates: business_purpose, share_capital_text with the parsed share_capital_eur, incorporation_date, articles_date and last_change_date — the facts a KYC or due-diligence check asks for.
  • 🗂️ Register entries and former names: register_entries with entry_count shows the filed changes, previous_names the company's former names, and available_documents which register documents exist.
  • ♻️ Incremental mode: recurring runs emit only directory entries that are new or updated — keep your supplier-outreach lists fresh without re-fetching the full directory. Saves 80–95% on weekly syncs.
  • 🔔 Notifications: Telegram, Slack, Discord, WhatsApp Cloud API, and generic webhook out of the box. Pair with incremental for daily new-listing alerts without pipeline glue.
  • 🔌 MCP connectors: push your leads into Notion via Apify's MCP connectors — a tidy run-summary page, no export step, no glue code. Opt-in, deterministic field-mapping (no AI). More destinations as Apify's connector catalog grows.

What data can you extract from handelsregister.de?

Each result includes Core company fields (query, found, scrapedAt, registry_court, registry_court_code, register_type, hr_number, and register_id, and more), detail fields when enrichment is enabled (detailFetched), and company metadata (company_name). In standard mode, all fields are always present — unavailable data points are returned as null, never omitted. In compact mode, only core fields are returned.

Enable detail enrichment in the input to get richer fields such as company metadata where the source provides them.

Input

The main inputs are a search keyword, an optional location filter, and a result limit. Additional filters and options are available in the input schema.

Key parameters:

  • query — Company name or keyword to search the register for (e.g. "Bäckerei", "Siemens AG"). Use a JSON array for several searches, e.g. ["Bäckerei","Kaffeerösterei"].
  • location — Optional. Restrict results to companies with this registered seat (city), e.g. "Hannover". Use a JSON array for several cities.
  • maxResults — Maximum total records (0 = everything the register returns). The register itself shows at most 100 hits per search — narrow the keyword or add a seat for bigger universes. (default: 100)
  • includeDetails — Fetch the structured register content per company (legal form, address, business purpose, share capital, officers, register entries). Turn off for name/court/seat only. (default: true)
  • includeDeleted — Also return companies whose register entry has been deleted (gelöscht) — useful for due diligence and history research. (default: false)
  • includeRawXml — Attach the raw structured register document (XJustiz XML) to each record as raw_xml — large, increases dataset size. Needs Include Full Register Details. (default: false)
  • compact — Core fields only (for AI-agent/MCP workflows). (default: false)
  • excludeEmptyFields — Drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards. (default: false)
  • incrementalMode — Compare against previous run state. stateKey is optional — defaults to a value derived from search inputs (queries, seats) so different filter sets never share state. (default: false)
  • stateKey — Optional. Stable identifier for the tracked search universe. Leave empty to auto-generate from search inputs.
  • skipReposts — When incremental, skip records whose content matches an expired record from a prior run (cross-run duplicate detection). (default: false)
  • emitUnchanged — When incremental mode is on, also emit records whose content has not changed since the last run. (default: false)
  • ...and 16 more parameters

Input examples

Basic search — Keyword-driven search with a result cap.

→ Full payload per result — all standard fields populated where the source provides them.

{
"query": "Bäckerei",
"maxResults": 50
}

Incremental tracking — Only emit records that changed since the previous run with this stateKey.

→ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set emitUnchanged: true to include unchanged records as well.

{
"query": "Bäckerei",
"maxResults": 200,
"incrementalMode": true,
"stateKey": "bäckerei-tracker"
}

Compact output for AI agents — Return only core fields for AI-agent and MCP workflows.

→ Small payload with the most important fields — ideal for piping into LLMs without token overhead.

{
"query": "Bäckerei",
"maxResults": 50,
"compact": true
}

Output

Each run produces a dataset of structured company records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example company record

{
"query": "Bäckerei",
"found": true,
"sourceUrl": "https://www.handelsregister.de/rp_web/sucheErgebnisse/welcome.xhtml",
"scrapedAt": "2026-10-14T13:37:04.736Z",
"company_name": "\"... em Tetz Backes\" Bäckerei und Konditorei GmbH",
"registry_court": "Amtsgericht Mönchengladbach",
"registry_court_code": "R1504",
"register_type": "HRB",
"hr_number": "4934",
"register_id": "Amtsgericht Mönchengladbach HRB 4934",
"state": "Nordrhein-Westfalen",
"registered_seat": "Mönchengladbach",
"status": "aktuell",
"legal_form": "Gesellschaft mit beschränkter Haftung (GmbH)",
"registered_address": "Konstantinstraße 117, 41238 Mönchengladbach",
"address_street": "Konstantinstraße",
"address_house_number": "117",
"address_postal_code": "41238",
"address_city": "Mönchengladbach",
"business_purpose": "der Betrieb einer Bäckerei und Konditorei sowie die Herstellung und der Verkauf von Backwaren und Lebensmitteln. Die Gesellschaft kann im In- und Ausland Zweigniederlassungen errichten, sich an andere...",
"share_capital_text": "50.000,00 DEM",
"representation_rule": "Die Gesellschaft hat einen oder mehrere Geschäftsführer. Ist nur ein Geschäftsführer bestellt, vertritt er die Gesellschaft allein. Sind mehrere Geschäftsführer bestellt, wird die Gesellschaft durch z...",
"managing_directors": [
{
"name": "Maximilian Tetz jun.",
"firstName": "Maximilian",
"lastName": "Tetz jun.",
"city": "Mönchengladbach"
}
],
"officers": [
{
"role": "Geschäftsführer(in)",
"roleCode": "086",
"isOrganisation": false,
"name": "Maximilian Tetz jun.",
"firstName": "Maximilian",
"lastName": "Tetz jun.",
"city": "Mönchengladbach"
}
],
"incorporation_date": "1994-10-24",
"articles_date": "1994-06-29",
"last_change_date": "2012-11-05",
"entry_count": 4,
"register_entries": [
{
"column": "6",
"position": "1",
"type": "Satzung",
"text": "Gesellschaftsvertrag vom 29.06.1994"
},
{
"column": "7",
"position": "2",
"type": "Freitext",
"text": "Tag der ersten Eintragung in Mönchengladbach: 24.10.1994. Dieses Blatt ist zur Fortführung auf EDV umgeschrieben worden und dabei an die Stelle des bisherigen Registerblattes getreten. Freigegeben am..."
},
{
"column": "7",
"position": "2",
"type": "Freitext",
"text": "Gesellschaftsvertrag Blatt 7 ff. Sonderband"
},
{
"column": "6",
"position": "2",
"type": "Insolvenz",
"text": "Durch Beschluss des Amtsgericht Mönchengladbach (32 IN 102/07) vom 01.09.2007 wurde das Insolvenzverfahren eröffnet. Die Gesellschaft ist damit kraft Gesetzes aufgelöst. Von Amts wegen eingetragen."
}
],
"available_documents": [
"AD",
"CD",
"HD",
"DK",
"UT",
"... 2 more items"
],
"search_result_url": "https://www.handelsregister.de/rp_web/sucheErgebnisse/welcome.xhtml",
"portalUrl": "https://www.handelsregister.de/rp_web/erweitertesuche/welcome.xhtml",
"scraped_at": "2026-10-14T13:37:04.736Z",
"listingId": "a9b313a9e4ad387c795105be405a21530d24a5e8f0d4483516e62e7d850dd111",
"searchQuery": "Bäckerei",
"contentQuality": "full",
"detailFetched": true,
"source": "handelsregister.de",
"contentHash": "722a4aadaa65ab27dc23793076786f4a27a31e283cebba48930be81cff48c73b"
}

Incremental fields

When incremental mode is on, each record also carries:

  • changeType — one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED. Default output covers NEW / UPDATED / REAPPEARED; set emitUnchanged: true or emitExpired: true to opt into the others.
  • isRepost, repostOfId, repostDetectedAt — populated when a new listing matches the tracked content of a previously expired one. Set skipReposts: true to drop detected reposts from the output.

How to scrape handelsregister.de

  1. Go to Handelsregister Germany Scraper in Apify Console.
  2. Enter a search keyword and optional location filter.
  3. Set maxResults to control how many results you need.
  4. Enable includeDetails if you need the extra detail-page fields.
  5. Click Start and wait for the run to finish.
  6. Export the dataset as JSON, CSV, or Excel.

Use cases

  • Extract company data from handelsregister.de for market research and competitive analysis.
  • Monitor new and changed records on scheduled runs without processing the full dataset every time.
  • Use structured location data for regional analysis, mapping, and geo-targeting.
  • Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
  • Export clean, structured data to dashboards, spreadsheets, or data warehouses.

How much does it cost to scrape handelsregister.de?

Handelsregister Germany Scraper uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

  • Run start: $0.01 per run
  • Per result: $0.0009 per company record

Example costs:

  • 10 results: $0.019
  • 25 results: $0.033
  • 100 results: $0.1

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of records that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 100 records per run, daily polling (30 runs/month). Costs scale linearly with the number of records.

Churn rateFull re-scrape run costIncremental run costSavings vs full re-scrapeMonthly cost after baseline
5% — stable niche query$0.10$0.01$0.09 (86%)$0.43
15% — moderate broad query$0.10$0.02$0.08 (76%)$0.70
30% — high-volume aggregator$0.10$0.04$0.06 (63%)$1.11

Full re-scrape monthly cost at the same cadence: $3.00. First month with incremental costs $0.52 / $0.78 / $1.17 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage is included in the per-result fee shown above.

FAQ

How many results can I get from handelsregister.de?

The number of results depends on the search query and available records on handelsregister.de. Use the maxResults parameter to control how many results are returned per run.

Does Handelsregister Germany Scraper support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed records on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate Handelsregister Germany Scraper with other apps?

Yes. Handelsregister Germany Scraper works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use Handelsregister Germany Scraper with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use Handelsregister Germany Scraper through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode, a single descriptionFormat, and excludeEmptyFields to keep payloads manageable for LLM context windows.

This actor extracts publicly available data from handelsregister.de. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

Getting started with Apify

New to Apify? Create a free account with $5 credit — no credit card required.

  1. Sign up — $5 platform credit included
  2. Open this actor and configure your input
  3. Click Start — export results as JSON, CSV, or Excel

Need more later? See Apify pricing.

Disclaimer

This actor accesses only publicly available data on handelsregister.de. You are responsible for how you use the extracted data — in particular any personal information such as names, phone numbers, or email addresses — and for complying with Handelsregister Germany's terms of use, applicable data-protection law (including the GDPR where it applies), and the anti-spam rules of your jurisdiction.

This actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Handelsregister Germany or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

Search keywords

handelsregister scraper, handelsregister api, apify handelsregister, handelsregister data extraction, handelsregister germany scraper, handelsregister germany api, apify handelsregister germany, handelsregister germany data extraction, handelsregister.de scraper, handelsregister.de data, handelsregister.de api.