Open Company Data in Germany: Official Sources, APIs and Reuse Rights

Germany is one of the most commercially important company-data markets in Europe, but it is also one of the easiest markets to describe badly. The country has authoritative official register and disclosure portals, strong public-sector open-data infrastructure, procurement notices, tax identifier services, insolvency publications, IP databases, financial-regulator databases and LEI records. That does not mean there is one clean, unrestricted, free official bulk file containing every German company and every reusable field.

The safe editorial angle is controlled official access plus enrichment. Unternehmensregister and the Handelsregister portal are the primary legal-register and disclosure routes. Bundesanzeiger gives legal-publication context. GovData and the German Data Licence explain open-data discovery and reuse where a dataset actually declares compatible terms. Destatis supports statistical benchmarking. service.bund.de, BZSt, Insolvenzbekanntmachungen, DPMA, BaFin and GLEIF add useful operational layers, but each of those layers covers a specific purpose rather than the full German business population.

This Wave 30 refresh rewrites the live Germany page as a deep reference article. It removes the unsafe legacy implication that official visibility equals unrestricted bulk reuse, replaces a previously unstable procurement root with a stable official tender-search route, and documents the source-risk items that should stay out of the public claim set until manual legal/privacy review is complete.

Key Takeaways

• Best registry backbone: Unternehmensregister plus the Handelsregister portal.
• Best disclosure layer: Bundesanzeiger for legal and company publications.
• Best open-data boundary: GovData and the German Data Licence, but only for datasets that declare compatible terms.
• Best enrichment layers: Destatis, service.bund.de procurement notices, BZSt VAT-ID context, Insolvenzbekanntmachungen, DPMA, BaFin and GLEIF.
• Main caution: Germany should not be marketed as a complete free official bulk-register country unless a specific official product proves that claim.
• Contact-data boundary: public company data is not consent for cold email, phone scraping or sales-prospecting reuse.

Editorial Methodology

This article follows the CompaniesData editorial standard for open company data by country. It starts with official registry and disclosure sources, then adds official open data, statistics, procurement, tax/identifier, insolvency, intellectual-property, regulator and LEI sources. Private aggregators and contact-data sellers are not used as evidence for official source rights.

Every final linked source was checked from this environment on 2026-05-29. Sources returning hard 404 or 410 are excluded. Sources with cookie-control behaviour, unstable deep links, beneficial-ownership sensitivity or extract/document redistribution questions are documented as held-source notes. Source logos in the matrix and Resource Pack are decorative favicon cues only; the evidence remains the official URL, owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

Germany company data is best understood as a layered official-source ecosystem. The register/disclosure backbone is strong for legal verification, but the access model is portal-based and document-aware. Open-data resources exist, but they are dataset-specific. Procurement, tax, insolvency, IP, regulator and LEI records are high-value enrichment signals, not replacements for the register.

Register access boundary: Unternehmensregister and Handelsregister are authoritative for inspection and verification. That should not be stretched into a claim that all register extracts, XML files, document images, officer records, historical filings or automated downloads are reusable without conditions.

Open-data boundary: GovData and the German Data Licence are useful only when the particular dataset declares that licence or another compatible term. A German open-data licence page does not override Handelsregister, Unternehmensregister, Bundesanzeiger, court-publication, tax-service or personal-data restrictions.

Privacy and lawful-use boundary: registry records can include natural-person names, representatives, addresses and event histories. Insolvency publications and beneficial-ownership-adjacent sources need stricter proportionality, retention and lawful-use review than ordinary company identifiers.

Update risk: register records, disclosure publications, open datasets, statistics, procurement notices, VAT-ID confirmation routes, insolvency publications, IP databases, BaFin registers and LEI records update on different schedules. A professional pipeline should store update dates per source and per field instead of using one generic Germany timestamp.

Reuse Checklist

