registercheckby openlaw group

Introduction

Company and person data from the German commercial register, as an API.

The Registercheck API gives you programmatic access to the German commercial register — every company filed at a German Amtsgericht, the people who run and own them, the documents they have filed, and the changes as they happen.

One HTTP call, JSON back, no PDF parsing.

Your first request
curl "https://api.registercheck.de/v1/search/companies?name=Siemens" \
  -H "Authorization: Bearer $REGISTERCHECK_API_KEY"

What you can build

How the API is shaped

The API is organised around the things the register itself contains, not around our storage, and it uses one word for each of them: in the paths, the object field, the ids and these pages. The data model explains them.

The API reference is grouped by the first segment of the path, so an endpoint is where its path says: /companies/{company_id}/roles is under Companies, /events under Events.

GroupWhat lives there
SearchTurning a name, a register number or a filter into companies and persons
FormationsCompanies entered in the register for the first time
CompaniesThe register entry, and everything listed under it: roles, shareholders, holdings, documents, financial statements, its events
PersonsNatural persons, the roles they hold and their shareholdings
EventsEvery change the register courts enter, across all companies
Monitors, Destinations, DeliveriesWatching companies, where the events go, and what was sent
ListsYour own lists of companies and persons
Reference dataThe codes other answers use, with their labels

What is planned and not served yet is on the roadmap.

Before you start

Read the coverage page first

The register is not uniformly complete, and neither are we. What a given endpoint returns for a given company depends on what has actually been filed and extracted. Data coverage states what is populated how often, measured rather than promised.

On this page