Handelsregister Scraper avatar

Handelsregister Scraper

Pricing

from $30.00 / 1,000 results

Go to Apify Store
Handelsregister Scraper

Handelsregister Scraper

Leistungsstarker Actor zur Identifikation von Firmen und Entscheidungsträgern aus dem deutschen Handelsregister. Zugriff auf Geschäftsführer, Vorstände und vertretungsberechtigte Personen per Echtzeit-API — ideal für Lead-Enrichment, Marktanalysen, KYC und Due-Diligence.

Pricing

from $30.00 / 1,000 results

Rating

0.0

(0)

Developer

Dominic M. Quaiser

Dominic M. Quaiser

Maintained by Community

Actor stats

5

Bookmarked

107

Total users

7

Monthly active users

5 days ago

Last modified

Features

Limited permissionsSingle-tenantServer interface

Share

A powerful Apify Actor for extracting company data from the German Commercial Register (Handelsregister).

This Actor runs in standby mode and provides real-time access to Handelsregister data via an HTTP interface with response times under one second.

Deutsche Dokumentation

Availability: Data comes live from handelsregister.de, which has frequent maintenance windows and outages, sometimes only for individual federal states. If requests fail, check the Actor status page (independent monitoring) or the official Handelsregister status.

Features

  • Real-time API: HTTP server in standby mode with sub-second response times
  • Single-Result Focus: The scraper specifically returns only the first (best-matching) result, simplifying direct data processing.
  • Flexible search options: Search by company name or register number with configurable search strategies
  • Phonetic search: Optionally include similarly sounding terms (e.g. "Meyer" also finds "Meier")
  • Automatic data storage: All results are automatically stored in the Apify dataset
  • Raw XML access: Optionally store the original XJustiz XML files in the Key-Value Store
  • Comprehensive legal form support: Complete data extraction for all German legal forms:
    • e.K. (Sole proprietor) - Owner
    • GmbH - Managing directors, Shareholders
    • AG - Board members, Chairman
    • SE (European Company) - Managing director
    • OHG - Partners
    • KG, GmbH & Co. KG - General partners, Limited partners with liability contributions
  • Simplified data structure: All decision-makers in a unified vertretungsberechtigte field for easy lead generation
  • Scalable: Automatically scales to handle concurrent requests

Usage

This Actor can be used in standby mode, meaning it behaves like a standard API.
You do not need to start the Actor manually. Simply send HTTP requests to the Actor’s endpoint and receive immediate results.
After an initial warm-up phase, the endpoint is ready for direct requests and remains active for the duration you have configured.

Endpoint

Send a POST request to your Actor’s standby URL in the following format:

https://dominic-quaiser--handelsregister-scraper.apify.actor?token=YOUR_API_TOKEN

Request Format

You need an Apify account and an API token to use this Actor.
You can find your token under Settings → API & Integrations in the Apify Console.

curl -X POST https://dominic-quaiser--handelsregister-scraper.apify.actor \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"firma_schlagwoerter": "SAP Deutschland SE & Co. KG",
"schlagwoerter_suchoptionen": "alle Schlagwörter enthalten.",
"aehnlich_lautende_schlagwoerter": false,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "DE"
}
}'

Alternative method – token as query parameter

curl -X POST https://dominic-quaiser--handelsregister-scraper.apify.actor?token=YOUR_API_TOKEN \
-H "Content-Type: application/json" \
-d '{
"registernummer": "350654",
"registerart": "HRA",
"registergericht": "Mannheim",
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "DE"
}
}'

Request Parameters

Search by company name / keywords

When searching by company name or keywords, the following parameters are available:

ParameterTypeRequiredDescriptionValid values
firma_schlagwoerterStringYesCompany name or keywords (separate multiple terms by spaces)Any text
schlagwoerter_suchoptionenStringYes (if firma_schlagwoerter is provided)How keywords should be matched"alle Schlagwörter enthalten.", "mindestens ein Schlagwort enthalten.", "den genauen Firmennamen enthalten."
aehnlich_lautende_schlagwoerterBooleanNoInclude phonetically similar termstrue, false
niederlassung_sitzStringNoLocation or city of the branch / registered officeAny location name
zusaetzliche_suchoptionenStringNoAdvanced search options"Auch geschlossene Registerblätter oder gelöschte Zweigniederlassungen finden.", "Nur nach Zweigniederlassungen neuen Rechts suchen."

Search by register number

When searching by register number, the following parameters are required:

ParameterTypeDescriptionValid values
registernummerStringUnique register number (max. 10 characters)Any number
registerartStringRegister type"alle", "HRA", "HRB", "GnR", "PR", "VR", "GsR"
registergerichtStringCity or location of the register court, or "alle"Any court location (e.g. “Munich”, “Berlin”)

Optional parameters

