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

Egypt has a large and commercially important official company-data ecosystem, but it should be described as a controlled official-source stack rather than a single free open company register. The strongest route starts with GAFI and the Internal Trade Development Authority for company formation and commercial-register authority, then adds tax, e-invoicing, procurement, statistics, intellectual-property, financial-regulator, central-bank, listed-company and LEI layers.

The old CompaniesData Egypt page was live and indexable, but Wave 182 estimated it at about 1,936 words and found that it lacked the newer deep-reference sections. This article rebuilds the guide around the current quality bar: official sources first, source limitations, reuse cautions, privacy and marketing-contact boundaries, a source matrix with stable favicon cues, practical access routes, missing data gaps and a recommended data model.

The safe editorial claim is narrow but useful. Egypt has strong official source coverage for verification and enrichment. The unsafe claim is that all Egyptian companies can be downloaded freely, reused without terms, or converted into lead lists. Any production dataset should preserve source provenance, access dates and lawful-use notes.

Key Takeaways

• Primary authority stack: use GAFI and ITDA for company-formation and commercial-register context.
• No complete bulk claim: this cycle did not verify a complete free official Egyptian company-register bulk download or unrestricted public API.
• Best enrichment layers: ETA, e-invoicing, procurement, CAPMAS and GLEIF can improve entity matching and market context; EGPO, FRA, CBE and EGX remain source-risk layers until their public routes pass final bot/source QA.
• Access model: many routes are service pages, portals, paid/controlled workflows or sector-specific datasets rather than open reusable microdata.
• Contact-data boundary: registry, tax, tender, officer, listed-company, email and phone data are not permission for sales outreach.

Editorial Methodology

This article uses an official-sources-first method. Each source was classified by owner, authority, access model, reuse note, business use and limitation, then checked under browser, Googlebot and Bingbot-style profiles. Sources that returned usable public content and matched expected semantics are treated as clean linked evidence. Sources that failed status, challenge, TLS, semantic or profile checks remain held until manual review.

The content QA follows the current CompaniesData country-page standard: minimum 2,400 words, preferred 2,800 to 3,800 for complex jurisdictions, Key Takeaways, editorial methodology, coverage and update-risk analysis, reuse checklist, source-by-source deep dives, practical manual/API/bulk options, missing-data gaps, recommended data model, CompaniesData value section, expanded FAQ, official sources, source matrix, Resource Pack and visible source-logo cues.

All claims are constrained. A source page can prove authority or workflow context without proving bulk reuse. A procurement or regulator route can enrich entities without covering the whole economy. A tax or e-invoice route can support verification without creating marketing permission. The article should publish only after the final source-live and public crawler QA pass.

Coverage, Access and Update-Risk Analysis

Registry coverage: GAFI and ITDA are the main official company-service and commercial-register authority routes. GAFI’s incorporation guidance is useful for company formation, commercial-register entry and investor-service workflows. ITDA provides commercial-registry authority and service context. These are strong official anchors, but they do not by themselves establish a complete free registry bulk file.

Tax and e-invoice coverage: the Egyptian Tax Authority and e-invoice guidance help with taxpayer, VAT, electronic invoice and compliance context. These routes can support known-entity verification and fiscal-system enrichment. They are privacy and purpose sensitive. Taxpayer identifiers, e-invoice records and taxpayer service routes should not be treated as marketing lists.

Procurement coverage: Egypt’s eTenders and EONEPS routes provide supplier and public procurement context. Procurement data is valuable for public-sector sales intelligence and supplier matching, but it is an event layer. It does not cover companies that do not sell to the public sector, and supplier names often need careful matching back to GAFI or ITDA identity.

Statistics, IP and regulated-sector coverage: CAPMAS provides establishment and economic context, EGPO adds patent and IP signals, FRA and CBE cover financial-sector subsets, EGX covers listed companies, and GLEIF adds structured LEI records for covered entities. These sources improve enrichment and quality control, but each has a narrower scope than the company register.

Update risk: Egypt source routes may change domains, language coverage, TLS behavior, service requirements, fee pages and bot responses. A material WordPress update should rerun source-live QA, external link checks, source-logo rendering, public crawler access for the canonical URL, sitemap XML checks and indexing workflows only after publication.

Reuse Checklist