• Separate source classes: keep registry, disclosure, open-data, statistics, procurement, tax, insolvency, IP, regulator and LEI layers distinct.
• Avoid open-bulk overclaiming: do not claim complete free official bulk Handelsregister or Unternehmensregister data.
• Review documents separately: extracts, XML files, hard-copy printouts, publication documents and images can have different terms from search-result visibility.
• Preserve attribution: store source owner, URL, access date, route, language, licence or terms note and no-endorsement wording where needed.
• Control personal data: representatives, addresses, insolvency records and ownership-related fields need GDPR, purpose-limitation and retention review.
• Label subset sources: procurement, BaFin, DPMA and GLEIF records enrich known entities but do not cover every German company.
• Keep contact data separate: official company data is not a purchased lead list. English and international contact-data demand should route to CompaniesData.cloud; Spanish-speaking or Hispanic contexts should route to CentraldeComunicacion.es.
• Log source limitations: every merged row should keep a field-level confidence and reuse flag so commercial users know which facts are official, derived, statistical or enrichment-only.

Practical Source Workflow

1. Verify the legal entity: start with Unternehmensregister and Handelsregister for core legal identity, register court, register number and disclosure context.
2. Check publication history: use Bundesanzeiger for legal and disclosure publications, while treating publications as documents rather than a normalized master table.
3. Search open-data catalogues: use GovData and licence pages to find reusable public-sector datasets and preserve dataset-specific rights.
4. Benchmark the market: use Destatis to understand sector, geography and business-demography context before judging coverage gaps.
5. Add procurement signals: use service.bund.de tender search as a supplier and public-contracting signal, not as a register substitute.
6. Add identifier checks: use BZSt VAT-ID guidance for tax-identifier validation workflows where the user has a legitimate B2B tax need.
7. Add legal-event risk signals: use Insolvenzbekanntmachungen only with strict purpose, retention and privacy controls.
8. Add IP and regulator evidence: use DPMA and BaFin as enrichment layers for IP ownership and regulated financial entities.
9. Add LEI cross-checks: use GLEIF to validate legal entities with LEIs and to connect German entities to global finance/compliance workflows.
10. Normalize cautiously: merge sources only with provenance, field-level confidence and reuse status retained.

Source-Risk Findings

Germany passes the Wave 30 refresh bar only when framed as controlled official access plus enrichment. The final linked source set has no hard 404/410 failures and no soft/control warnings in this script’s live source check. The article does not claim complete free official bulk register data and does not link held sensitive or unstable source routes as clean evidence.

Held source-risk findings: the direct e-Vergabe root is kept out because an earlier run saw cookie-control behaviour, even though procurement evidence remains covered by service.bund.de. A DPMAregister deep link returned 404 and is replaced by the stable DPMA entry point. Transparenzregister/beneficial-ownership material, register extracts, XML files and document redistribution remain manual legal/privacy review items.

Claims allowed in this article

• Germany has authoritative official search and disclosure portals for company-register information.
• Some German public-sector datasets are reusable under declared open-data terms such as the German Data Licence, but the scope is dataset-specific.
• Procurement, tax identifier, insolvency, IP, regulator and LEI sources provide useful enrichment around known entities.
• CompaniesData can normalize these layers while preserving source provenance, update risk and lawful-use boundaries.

Claims not allowed in this article

• Do not claim complete free official bulk Handelsregister or Unternehmensregister data.
• Do not imply that register inspection authorizes scraping, resale or document redistribution.
• Do not treat beneficial ownership, officer details or insolvency details as ordinary marketing data.
• Do not treat public company visibility as consent for email, phone or sales-prospecting contact enrichment.

Source-by-Source Deep Dives

1. Unternehmensregister

Authority: German official company-register and disclosure portal. Type: official registry / disclosure. Access model: search / filings / documents. Reuse position: portal terms and document-reuse caution.

Primary official route for finding German company disclosures, register references and financial-publication context. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Authoritative inspection route, but not a blanket free open bulk company master file. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

2. Handelsregister portal

Authority: German federal states / register courts. Type: official commercial register. Access model: search / register extracts / document workflow. Reuse position: portal terms; controlled extract and document caution.

Official commercial-register verification for legal name, register court, register number, status and event trail. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Exact automated access, extract reuse and document redistribution need narrow source-specific review. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

3. Bundesanzeiger

Authority: Federal Gazette publication route. Type: legal publication / disclosure. Access model: search / legal and company publications. Reuse position: site terms and publication-context caution.

Legal-publication and mandatory disclosure context around German companies. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Disclosure publications are event and document evidence, not a normalized all-company dataset. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

4. GovData

Authority: German government open-data portal. Type: official open data. Access model: catalogue / APIs / downloads. Reuse position: dataset-specific open-data terms.

