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.
curl https://api.registercheck.de/v1/search/companies?name=Siemens \
-H "Authorization: Bearer $REGISTERCHECK_API_KEY"What you can build
Find a company
Resolve a half-remembered name or a register number to a stable company id.
Build a company report
Assemble register facts, management, ownership and financials into one view.
Track changes
Subscribe to a company and receive an event when its register entry moves.
Run long work asynchronously
Trigger a document fetch or a shareholder rebuild, then poll for the result.
How the API is shaped
The API is organised around the things the register itself contains, not around our storage. Six domains, and every endpoint belongs to exactly one of them:
| Domain | What lives there |
|---|---|
| Search | Turning a name, a register number or a filter into candidate entities |
| Companies | The register entry: name, seat, purpose, capital, status, history |
| People | Natural persons, and the roles they hold at companies |
| Ownership | Shareholders, shareholdings and the investments a company holds |
| Financials | Filed annual accounts and the figures extracted from them |
| Monitoring | Subscriptions that raise an event when a company changes |
Lists and Jobs sit alongside these as workspace and plumbing rather than register data.
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.