• Source provenance: store source name, authority, URL, access date, profile result and exact field route for every claim.
• Licence and terms: check GAFI, ITDA, ETA, procurement, CAPMAS and GLEIF terms separately, and keep EGPO, FRA, CBE and EGX terms in held-source review.
• No endorsement: do not imply that a CompaniesData dataset is endorsed by any Egyptian public authority.
• Bulk caution: do not claim a complete free official company-register API or bulk file without direct official proof.
• Privacy controls: flag natural-person, officer, owner, taxpayer, address, email and phone fields for purpose limitation and retention review.
• Marketing separation: official company identity is not permission to send email, call, enrich phone lists or build lead lists.
• Update tracking: keep source date, parser version and last-seen source status beside normalized records.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
GAFI company incorporation services	General Authority for Investment and Free Zones	public service guidance / controlled incorporation workflows	GAFI terms and service-specific rules	Service guidance and fees are not a complete open company register or reusable bulk dataset.
GAFI investor service center	General Authority for Investment and Free Zones	portal / investor services	GAFI terms	Institutional portal, not a downloadable company master file.
Internal Trade Development Authority	Internal Trade Development Authority	public portal / registry services	ITDA terms	Portal coverage and language availability vary; no complete open bulk proof.
ITDA commercial registry services	Internal Trade Development Authority	service page / controlled registry workflow	ITDA terms	Service page; does not establish open registry bulk reuse.
Egyptian Tax Authority	Egyptian Tax Authority	taxpayer services / guidance / inquiries	ETA privacy and service terms	Tax context is not marketing-contact permission and may involve protected taxpayer data.
Egypt e-invoice guides	Egyptian Tax Authority	public guidance pages	ETA terms	Guidance layer, not company-register coverage.
EONEPS public e-procurement system	Egypt public e-procurement system	e-procurement portal / G2B workflows	portal terms and procurement-publication rules	Procurement workflow layer, not all-entity registry coverage.
CAPMAS establishment statistics catalogue	Central Agency for Public Mobilization and Statistics	metadata catalogue / statistical releases	CAPMAS and dataset-specific terms	Aggregate or survey/statistical layer; not legal-entity master data.
GLEIF LEI records for Egypt	Global Legal Entity Identifier Foundation	public API	GLEIF API terms	LEI coverage is partial and skewed toward financial/cross-border entities.

Source-by-Source Deep Dives

GAFI company incorporation services

Authority: General Authority for Investment and Free Zones. Type: official company/investment services. Access model: public service guidance / controlled incorporation workflows. Reuse note: GAFI terms and service-specific rules.

This is the strongest evidence route for company-formation context. It describes incorporation fees, commercial-register entry and related investor-service workflows. Use it to explain formation and register entry, but do not turn a service page into a claim that GAFI publishes an unrestricted company master file.

Main limitation: Service guidance and fees are not a complete open company register or reusable bulk dataset.

GAFI investor service center

Authority: General Authority for Investment and Free Zones. Type: official investment authority portal. Access model: portal / investor services. Reuse note: GAFI terms.

The GAFI portal anchors the investment-authority and investor-service-center context. It supports the claim that company incorporation, mergers, liquidations and investor documents sit in a government service stack. Its limitation is that institutional context is not the same thing as reusable company microdata.

Main limitation: Institutional portal, not a downloadable company master file.

Internal Trade Development Authority

Authority: Internal Trade Development Authority. Type: official commercial-register authority. Access model: public portal / registry services. Reuse note: ITDA terms.

ITDA is the commercial-register authority layer. It is important because it explicitly frames commercial registry services and trade databases as part of Egypt's digital-transformation agenda. For data modelling, ITDA should be treated as the registry authority, while individual fields still need source-route and terms evidence.

Main limitation: Portal coverage and language availability vary; no complete open bulk proof.

ITDA commercial registry services

Authority: Internal Trade Development Authority. Type: official commercial-register service page. Access model: service page / controlled registry workflow. Reuse note: ITDA terms.

The commercial-registry service route helps users understand how official extracts or registry services are requested. It is useful for known-company verification and document workflows. It should be described as a controlled service page unless a separate official open-data endpoint is verified.

Main limitation: Service page; does not establish open registry bulk reuse.

Egyptian Tax Authority