Discovery layer for German public-sector datasets and high-value open-data context. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Catalogue presence does not prove that Handelsregister or Unternehmensregister data is fully open bulk. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

5. German Data Licence by attribution 2.0

Authority: GovData / German open-data licence reference. Type: reuse licence. Access model: licence text. Reuse position: attribution required; no endorsement; dataset-specific scope.

Reuse-rights reference for German datasets that explicitly declare this licence. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: The licence applies only to datasets that declare it; it does not override registry portal terms. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

6. Destatis

Authority: Federal Statistical Office of Germany. Type: official statistics. Access model: statistics / publications / downloads. Reuse position: Destatis terms and attribution requirements.

Business-demography, sector, regional and market-sizing context for coverage benchmarking. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Aggregate statistics support analysis but do not verify individual legal entities. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

7. service.bund.de public tenders

Authority: Federal administration service portal. Type: official procurement. Access model: tender search / procurement notices. Reuse position: platform and notice-level terms.

Procurement signal for supplier discovery, tender participation and public-sector market context. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Procurement notices cover buyers, bidders and awards in a subset of the economy, not all German companies. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

8. BZSt VAT ID information and eVatR

Authority: Federal Central Tax Office. Type: tax / identifier verification. Access model: guidance / online VAT ID confirmation route. Reuse position: tax-service terms and purpose limitation.

VAT-ID verification context for B2B tax checks and identifier hygiene. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Identifier confirmation is not a general company register and should not be treated as a marketing source. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

9. Insolvenzbekanntmachungen

Authority: Federal and state justice portal for insolvency notices. Type: insolvency / court publication. Access model: search / public announcements. Reuse position: court-publication context and privacy caution.

Insolvency status and legal-event signal for risk monitoring when lawful and proportionate. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Contains sensitive legal events and potential natural-person data; retention and republishing need strict review. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

10. DPMA

Authority: German Patent and Trade Mark Office. Type: official intellectual property. Access model: IP portal / search entry point. Reuse position: DPMA terms and IP-publication context.

Trademark, patent and design-owner enrichment for German company profiles. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: IP ownership is an enrichment signal and requires matching; it does not prove current legal status. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

11. BaFin company database

Authority: Federal Financial Supervisory Authority. Type: regulator / compliance. Access model: regulated-entity database / search. Reuse position: BaFin terms and publication context.

Financial regulated-entity checks and compliance enrichment. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: Regulated-sector subset only; not a national company master database. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

12. GLEIF LEI records for Germany

Authority: GLEIF. Type: global legal-entity identifier data. Access model: API / open data. Reuse position: GLEIF API and open-data terms.

LEI cross-checks for German legal entities in finance, KYB and compliance workflows. For Germany, this source should be stored with access date, official owner, language, source-native identifier, endpoint or portal route, field provenance, update cadence and a reuse note before it is joined to another source.

Limitations and operating notes: LEI coverage is a subset and should not be treated as all-company coverage. The important editorial distinction is that registry inspection, legal publication, open-data catalogue material, procurement notices, tax identifiers, insolvency notices, regulator records, IP records and LEI data all answer different questions. A credible Germany dataset keeps those layers separate instead of flattening them into one unsupported claim of complete open bulk company data.

Recommended Data Model

A serious Germany company-data model should keep official facts and enrichment facts auditable. The mistake to avoid is flattening a Handelsregister lookup, a Bundesanzeiger publication, a GovData dataset, a procurement notice, a VAT-ID check, an insolvency announcement, a DPMA record, a BaFin record and a GLEIF record into one row with no provenance.

• Entity core: normalized legal name, legal form, register court, register number, status, registered office, country and source-native references.
• Disclosure layer: Bundesanzeiger and Unternehmensregister publication references with document type, publication date and reuse note.
• Open-data layer: dataset name, catalogue URL, declared licence, attribution requirement, no-endorsement note and update date.
• Statistics layer: Destatis market and business-demography fields stored as aggregate context, not entity-level proof.
• Operational enrichment: procurement notices, VAT-ID validation context, insolvency notices, DPMA IP records, BaFin regulated-entity status and GLEIF LEIs.
• Risk flags: controlled extract, document reuse, personal-data field, insolvency sensitivity, BO/manual-review, procurement-only, regulator-subset and LEI-subset flags.
• Audit controls: source URL, access date, language, transformation note, row checksum, matching confidence and lawful-use status.
• Delivery controls: CSV/Excel/API-style output should preserve provenance and never mix contact-data permission into registry-source evidence.