ParameterTypeDescriptionDefault
xml_im_key_value_store_speichernBooleanStores the original XML file (structured register content) in the Key-Value Storefalse
proxyConfigurationObjectProxy configuration for HTTP requests. Allows using Apify proxies (Residential, Datacenter) to hide the originApify Residential Proxy (Germany)

Register Types

Select the appropriate register type based on the company type you are looking for:

  • alle: Search all register types
  • HRA (Commercial Register A): Sole traders, OHG, KG
  • HRB (Commercial Register B): GmbH, AG, KGaA
  • GnR (Cooperative Register): Cooperatives
  • PR (Partnership Register): Professional partnerships
  • VR (Association Register): Associations
  • GsR (Company Register): European companies

Keyword Search Options

  • "alle Schlagwörter enthalten.": Only results containing all provided keywords
  • "mindestens ein Schlagwort enthalten.": Results containing at least one keyword
    • Important: Requires at least one of the following parameters: registerart, registergericht, or registernummer
  • "den genauen Firmennamen enthalten.": Exact company name matches only

When aehnlich_lautende_schlagwoerter is set to true, phonetically similar names are also matched:

  • "Meyer" also finds "Meier", "Mayer", "Maier"
  • "Schmidt" also finds "Schmitt", "Schmid"
  • Especially useful when spelling is uncertain

Response Format

Successful response (200 OK)

(Response example identical to the German version; field names remain unchanged for API consistency.)

Notes

  • Empty fields are omitted: Fields with null values or empty arrays are removed automatically to reduce payload size
  • stammkapital is only returned for capital companies
  • komplementaere and kommanditisten are only returned for partnerships (KG, KGaA)
  • Partners can be natural persons or legal entities
  • Legal entities include their own register entry
  • Limited partners include a hafteinlage (liability contribution)
  • Optional fields (e.g. date of birth, profession) are only included if available
  • Check the register entry against your own record: if the register document carries no register entry for the company itself, register_eintrag (register type and number) may be taken from a partner company's entry instead, e.g. the general partner GmbH of a GmbH & Co. KG. Compare register_eintrag with the court and register number you searched for before relying on it

Error Handling

The Actor returns standard HTTP status codes:

  • 200: Success – company data retrieved successfully
  • 400: Bad request – check input parameters
  • 401: Unauthorized – invalid or missing API token
  • 402: Payment required – dataset limit reached, upgrade plan
  • 404: Not found – no results for search criteria
  • 500: Internal server error – unexpected error (contact support if persistent)

If you get repeated 500 errors, check whether the register is down:

Raw XML Access

If you need the original XML file (structured register content), you can store it in the Apify Key-Value Store.

Enable via parameter

Set xml_im_key_value_store_speichern to true.

Accessing stored XML files

Files are stored with a unique key:

xml_{Court}_{RegisterType}_{RegisterNumber}.xml

Apify allows only ASCII letters, digits and a few punctuation marks in keys, so umlauts and ß are spelled out, spaces and slashes become underscores, and other characters are dropped: Amtsgericht München, HRB 123456 is stored as xml_Muenchen_HRB_123456.xml.

They can be accessed via the Apify Console or API.
The XML is stored in XJustiz format, the German standard for electronic legal communication.

Code Examples

Python

import requests
url = "https://dominic-quaiser--handelsregister-scraper.apify.actor?token=YOUR_API_TOKEN"
payload = {
"firma_schlagwoerter": "SAP Deutschland SE & Co. KG",
"schlagwoerter_suchoptionen": "alle Schlagwörter enthalten.",
"registerart": "alle",
"xml_im_key_value_store_speichern": True
}
response = requests.post(url, json=payload)
result = response.json()
print(f"Company: {result['bezeichnung']}")
print(f"Legal form: {result['rechtsform']['kurz']}")
print(f"Registered office: {result['sitz']}")

JavaScript / Node.js

const response = await fetch(
"https://dominic-quaiser--handelsregister-scraper.apify.actor?token=YOUR_API_TOKEN",
{
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
firma_schlagwoerter: "SAP Deutschland SE & Co. KG",
schlagwoerter_suchoptionen: "alle Schlagwörter enthalten.",
registerart: "alle",
}),
},
);
const data = await response.json();
console.log(`Company: ${data.bezeichnung}`);
console.log(`Legal form: ${data.rechtsform.kurz}`);

Use Cases

  • Lead generation
  • Due diligence
  • Compliance & KYC
  • Market research
  • Database enrichment (CRM / ERP)
  • Change monitoring
  • Workflow automation
  • Contract and signatory validation

Integrations

  • Scheduler
  • Webhooks
  • Apify API
  • Composer
  • Zapier / Make

Technical Details

Standby Mode

  • Always-on HTTP endpoint
  • Automatic scaling under load
  • Ideal for APIs and integrations

Data Source

Data is retrieved directly from the official German Commercial Register portal (handelsregister.de).

Automatic Error Correction

  • Automatic correction of court name typos
  • Fuzzy matching for unclear inputs
  • Helpful suggestions for invalid court names

Maintenance