Authority: Egyptian Tax Authority. Type: tax authority / identifier context. Access model: taxpayer services / guidance / inquiries. Reuse note: ETA privacy and service terms.

ETA is a tax and fiscal-compliance layer, not a sales-data layer. Taxpayer services, VAT, e-invoicing and registered-taxpayer inquiries can support verification, but taxpayer identifiers and fiscal records need privacy, purpose and source-terms controls.

Main limitation: Tax context is not marketing-contact permission and may involve protected taxpayer data.

Egypt e-invoice guides

Authority: Egyptian Tax Authority. Type: tax e-invoicing guidance. Access model: public guidance pages. Reuse note: ETA terms.

The e-invoice guidance route is useful for understanding structured fiscal workflows, readiness guides and integration context. It supports enrichment and compliance analysis, but it does not prove company-register coverage and should not be used as marketing-contact permission.

Main limitation: Guidance layer, not company-register coverage.

EONEPS public e-procurement system

Authority: Egypt public e-procurement system. Type: official public e-procurement system. Access model: e-procurement portal / G2B workflows. Reuse note: portal terms and procurement-publication rules.

Procurement sources are valuable for supplier, tender, award and public-contracting activity. They are event sources, not full registry sources. Match suppliers to GAFI/ITDA identity where possible and keep tender fields in a separate procurement table.

Main limitation: Procurement workflow layer, not all-entity registry coverage.

CAPMAS establishment statistics catalogue

Authority: Central Agency for Public Mobilization and Statistics. Type: official statistics / establishment data. Access model: metadata catalogue / statistical releases. Reuse note: CAPMAS and dataset-specific terms.

CAPMAS supports market sizing and quality checks through establishment, employment and sector statistics. It is useful for aggregate context and coverage benchmarks, not legal-entity identity. Store CAPMAS evidence as statistics with survey scope and period metadata.

Main limitation: Aggregate or survey/statistical layer; not legal-entity master data.

GLEIF LEI records for Egypt

Authority: Global Legal Entity Identifier Foundation. Type: LEI API. Access model: public API. Reuse note: GLEIF API terms.

GLEIF gives structured LEI records for Egyptian entities that have Legal Entity Identifiers. It is excellent for cross-border matching and update metadata, but coverage is partial and absence of an LEI is not evidence that a company does not exist.

Main limitation: LEI coverage is partial and skewed toward financial/cross-border entities.

Held Source-Risk Findings

Current result: the following official or useful routes remain in the research map but are not treated as clean linked evidence for this article. They need manual browser, TLS, semantic or source-terms review before publication.

• Egypt Government eTenders Portal: held. Reason: browser status=ConnectTimeout semantic=False challenge=True; googlebot status=ConnectTimeout semantic=False challenge=True; bingbot status=ConnectTimeout semantic=False challenge=True
• Egyptian Patent Office search: held. Reason: browser status=ConnectionError semantic=False challenge=True; googlebot status=ConnectionError semantic=False challenge=True; bingbot status=ConnectionError semantic=False challenge=True
• Financial Regulatory Authority: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=ReadTimeout semantic=False challenge=True; bingbot status=ReadTimeout semantic=False challenge=True
• Central Bank of Egypt: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=200 semantic=False challenge=False; bingbot status=200 semantic=False challenge=False
• Egyptian Exchange listed stocks: held. Reason: Final Wave 188 source QA returned a browser JavaScript/support page and Googlebot/Bingbot connection resets for the Egyptian Exchange listed-stocks route; keep it research-only until browser, Googlebot and Bingbot all return semantic listed-company content.

Practical Manual, API and Bulk Options

Manual verification: start with GAFI and ITDA for authority and workflow context. For a known company, store the searched legal name, local spelling, registration or tax identifier where lawfully available, source route, access date and confidence. Treat documents, certificates and extracts as controlled evidence rather than open scrape targets.

Procurement enrichment: use eTenders and EONEPS for supplier and contract activity where public. Store procurement evidence as events: buyer, supplier, tender, award, stage, value where published, source URL and match confidence. Reconcile supplier names against registry and tax-context records before treating them as unique entities.

Regulated and market enrichment: treat FRA, CBE, EGX and EGPO as valuable regulated-sector, listed-company and IP context only after their routes clear source-risk review. These layers are high value, but all are subsets. They should be linked to the core entity with source-specific confidence.

