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

Greece has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate Greece is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.

The strongest route is GEMI public company services and GEMI open-data/API access, enriched with ELSTAT, Diavgeia and procurement sources. That makes Greece a fragmented but increasingly API-visible registry ecosystem, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.

This guide maps the main official sources for company data in Greece, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.

The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.

Quick Answer

Greece is stronger than the older generic view suggests because GEMI now gives the article a real official API/open-data angle.

For practical work, the most useful source stack is: GEMI open-data service, GEMI overview, GEMI / OSS portal, Greek open-data portal, ELSTAT business statistics, ELSTAT SBR publication.

The safe editorial answer is this: Greece has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.

A serious Greece dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.

Key Takeaways

• Best starting point: GEMI public company services and GEMI open-data/API access, enriched with ELSTAT, Diavgeia and procurement sources.
• Core source stack: GEMI open-data service, GEMI overview, GEMI / OSS portal, Greek open-data portal, ELSTAT business statistics, ELSTAT SBR publication.
• Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
• Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
• Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.

Editorial Methodology

This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.

• Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
• Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
• Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
• Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
• Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.

What Counts as Company Data in Greece?

In Greece, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.

Reuse Rights and Compliance

Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, Greece's actual reuse position still depends on each source, endpoint, licence and access method.

• Cite official sources and preserve update dates where the source provides them.
• Do not imply that a derived dataset is endorsed by the registry or public authority.
• Do not mix public register data with marketing-contact permission.
• Check whether API, bulk download, paid extract and web-search access have different terms.
• Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.

Greece has a central official register through GEMI and public data services, but the broader data ecosystem is fragmented. The strongest article angle is GEMI plus Diavgeia/procurement/ELSTAT/IP, with caution around API reliability and marketing-contact use.

Coverage, Access and Update Risk

The most common mistake in Greece company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.

• Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
• Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
• Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
• Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
• Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.

Reuse Checklist for Greece

Resource Pack

Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.

Main Official Sources: Deep Dive

1. GEMI open-data service

Owner: General Commercial Registry. Access: https://opendata.businessportal.gr/.

• What it gives: Swagger/OpenAPI-style access to public GEMI data
• Reuse value: Strong official API/open-data signal
• Main limitation: API-key and endpoint terms must be checked live

GEMI open-data service is a General Commercial Registry source for Greece. Its main practical value is Swagger/OpenAPI-style access to public GEMI data Access is through https://opendata.businessportal.gr/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Strong official API/open-data signal. The main limitation is API-key and endpoint terms must be checked live In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

2. GEMI overview

Owner: General Commercial Registry. Access: https://www.businessportal.gr/en/what-is-g-e-mi/.

• What it gives: Official explanation of GEMI
• Reuse value: Official register context
• Main limitation: Not API documentation

GEMI overview is a General Commercial Registry source for Greece. Its main practical value is Official explanation of GEMI Access is through https://www.businessportal.gr/en/what-is-g-e-mi/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Official register context. The main limitation is Not API documentation In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

3. GEMI / OSS portal

Owner: General Commercial Registry. Access: https://www.businessportal.gr/en/home-en/.

• What it gives: Company search and public company data service
• Reuse value: Official source
• Main limitation: API/bulk terms need confirmation

GEMI / OSS portal is a General Commercial Registry source for Greece. Its main practical value is Company search and public company data service Access is through https://www.businessportal.gr/en/home-en/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Official source. The main limitation is API/bulk terms need confirmation In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

4. Greek open-data portal

Owner: Government of Greece. Access: https://data.gov.gr/.

• What it gives: National open datasets and APIs
• Reuse value: Dataset-specific reuse
• Main limitation: Portal/API quality varies

Greek open-data portal is a Government of Greece source for Greece. Its main practical value is National open datasets and APIs Access is through https://data.gov.gr/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Dataset-specific reuse. The main limitation is Portal/API quality varies In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

5. ELSTAT business statistics

Owner: Hellenic Statistical Authority. Access: https://www.statistics.gr/en/statistics/ind.

• What it gives: Statistical Business Register and enterprise statistics
• Reuse value: Official aggregate data
• Main limitation: Not legal company master file

ELSTAT business statistics is a Hellenic Statistical Authority source for Greece. Its main practical value is Statistical Business Register and enterprise statistics Access is through https://www.statistics.gr/en/statistics/ind, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Official aggregate data. The main limitation is Not legal company master file In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

6. ELSTAT SBR publication

Owner: ELSTAT. Access: https://lms.statistics.gr/documents/20181/18511159/NWS_STAT_BUSIN_REG_EN.pdf/969a910d-04d1-05fe-b1ae-3d4e8366ea73.