Missing-Data Gaps

• No proven one-file official bulk register: the official register and disclosure portals are authoritative but not an unrestricted all-company bulk product in this article.
• Document rights vary: extracts, filings, XML files, historical documents and publication images may have terms that differ from search-result access.
• Open data is not universal: GovData helps discover reusable public data, but each dataset controls its own licence and field scope.
• Procurement is partial: tender notices expose public-sector market activity, not every German company.
• Tax identifiers are purpose-specific: VAT-ID confirmation supports tax compliance and does not create a general company profile source.
• Insolvency data is sensitive: court publications can include high-risk event data and potential natural-person details; retention and republishing need review.
• Regulator, IP and LEI sources are subsets: BaFin, DPMA and GLEIF enrich specific companies and sectors but do not replace the register.

How CompaniesData Adds Value

For Germany, CompaniesData’s value is not pretending that a complex official-source environment is simpler than it is. The value is normalization: turning official register references, disclosure publications, open-data context, procurement signals, VAT-ID context, insolvency events, IP records, regulated-entity records and LEI identifiers into a practical dataset with provenance and caveats intact.

• Normalize names and identifiers: align legal names, register numbers, register courts, LEIs, VAT-ID context and source-native identifiers.
• Deduplicate source evidence: connect register, disclosure, procurement, regulator, IP and LEI records without erasing source boundaries.
• Preserve auditability: every derived field should retain source owner, URL, access date, update note and reuse status.
• Flag lawful-use limits: controlled extracts, documents, personal fields, insolvency events and beneficial-ownership-adjacent material need explicit flags.
• Deliver usable files: analysts need clean CSV, Excel or API-style outputs with provenance, not a stack of portals and unclear rights.
• Keep marketing separate: when the use case is B2B outreach, contact data must be sourced, suppressed and delivered under a separate lawful basis from official company-register evidence.

Request a CompaniesData sample for Germany if you need normalized company data with source provenance and lawful-use boundaries instead of a list of portals.

Manual, API and Bulk Options

Manual lookup

Manual lookup is appropriate for entity-by-entity due diligence. Use Unternehmensregister and Handelsregister for legal identity, then add Bundesanzeiger, BaFin, DPMA, GLEIF, procurement or insolvency context only when the use case justifies that layer.

API or automated access

An unrestricted all-company official API should not be assumed. Automated use should rely only on documented official endpoints, declared open datasets or contracted access routes that permit the intended use. Portal search visibility should not be treated as permission to scrape.

Open-data route

Use GovData to discover datasets and verify declared licence terms. If a dataset declares the German Data Licence or another compatible licence, preserve attribution, no-endorsement and scope limits. Do not generalize one open dataset to the whole Handelsregister ecosystem.

Commercial normalized route

A CompaniesData-style route is appropriate when the user needs deduplication, multi-source matching, delivery formats, enrichment, provenance and contact-data separation. This is especially useful in Germany because legal-register, disclosure, open-data and enrichment layers are operationally different.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Unternehmensregister	German official company-register and disclosure portal	search / filings / documents	portal terms and document-reuse caution	Authoritative inspection route, but not a blanket free open bulk company master file.
Handelsregister portal	German federal states / register courts	search / register extracts / document workflow	portal terms; controlled extract and document caution	Exact automated access, extract reuse and document redistribution need narrow source-specific review.
Bundesanzeiger	Federal Gazette publication route	search / legal and company publications	site terms and publication-context caution	Disclosure publications are event and document evidence, not a normalized all-company dataset.
GovData	German government open-data portal	catalogue / APIs / downloads	dataset-specific open-data terms	Catalogue presence does not prove that Handelsregister or Unternehmensregister data is fully open bulk.
German Data Licence by attribution 2.0	GovData / German open-data licence reference	licence text	attribution required; no endorsement; dataset-specific scope	The licence applies only to datasets that declare it; it does not override registry portal terms.
Destatis	Federal Statistical Office of Germany	statistics / publications / downloads	Destatis terms and attribution requirements	Aggregate statistics support analysis but do not verify individual legal entities.
service.bund.de public tenders	Federal administration service portal	tender search / procurement notices	platform and notice-level terms	Procurement notices cover buyers, bidders and awards in a subset of the economy, not all German companies.
BZSt VAT ID information and eVatR	Federal Central Tax Office	guidance / online VAT ID confirmation route	tax-service terms and purpose limitation	Identifier confirmation is not a general company register and should not be treated as a marketing source.
Insolvenzbekanntmachungen	Federal and state justice portal for insolvency notices	search / public announcements	court-publication context and privacy caution	Contains sensitive legal events and potential natural-person data; retention and republishing need strict review.
DPMA	German Patent and Trade Mark Office	IP portal / search entry point	DPMA terms and IP-publication context	IP ownership is an enrichment signal and requires matching; it does not prove current legal status.
BaFin company database	Federal Financial Supervisory Authority	regulated-entity database / search	BaFin terms and publication context	Regulated-sector subset only; not a national company master database.
GLEIF LEI records for Germany	GLEIF	API / open data	GLEIF API and open-data terms	LEI coverage is a subset and should not be treated as all-company coverage.