API and bulk status: GLEIF is the clean structured API layer for entities with LEIs. Procurement and tax systems may expose service or platform workflows, but this article did not verify a complete official open company-register API. Any future bulk route needs licence, field, privacy and update-frequency review before it is recommended.

Missing Data Gaps

• Complete registry bulk: no complete free official GAFI/ITDA company-register bulk file was verified.
• Beneficial ownership: no complete lawful public beneficial-ownership layer was verified for publication in this cycle.
• Historical filings: changes, extracts and certificates may depend on controlled workflows or formal requests.
• Arabic-English normalization: legal names, transliteration, branches and activity descriptions need language-aware matching.
• Marketing contacts: public official data does not establish consent for emails, phone lists or role-based outreach.

Recommended Data Model

An Egypt dataset should use a registry-first core with separate enrichment tables. The core entity table should contain normalized legal name, Arabic and English names where available, registration context, legal form, jurisdiction, source authority, source route, access date and confidence. Do not flatten every official source into a single unqualified profile.

Tax and e-invoice records should sit in a fiscal-context table with strict sensitivity flags. Procurement should sit in an event table with tenders, buyers, awards and supplier matching. CAPMAS should sit in a statistics table with period and methodology notes. EGPO should sit in an IP table. FRA, CBE and EGX should sit in regulated-sector and listed-company tables. GLEIF should sit in a global identifier table with LEI status, legal name, address and update date.

The matching layer should preserve ambiguity. Use identifiers where public and lawful, then normalized names, local-language variants, addresses, sector, procurement context, regulator evidence and manual review flags. Every field should carry source provenance and a reuse note.

CompaniesData Normalization and Enrichment Value

CompaniesData adds value in Egypt by turning fragmented official evidence into a usable, auditable business dataset. Manual users have to move between GAFI, ITDA, tax systems, procurement portals, CAPMAS, held EGPO/FRA/CBE/EGX routes and GLEIF. Those sources differ in language, scope, update cadence, field formats, access rules and reuse terms.

A normalized CompaniesData workflow can standardize names, deduplicate entities, preserve Arabic-English variants, match procurement and LEI signals, mark regulated-sector context, separate sensitive tax or natural-person fields, and deliver source-aware exports for analysis, CRM hygiene and KYB. For English and international contact-data needs, the owned route is CompaniesData.cloud. Official-source company identity and compliant contact enrichment should remain separate workflows.

Grouped Resource Pack

Official Sources

• GAFI company incorporation services – General Authority for Investment and Free Zones
• GAFI investor service center – General Authority for Investment and Free Zones
• Internal Trade Development Authority – Internal Trade Development Authority
• ITDA commercial registry services – Internal Trade Development Authority
• Egyptian Tax Authority – Egyptian Tax Authority
• Egypt e-invoice guides – Egyptian Tax Authority
• EONEPS public e-procurement system – Egypt public e-procurement system
• CAPMAS establishment statistics catalogue – Central Agency for Public Mobilization and Statistics
• GLEIF LEI records for Egypt – Global Legal Entity Identifier Foundation

FAQ

What is the best first source for company data in Egypt?

Start with GAFI and ITDA because they anchor company formation and commercial-register authority. Then add tax, procurement, statistics and LEI layers, while holding IP, regulator and exchange routes until source QA clears depending on the use case.

Is there a complete free official bulk company register for Egypt?

Not verified in this cycle. Egypt has strong official sources, but service workflows, portals, extracts, e-invoice systems and sector lists do not automatically equal a free reusable bulk register.

Can procurement records replace registry data?

No. Procurement records identify public-sector activity and suppliers. They should be matched back to registry identity and treated as events, not as the whole company universe.

Can tax or e-invoice data be used for marketing?

No. Tax and e-invoice records are fiscal-compliance context. They require purpose, privacy and source-terms review and should not be converted into sales-prospecting data.

Why include EGPO, FRA, CBE, EGX and GLEIF?

They add IP, financial-regulator, banking, listed-company and global identifier enrichment. Each is partial, but each can materially improve a source-aware company profile.

How does CompaniesData help?

CompaniesData normalizes names, reconciles source layers, tracks provenance, flags source limitations and separates company identity from contact-data workflows.