• What it gives: Statistical Business Register tables
• Reuse value: Official statistical source
• Main limitation: Aggregate tables

ELSTAT SBR publication is a ELSTAT source for Greece. Its main practical value is Statistical Business Register tables Access is through https://lms.statistics.gr/documents/20181/18511159/NWS_STAT_BUSIN_REG_EN.pdf/969a910d-04d1-05fe-b1ae-3d4e8366ea73, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Official statistical source. The main limitation is Aggregate tables In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

7. ESIDIS / procurement

Owner: Greek procurement system. Access: https://www.eprocurement.gov.gr/.

• What it gives: Procurement procedures
• Reuse value: Procurement signal
• Main limitation: Supplier-only coverage

ESIDIS / procurement is a Greek procurement system source for Greece. Its main practical value is Procurement procedures Access is through https://www.eprocurement.gov.gr/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Procurement signal. The main limitation is Supplier-only coverage In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

8. Diavgeia

Owner: Greek transparency programme. Access: https://diavgeia.gov.gr/.

• What it gives: Government decisions, spending and public acts
• Reuse value: Public decision signal
• Main limitation: Not a company register

Diavgeia is a Greek transparency programme source for Greece. Its main practical value is Government decisions, spending and public acts Access is through https://diavgeia.gov.gr/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Public decision signal. The main limitation is Not a company register In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

9. Hellenic Industrial Property Organisation

Owner: OBI. Access: https://www.obi.gr/en/.

• What it gives: Patents, trademarks and designs
• Reuse value: IP signal
• Main limitation: Rights separate

Hellenic Industrial Property Organisation is a OBI source for Greece. Its main practical value is Patents, trademarks and designs Access is through https://www.obi.gr/en/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: IP signal. The main limitation is Rights separate In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

10. Hellenic Competition Commission

Owner: HCC. Access: https://www.epant.gr/en/.

• What it gives: Competition decisions
• Reuse value: Risk signal
• Main limitation: Decision-based

Hellenic Competition Commission is a HCC source for Greece. Its main practical value is Competition decisions Access is through https://www.epant.gr/en/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Risk signal. The main limitation is Decision-based In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

Practical Options

Official open-data or API route

Use GEMI and GEMI open-data/API access as the company identity layer, then add ELSTAT, Diavgeia, ESIDIS procurement, OBI and financial regulators.

For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.

Manual verification and document route

Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.

Contact-data and marketing-list route

For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.

Private reports and risk products

Private company-report providers can be useful for manual due diligence in Greece, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.

If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.

API, Publicity and Personal-Data Boundaries

Greece has one of the clearest official API stories in Southern Europe, but it is not a licence to treat every GEMI field as unrestricted bulk data. The GEMI open-data service, data-provision route and integrated-systems pages support an official API and public-data narrative, while public search, certificates, documents, KED/web-service access, statistics and regulator data can follow different rules. Treat GEMI as the company-identity backbone first, then review endpoint, API-key, document, fee, personal-data and redistribution conditions before operational reuse.

• Allowed claim: Greece has a central official company register through GEMI and official GEMI open-data/API evidence.
• Blocked claim: every GEMI dataset, filing, officer field, API endpoint or certificate is freely bulk downloadable without registration, API-key or terms review.
• Operational rule: keep GEMI identity, GEMI publications/documents, ELSTAT statistics, Diavgeia/procurement events, IP/regulator signals and contact data in separate model layers.

Contact-Data Boundary

Public company records are not a cold-email licence. If the business need is enriched company records, segmentation, email or phone workflows for an English or international audience, route the workflow through CompaniesData.cloud. For Spanish-speaking or Hispanic outreach workflows, CentraldeComunicacion.es is the preferred property. This article does not recommend third-party contact-data sellers as evidence for official Greek reuse rights.

What Is Missing from Official Open Data?

• GEMI access may require API keys or registration depending on the endpoint.
• Greek public-decision and procurement data are enrichment layers, not a company master file.
• API access does not create marketing-contact permission.

This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.

Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.

Recommended Data Model

A practical CompaniesData-style model for Greece should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.

• Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
• Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
• Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
• Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
• Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.

How CompaniesData Adds Value

For Greece, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.

• Normalize register identifiers and legal names.
• Match official company records with procurement, IP, LEI and regulator signals.
• Flag source provenance so every derived profile can be audited.
• Separate company identity from contact-data and marketing-permission layers.
• Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.

For Greece, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.

Request a CompaniesData sample for Greece if you need a practical dataset rather than a list of source portals.

Source Matrix

