/handelsregister/companies

POST /api/handelsregister/companies

Price: 20 credits

Get German company details from the commercial register by court, register type and number

How to use it

Get full registry details for a German company by its commercial-register identity, given as 'court/register_type/number' (e.g. 'München/HRB/6684'). The court accepts either the city name or the official court code; register_type is one of HRA, HRB, GnR, PR, VR, GsR.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company identity as 'court/register_type/number' (examples: "München/HRB/6684", "D2601/HRB/6684", "Berlin (Charlottenburg)/HRB/170416"; minLength: 1)

Response

• @type string (default: "HandelsregisterCompany")
• name string required
• court string required
• register_type string required
• register_number string required
• legal_form string nullable
• registered_office string nullable
• address object nullable
  • @type string (default: "HandelsregisterAddress")
  • street string nullable
  • house_number string nullable
  • postal_code string nullable
  • city string nullable
  • country string nullable
• capital object nullable
  • @type string (default: "HandelsregisterCapital")
  • value number nullable
  • currency string nullable
• purpose string nullable
• representation string nullable
• status string nullable
• last_entry_date string nullable
• entry_count integer nullable
• last_change_date string nullable
• first_statute_date string nullable
• officers array
  • @type string (default: "HandelsregisterOfficer")
  • name string nullable
  • role string nullable
  • organization_name string nullable
  • birth_date string nullable
  • city string nullable
  • representation string nullable
• former_names array
• register_entries array

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No company found for the given court, register type and number Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.