German Handelsregister Company Lookup (handelsregister.de)

Search the official German company register (handelsregister.de) by keyword or HRB / HRA / GnR / PR / VR / GsR number. Get clean JSON: company name, register court, seat, federal state, status, available document codes, and name history.

Store: metsuryu/handelsregister-company-lookup

What it does

Walks the public Registerportal advanced-search flow (stateful JSF session), submits your keyword or register filters, and parses the result table. One dataset item per company.

Why use this Actor

• Official portal — primary source German federal states maintain
• Cheap PPE — pay per company row; undercuts richer SI competitors when you only need search-table facts
• No CAPTCHA wall in normal operation (DC proxies OK)
• Ready-made tasks — demo lookups you can clone and edit

Common use cases (ready-made tasks)

Use case	Task	What you get
Demo: Gasag group companies	gasag-company-lookup	Sample Berlin energy-group hits from keyword Gasag
Siemens keyword search (max 50)	siemens-hrb-keyword-search	Broader keyword scan capped for cost control

Typical buyers: KYC / AML enrichment, lead gen on German GmbH/AG entities, M&A screening, and CRM backfill of register court + HRB number.

Honest limits (read before buying)

• Portal cap: each search returns at most 100 hits — split broad names into narrower queries (city, register type, state).
• Rate limits: the justice portal paces / IP-blocks aggressive clients (order of ~60 retrievals/hour class). This Actor adds request delays; use datacenter proxies on Apify.
• No CAPTCHA wall in normal operation (unlike Cloudflare-gated Italian registries). If a CAPTCHA appears, the run fails loudly.
• v0.1 fields: search-table facts + history. Structured SI/XJustiz officers & street address are not fetched yet (officers / address / legalForm stay null). Competitor Actors that parse SI charge more for a reason. (v0.2 SI enrichment skipped for now — see sprint notes: feasible without CAPTCHA but not low-risk JSF/doc-tree work.)

Input highlights

Field	Purpose
searchQueries	Keywords; one portal search each
keywordMatch	all / any / exact
registerType + registerNumber + registerCourt	Precise lookup
city / postalCode / states	Geographic narrowing
includeDeleted	Include gelöscht entries
maxItems	Hard cap (PPE control)
proxy	Apify Proxy (DC OK)

Example input

{
  "searchQueries": ["Gasag"],
  "keywordMatch": "all",
  "maxItems": 10,
  "proxy": { "useApifyProxy": true }
}

Output fields

companyName, registerId, registerCourt, registerType, registerNumber, state, seat, status, statusRaw, history[], availableDocuments[], searchQuery, scrapedAt.

Pricing

Pay-per-event: near-zero apify-actor-start + primary charge per company dataset item. See the pricing panel.

Legal / GDPR

Public register data. Officer PII appears only if/when SI parsing is enabled in a later version — users remain responsible for lawful basis under GDPR and the portal terms (no bulk dump / resale of the full register).