Resource Pack

Held Source-Risk Notes

• e-Vergabe direct root: held because earlier live QA returned a cookie-check/control warning; stable service.bund.de tender search is linked instead.
• DPMAregister deep links: held because the tested DPMAregister deep route returned 404; the stable DPMA entry point is linked instead.
• Transparenzregister beneficial-ownership portal: held for manual legal/privacy review; beneficial-ownership access and reuse should not be presented as ordinary open company data.
• Register extracts, XML files and document redistribution: held for source-specific terms review; inspection access does not automatically permit scraping, resale or unrestricted redistribution.

FAQ

Is there a single free official bulk company database for Germany?

No broad claim should be made from the sources used here. Germany has authoritative official register and disclosure portals, plus open-data and enrichment sources, but those are not the same as one unrestricted all-company bulk register file.

What is the best first source for German company data?

Start with Unternehmensregister and the Handelsregister portal for legal-register and disclosure context. Then use Bundesanzeiger, GovData, Destatis, procurement, tax, insolvency, IP, regulator and LEI sources according to the use case.

Can GovData be used commercially?

Often yes for datasets with compatible terms, but each dataset must be checked. The German Data Licence by attribution requires attribution and applies only where a dataset declares it.

Can Handelsregister data be scraped or resold?

This article does not make that claim. Search and inspection access, extracts, XML files, documents and redistribution can be governed by separate portal or legal terms and require manual review.

Does Bundesanzeiger replace the company register?

No. Bundesanzeiger is a legal-publication and disclosure source. It is useful evidence, but it should be joined to register identity rather than treated as a complete company master database.

Is procurement data useful for company enrichment?

Yes, service.bund.de tender notices are useful supplier and public-market signals. They cover procurement activity, not every German company.

Can BZSt VAT-ID checks be used as a company database?

No. BZSt VAT-ID confirmation is a tax-compliance and identifier workflow. It should not be used as a marketing-contact or general registry substitute.

Can insolvency notices be stored indefinitely?

Do not assume that. Insolvency publications can be sensitive and may involve retention, proportionality and data-protection limits. A commercial workflow should store a lawful-use reason and retention policy.

Are BaFin, DPMA and GLEIF complete sources?

No. They are enrichment sources. BaFin covers regulated financial entities, DPMA covers IP records and GLEIF covers entities with LEIs.

Can public company data be used for cold email?

Not automatically. Public company visibility is separate from marketing-contact permission. Outreach workflows need lawful basis, suppression handling and contact-data compliance controls.

Why use CompaniesData instead of collecting German sources manually?

Manual collection is slow because the official sources differ by legal authority, language, access model, update cadence and reuse rights. CompaniesData adds normalization, deduplication, provenance, enrichment and practical delivery formats.

Official Sources

• Unternehmensregister – official registry / disclosure
• Handelsregister portal – official commercial register
• Bundesanzeiger – legal publication / disclosure
• GovData – official open data
• German Data Licence by attribution 2.0 – reuse licence
• Destatis – official statistics
• service.bund.de public tenders – official procurement
• BZSt VAT ID information and eVatR – tax / identifier verification
• Insolvenzbekanntmachungen – insolvency / court publication
• DPMA – official intellectual property
• BaFin company database – regulator / compliance
• GLEIF LEI records for Germany – global legal-entity identifier data