Skip to main content
The German Transparenzregister is the official register for beneficial ownership information in Germany. OpenRegister gives you simple API access to request extracts and receive structured UBO data plus official source documents. OpenRegister is officially certified by Bundesanzeiger Verlag GmbH, the publisher of the Transparenzregister API. Access to live data still requires berechtigtes Interesse (legitimate interest) under the Geldwäschegesetz (GwG).

​
What You Get

  • Structured UBO records — Get full name, date of birth, city, country, and percentage hints where available in the register text.
  • Official source documents — Download original Transparenzregister artifacts (PDF, JSON, optional SVG) through documents[].
  • Sandbox mode — Test the full integration flow without live credentials and without credit usage.
  • Credential isolation — Store multiple credential sets under different name values (default default) for separate clients or environments.

​
Getting Started

Live Transparenzregister extracts run through your own account at transparenzregister.de. Three prerequisites must be met before the first extract request succeeds:
  1. Legitimate interest — You need a berechtigtes Interesse in inspecting the register under the Geldwäschegesetz (GwG). The Transparenzregister verifies this for your account.
  2. Einsichtnahmeschnittstelle enabled — The inspection API must be activated on your Transparenzregister account. Log in to transparenzregister.de and go to „Meine Aktionen“ → „Einsichtnahmeschnittstelle freischalten“. The activation is complete once the status shown there is „Abgeschlossen“.
  3. Credentials stored with OpenRegister — Store your personal Transparenzregister username and password via the Store Credentials endpoint. You can store multiple credential sets under different name values (e.g. one per client account).
After that, production extract requests use your stored credentials automatically (unless you choose another credential via X-Credential-Name).
Storing credentials validates them against the Transparenzregister inspection API. If the Einsichtnahmeschnittstelle is not yet enabled on your account, that login is rejected and the endpoint returns 401 — wait until the status shows „Abgeschlossen“ before storing credentials.
You can test the integration without live credentials by sending X-Credential-Name: sandbox on Order extract. This uses the Transparenzregister test environment and costs 0 credits.

​
Use Cases

AML & KYC — Retrieve structured beneficial ownership records as part of customer onboarding, periodic review, and risk-based due diligence processes. Compliance Operations — Centralize Transparenzregister retrieval across teams and clients in a single API flow. Track every extract by extract_id and audit outcomes programmatically. Due Diligence — Combine Transparenzregister UBO data with Handelsregister company details and Bundesanzeiger financials for complete entity profiles.

​
API Endpoints

Store Credentials

Save Transparenzregister credentials with an optional name

Order extract

Create a new Transparenzregister extract and get an extract id

Get extract

Poll by extract id and retrieve structured UBO data and source documents when completed

​
Update Frequency

  • Source: Transparenzregister official API
  • Updates: On-demand per extract submission
  • Processing: Async workflow; poll Get extract until status is completed or failed