Source	Owner	What it gives	Reuse value	Limitations
GEMI open-data service	General Commercial Registry	Swagger/OpenAPI-style access to public GEMI data	Strong official API/open-data signal	API-key and endpoint terms must be checked live
GEMI overview	General Commercial Registry	Official explanation of GEMI	Official register context	Not API documentation
GEMI / OSS portal	General Commercial Registry	Company search and public company data service	Official source	API/bulk terms need confirmation
Greek open-data portal	Government of Greece	National open datasets and APIs	Dataset-specific reuse	Portal/API quality varies
ELSTAT business statistics	Hellenic Statistical Authority	Statistical Business Register and enterprise statistics	Official aggregate data	Not legal company master file
ELSTAT SBR publication	ELSTAT	Statistical Business Register tables	Official statistical source	Aggregate tables
ESIDIS / procurement	Greek procurement system	Procurement procedures	Procurement signal	Supplier-only coverage
Diavgeia	Greek transparency programme	Government decisions, spending and public acts	Public decision signal	Not a company register
Hellenic Industrial Property Organisation	OBI	Patents, trademarks and designs	IP signal	Rights separate
Hellenic Competition Commission	HCC	Competition decisions	Risk signal	Decision-based
GEMI provided services	General Commercial Registry	Official GEMI service map including publicity, statistics, data provision, BRIS and follow-company services	Official service context; reuse depends on the specific service, terms and access model	Service overview, not a blanket permission for all GEMI data or documents
GEMI data provision	General Commercial Registry	Official data-provision route for G.E.MI. data to third parties and public bodies	Official data-provision context; contractual, API-key or public-body conditions may apply	Do not describe as unrestricted public bulk access; check each data-provision route
GEMI integrated systems	General Commercial Registry	Official description of GEMI/e-OSS systems including registry, publication, statistics and web services via KED	Official systems context; data reuse still depends on endpoint and service terms	System map, not a standalone download endpoint
GEMI terms of use	General Commercial Registry	Official portal terms for GEMI browsing and electronic services	Terms-controlled reuse; cite the source and avoid implying official endorsement	Terms page is a compliance source, not a data source by itself
ELSTAT home	Hellenic Statistical Authority	Official statistics entry point for Greece	Official statistics terms and source-reference requirements	Statistics are context and benchmarks, not legal company profiles
GLEIF LEI records for Greece	Global Legal Entity Identifier Foundation	Open LEI cross-checks for Greek legal entities with LEIs	GLEIF API/open-data terms; attribution and API conditions apply	LEI coverage is a regulated-market/KYB subset, not the national GEMI register

Greece needs a "fragmented but rich" article: GEMI for identity, ELSTAT for business counts, Diavgeia/procurement for public-sector signals.

Held Source Notes

• Geodata CKAN old route: connect timeout from this node; geospatial/open-data context is not required for the company-data evidence stack
• Hellenic Capital Market Commission: connect timeout during live QA; held as regulator context, not linked as clean source evidence
• Bank of Greece supervised institutions: HTTP 403 Access Denied from this node; held as financial-regulator context until browser/manual source QA passes
• GEMI / data.gov API guessed subpaths: guessed API subpaths returned 404 and were not used; the clean linked evidence is the official GEMI open-data service page and data.gov.gr portal

FAQ

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

Not always. Greece has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.

What is the best first source for Greece company data?

The best first source is GEMI public company services and GEMI open-data/API access, enriched with ELSTAT, Diavgeia and procurement sources. It should then be combined with statistics, procurement, IP and regulator sources.

Can public company data be reused commercially?

Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.

Can I use registry data for cold email marketing?

No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.

Why use CompaniesData instead of manually collecting Greece sources?

Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.

How often should Greece company data be refreshed?

Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.

What should be audited before publishing or selling an enriched dataset?

Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.

Sources

• GEMI open-data service – General Commercial Registry
• GEMI overview – General Commercial Registry
• GEMI / OSS portal – General Commercial Registry
• Greek open-data portal – Government of Greece
• ELSTAT business statistics – Hellenic Statistical Authority
• ELSTAT SBR publication – ELSTAT
• ESIDIS / procurement – Greek procurement system
• Diavgeia – Greek transparency programme
• Hellenic Industrial Property Organisation – OBI
• Hellenic Competition Commission – HCC
• GEMI provided services – General Commercial Registry
• GEMI data provision – General Commercial Registry
• GEMI integrated systems – General Commercial Registry
• GEMI terms of use – General Commercial Registry
• ELSTAT home – Hellenic Statistical Authority
• GLEIF LEI records for Greece – Global Legal Entity Identifier Foundation