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

Kenya is a commercially useful East Africa company-data market because it has a clear official company-registration authority, a public Companies Registry service page, tax and IP context, a clean capital-markets regulator layer, global LEI enrichment and additional source-mapped routes that need bot-profile clearance before they can be linked as evidence. That does not mean Kenya should be described as a simple free bulk company database. The safe article angle is a source map with controlled-access caveats.

The existing CompaniesData Kenya article is already public at https://companiesdata.cloud/open-company-data-kenya.html, but it was written before the current deep-reference standard. The 2026-06-13 source-route cleanup keeps 6 clean linked official or high-quality sources and holds 3 current matrix routes: BRS eCitizen, Central Bank of Kenya and Kenya Gazette. Legacy research-only routes such as Kenya Open Data, PPIP and KNBS remain source-mapped but are not linked as evidence in this publication cycle.

This draft is designed for analysts, KYB teams, market researchers, data buyers and compliance teams who need practical source mapping. It explains what each source can prove, where official reuse is limited, and where CompaniesData normalization adds value without overclaiming open-bulk availability or contact-data permission.

Key Takeaways

• Best first source: Business Registration Service is the official authority context for company registration and registry services.
• Best registry service page: BRS Companies Registry is clean and useful for explaining company search and extract workflows.
• Controlled workflow: the BRS eCitizen portal is source-mapped but held and de-linked after a Bingbot Cloudflare challenge; use the clean BRS authority and Companies Registry pages for public evidence.
• Useful enrichment: KRA iTax, KIPI, CMA and GLEIF add clean linked tax, IP, regulator and LEI context; CBK and Kenya Gazette remain held until bot-profile QA is stable.
• Held sources: the 2026-06-12 gate recorded a Bingbot Cloudflare challenge for BRS eCitizen, connection errors for Central Bank of Kenya, and 500 responses for Kenya Gazette under Googlebot/Bingbot; Kenya Open Data, PPIP and KNBS remain legacy research-only holds.
• Blocked claim: do not claim a complete free reusable BRS bulk register, public beneficial-ownership coverage or marketing-contact permission.

Editorial Methodology

The CompaniesData country method starts with official sources first. Each Kenya source is classified by authority, access model, reuse note, business use, limitation, link policy and live-check result. A link is clean for publication only when the live check returns real content or API data without a hard 404/410, misleading challenge page, empty response, access denial or TLS problem that would create false confidence.

For Kenya, the clean linked evidence stack is BRS authority, BRS Companies Registry, KRA iTax, KIPI, CMA licensees and GLEIF. BRS eCitizen, CBK and Kenya Gazette remain source-relevant, but they are held in this article cycle because the 2026-06-12 quality gate observed a Bingbot Cloudflare challenge, connection errors or bot-profile 500 responses. They can be reintroduced after browser, TLS or official alternate-route QA clears them.

Source logos and favicons are decorative recognition cues only. They make the Source Matrix and Resource Pack easier to scan, but the proof remains the official URL, public owner, access model, reuse note, limitation and access date. This article also separates company identity from contact-data enrichment because a registry, tax, IP, regulator or LEI record is not permission to send cold email, create phone lists or resell personal contact data.

Coverage, Access and Update-Risk Analysis

BRS authority layer: BRS is the main source for Kenya company-registration authority and registry service context. It supports the official-source claim, but not a complete open-bulk claim by itself.

Companies Registry layer: the BRS Companies Registry page supports legal-entity search and extract context. It is the best clean source for explaining where company registry users should begin, while keeping paid, account or controlled extract workflows separate from reusable open data.

eCitizen service layer: the BRS eCitizen portal can support practical manual workflow guidance, but this cleanup keeps it de-linked after a Bingbot Cloudflare challenge. Treat it as a held controlled workflow, not anonymous scraping or open bulk data.

Tax/PIN layer: KRA iTax is useful for tax-service context and known-entity verification, but tax systems have privacy, purpose and access boundaries. Store tax identifiers and taxpayer-service observations separately from registry identity.

IP layer: KIPI can strengthen company profiles through trademark, patent and industrial-property records. Coverage is optional and selective, so absence of IP evidence is not evidence that a company is inactive or invalid.

Regulator layer: CMA adds clean linked high-authority sector context for licensed capital-market entities. CBK remains source-mapped but de-linked until browser, Googlebot and Bingbot profiles can retrieve real content consistently. They should be joined as regulated-subset enrichment, not as economy-wide company registers.

Gazette layer: Kenya Law’s Gazette route can support legal notices and official publication context. Use specific notice dates and references for record-level claims.

LEI layer: GLEIF is useful for standardized legal-entity identifier matching and global enrichment. Coverage is partial and should carry a separate LEI-subset flag.

Held layer: Kenya Open Data, PPIP and KNBS remain important research leads, but this draft does not link them as clean evidence because timeout or TLS validation problems could create crawlability and source-reliability risk.

Reuse Checklist

• Authority check: store whether each field came from BRS, BRS Companies Registry, eCitizen, KRA, KIPI, CMA, CBK, Kenya Law, GLEIF or a held source.
• Access-model check: label official portal, registry service page, account workflow, tax service, IP office, regulator list, gazette page or public API.
• Terms check: preserve source terms, portal terms, service limits, no-endorsement wording and any paid/extract boundaries.
• Access-date check: record live-check date, final URL, page title, content type and local ingestion date.
• Field-provenance check: do not merge registry fields, tax identifiers, regulator status, IP records, gazette events and LEI records without source labels.
• Coverage check: keep regulated-entity, IP-holder, gazette-notice and LEI-holder flags separate from the core company population.
• Privacy check: officer, director, representative, address, tax and contact-like fields need privacy and lawful-use review.
• Marketing check: public official data is not sales-prospecting permission; contact data requires a separate lawful basis and suppression workflow.
• Held-source check: do not publish links or claims based on timeout, SSL mismatch, certificate-chain failure or access-controlled routes until QA clears.

Resource Pack

Source-by-Source Deep Dives

1. Business Registration Service

Authority: Business Registration Service, Government of Kenya. Type: official company registry authority. Access model: official portal / registry services. Reuse note: BRS website and service terms. Business use: Primary authority context for company incorporation, registry services and official filings.

BRS is the official starting point for Kenya company-data work because it anchors incorporation, registry services and company-life filings in the Government of Kenya source family. In a normalized data pipeline, BRS should be stored as the authority layer for registry context, with the access date, final URL and observed page title preserved. The correct editorial claim is that BRS is the official company-registration authority; it is not proof of an unrestricted bulk file or permission to scrape account-controlled services.

Limitation: Portal access is not proof of complete free reusable bulk company-register data.

2. BRS Companies Registry

Authority: Business Registration Service. Type: official Companies Registry service page. Access model: company registry services / search and extract context. Reuse note: BRS service terms. Business use: Companies Registry route for legal-entity search, official extracts and company-service context.

The BRS Companies Registry page is the cleanest public page for explaining company registry services, search context and official extracts. It is useful for readers who need to know where legal-entity records and company-service workflows begin. Its limitation is important: a service page is not the same thing as an open API, a complete downloadable register or a reusable licence for every company field.

Limitation: Controlled portal/service workflow; no open bulk-register licence confirmed.

3. BRS eCitizen portal

Authority: Business Registration Service / eCitizen. Type: official account/service portal. Access model: account workflow / company services. Reuse note: eCitizen and BRS service terms. Business use: Live company, business-name and insolvency-related service workflow context.

The BRS eCitizen portal provides live account and service workflows around companies, business names and related registry processes. Treat it as a manual or authenticated workflow layer. It can support practical guidance, but automated reuse needs source terms, account rules and lawful-use review before any production ingestion.

Limitation: Account/session controls apply; not open bulk data.

4. Kenya Revenue Authority iTax

Authority: Kenya Revenue Authority. Type: official tax/PIN portal. Access model: tax services / PIN context. Reuse note: KRA terms and tax privacy limits. Business use: Tax/PIN verification context for known entities where lawful.

KRA iTax is relevant for tax/PIN context around known entities. That makes it useful for verification and compliance workflows, but tax identifiers and taxpayer-service observations are not open company bulk data and are not contact-data permission. A CompaniesData model should store tax context separately from registry identity and mark any controlled workflow with privacy and lawful-use flags.

Limitation: Tax identifier context is controlled and not marketing-contact permission.

5. Kenya Industrial Property Institute

Authority: Kenya Industrial Property Institute. Type: official intellectual-property office. Access model: IP office portal / searches / publications. Reuse note: KIPI website and database terms. Business use: Trademark, patent and industrial-design enrichment.

KIPI is an official intellectual-property enrichment source. Trademarks, patents and other IP records can strengthen brand matching, ownership analysis and entity disambiguation. KIPI should not be interpreted as a general register because most businesses do not hold IP records. It is best joined as optional enrichment with source provenance and match confidence.

Limitation: IP layer only; not company-register coverage.

6. Capital Markets Authority Kenya licensees

Authority: Capital Markets Authority Kenya. Type: capital-market licensee register. Access model: licensee register / regulator portal. Reuse note: CMA website and register terms. Business use: Regulated capital-market entity enrichment.

The Capital Markets Authority licensee register is a high-value regulator layer for capital-market actors. It supports supervised-entity enrichment and compliance segmentation, but it covers a regulated subset. Use it to improve profiles for licensed firms without projecting that coverage onto all Kenyan businesses.

Limitation: Sector-specific scope only.

7. Central Bank of Kenya

Authority: Central Bank of Kenya. Type: central bank / financial regulator. Access model: regulator site / supervision / directories. Reuse note: CBK website terms. Business use: Banking and financial-sector context.

The Central Bank of Kenya is the financial-sector supervision context. It matters for banks and other regulated financial institutions, but the 2026-06-12 quality gate returned connection errors for browser, Googlebot and Bingbot profiles. Keep CBK as source-mapped context in this cleanup cycle and relink it only after a follow-up cycle confirms stable access.

Limitation: Sector-specific layer only.

8. Kenya Gazette

Authority: National Council for Law Reporting / Kenya Law. Type: official legal-publication route. Access model: gazette publications / legal notices. Reuse note: Kenya Law terms and official-publication rules. Business use: Legal notice and company-life publication context where relevant.

The Kenya Gazette is important for legal notices and official publications, but the 2026-06-12 quality gate returned 500 responses for Googlebot and Bingbot profiles. Keep the route source-mapped and de-linked in this cleanup cycle; when it is used later, tie evidence to specific notices, dates and publication references.

Limitation: Gazette notices are not a complete structured company register.

9. GLEIF LEI records for Kenya

Authority: global official LEI system. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions. Business use: Cross-border legal-entity identifier enrichment for Kenyan entities with LEIs.

GLEIF provides standardized LEI records through a public API. For Kenya, LEI data is useful for global identifier matching, address normalization and cross-border entity confidence. Coverage is partial and biased toward financial, larger or internationally active entities, so LEI presence should be a linked identifier, not the definition of the Kenyan company universe.

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

Practical Manual, API and Bulk Options

1. Manual BRS route

Start with Business Registration Service and the BRS Companies Registry page. Use those sources to document the official registry authority, company search context and extract/service workflow. Store the source URL, final URL, access date and observed page title in the research record.

2. eCitizen route

Use the BRS eCitizen portal as a controlled workflow route for live company and business-name services. It can help analysts understand practical access, but any automation, scraping or redistribution plan needs explicit source-terms review.

3. Tax context route

Use KRA iTax only as tax-service context for known entities. Do not frame tax/PIN workflows as open company bulk data, and do not use tax context to justify marketing-contact enrichment.

4. IP and regulator route

Use KIPI, CMA and CBK as enrichment layers. These sources can improve company profiles, sector segmentation and compliance review. Store them as optional linked sources with subset flags and match confidence.

5. Gazette route

Use Kenya Gazette only as held legal-publication context in this cycle because Googlebot and Bingbot received 500 responses. For production data, recheck access first and link specific notices to specific companies only when the notice text, date, source URL and matching rule are documented.

6. LEI API route

Use GLEIF’s public LEI API for entities with legal-entity identifiers. LEI data is strong for global matching but partial for country coverage. Keep LEI status, registration authority and update timestamp separate from BRS identity fields.

7. Held open-data/procurement/statistics route

BRS eCitizen, CBK, Kenya Gazette, Kenya Open Data, PPIP and KNBS are source-relevant. This cycle keeps them in source-risk findings because they did not pass the prior source or bot-profile gate used for the cleanup decision. Recheck them through browser QA, bot-profile QA, alternate official domains or official API/documentation routes before adding them to the clean matrix.

Held Source-Risk Findings

• BRS eCitizen portal: held and de-linked after the 2026-06-12 quality gate recorded a Bingbot Cloudflare challenge. The clean BRS authority page and BRS Companies Registry page remain the linked evidence for official registry context.
• Central Bank of Kenya: held and de-linked after the 2026-06-12 quality gate recorded browser, Googlebot and Bingbot connection errors. The 2026-06-13 cleanup artifact can be used to decide a later relink, but this cycle keeps CBK as financial-sector source-mapping context.
• Kenya Gazette: held and de-linked after the 2026-06-12 quality gate recorded HTTP 500 responses for Googlebot and Bingbot. The 2026-06-13 cleanup artifact can be used to decide a later relink, but this cycle keeps the route as legal-publication context only.
• Kenya Open Data: held in this draft after live-check result ConnectTimeout. Reason: HTTPSConnectionPool(host='opendata.go.ke', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<HTTPSConnection(host='opendata.go.ke', port=443) at 0x21ae37c4410>, 'Connection to opendata.go.ke timed out. (connect timeout=8)')). Scope: Company microdata coverage varies; dataset-level confirmation required. Keep it source-mapped, but do not link it as clean evidence until browser/TLS QA clears.
• Public Procurement Information Portal: held in this draft after live-check result SSLError. Reason: HTTPSConnectionPool(host='www.tenders.go.ke', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'www.tenders.go.ke'. (_ssl.c:1010)"))). Scope: Procurement participants are a subset, not the full company universe. Keep it source-mapped, but do not link it as clean evidence until browser/TLS QA clears.
• Kenya National Bureau of Statistics: held in this draft after live-check result SSLError. Reason: HTTPSConnectionPool(host='www.knbs.or.ke', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1010)'))). Scope: Aggregate/statistical layer, not legal-entity master data. Keep it source-mapped, but do not link it as clean evidence until browser/TLS QA clears.
• Complete free BRS bulk claim: blocked. BRS and Companies Registry pages are strong official authority evidence, but this cycle did not verify a complete free reusable bulk register or public API.
• Tax/PIN reuse claim: blocked. KRA iTax can support tax-service context for known entities, not unrestricted company bulk data or marketing use.
• Procurement universe claim: blocked until the PPIP route clears TLS/source QA, and even then procurement participants would not equal the full company population.
• Contact-use claim: blocked. Registry, tax, IP, regulator, gazette and LEI data do not create consent for unsolicited outreach, email extraction, phone lists or lead databases.

Missing-Data Gaps

• Complete free bulk register: this cycle did not verify a complete free reusable BRS company-register bulk dataset or API.
• Beneficial ownership: do not claim complete public beneficial-owner coverage from the clean source stack.
• Company events: gazette notices and registry events require specific references before record-level claims are safe.
• Procurement suppliers: PPIP remains held in this draft and, even when clean, covers procurement participants rather than every company.
• Statistics: KNBS remains held in this draft and, even when clean, would mainly provide aggregate context rather than company microdata.
• Contact fields: emails, phones, contact roles and outreach permissions are separate from official company identity.
• Source cadence: service portals, regulator pages, gazette pages and APIs may update on different cycles and need independent freshness metadata.

Recommended Data Model

• Entity table: CompaniesData id, BRS/company identifier where lawfully available, legal name, legal form, status, source URL and source date.
• Registry evidence table: BRS source page, Companies Registry service reference, eCitizen workflow note, extract type and evidence confidence.
• Tax context table: KRA/PIN context for known entities, access model, source date, privacy flag and lawful-use note.
• IP table: KIPI record identifiers, owner strings, trademark/patent classes, status, publication date and match confidence.
• Regulator table: CMA or CBK source, licence/category, regulator status, subset flag and source URL.
• Gazette table: notice date, issue/year, notice text reference, matched company, matching rule and confidence.
• LEI table: LEI, legal name, address country, registration status, managing LOU, GLEIF update timestamp and source URL.
• Compliance flags: controlled-workflow, no-open-bulk-proof, privacy-sensitive, tax-context, regulator-subset, lei-subset, held-source and contact-use-blocked.

CompaniesData Normalization and Enrichment Value

Kenya’s official source map is strong enough to justify a deep article, but the raw source stack is fragmented. CompaniesData adds value by normalizing legal names, preserving source provenance, separating registry authority from service portals, tagging controlled workflows, matching IP/regulator/LEI evidence, and packaging the result into stable country-level business data.

For English and international users, the owned route is CompaniesData.cloud. Request a CompaniesData sample for Kenya if you need a normalized dataset rather than a set of source links. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the owned route, but that contact layer remains separate from official registry reuse.

Important boundary: CompaniesData can support market research, KYB, CRM cleanup and lawful enrichment. It should not be presented as a shortcut around BRS/eCitizen source terms, tax-service privacy, regulator-subset limits or contact-data consent requirements.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Business Registration Service	Business Registration Service, Government of Kenya	official portal / registry services	BRS website and service terms	Portal access is not proof of complete free reusable bulk company-register data.
BRS Companies Registry	Business Registration Service	company registry services / search and extract context	BRS service terms	Controlled portal/service workflow; no open bulk-register licence confirmed.
BRS eCitizen portal	Business Registration Service / eCitizen	account workflow / company services	eCitizen and BRS service terms	Held after Bingbot Cloudflare challenge; account/session controls apply and this is not open bulk data.
Kenya Revenue Authority iTax	Kenya Revenue Authority	tax services / PIN context	KRA terms and tax privacy limits	Tax identifier context is controlled and not marketing-contact permission.
Kenya Industrial Property Institute	Kenya Industrial Property Institute	IP office portal / searches / publications	KIPI website and database terms	IP layer only; not company-register coverage.
Capital Markets Authority Kenya licensees	Capital Markets Authority Kenya	licensee register / regulator portal	CMA website and register terms	Sector-specific scope only.
Central Bank of Kenya	Central Bank of Kenya	regulator site / supervision / directories	CBK website terms	Sector-specific layer only.
Kenya Gazette	National Council for Law Reporting / Kenya Law	gazette publications / legal notices	Kenya Law terms and official-publication rules	Held after Googlebot/Bingbot 500 responses; gazette notices are not a complete structured company register.
GLEIF LEI records for Kenya	global official LEI system	public API	GLEIF open data licence with attribution and no-endorsement conditions	LEI coverage is partial and skewed toward financial/cross-border entities.

FAQ

What is the best first source for Kenya company data?

Start with Business Registration Service and the BRS Companies Registry page. They are the cleanest official authority and registry-service sources in this recheck.

Does Kenya have a complete free official bulk company-register API?

This cycle did not verify a complete free reusable BRS bulk register or public API. The safe claim is official registry/service access with controlled-workflow caveats.

Can the BRS eCitizen portal be scraped?

Do not assume that. It is an account and service workflow, so automation or redistribution needs source-terms, privacy and lawful-use review.

Why is Kenya Open Data held in this draft?

It timed out from this node. It remains source-relevant, but it should not be linked as clean evidence until browser or alternate-route QA clears it.

Why is the Public Procurement Information Portal held?

The tested PPIP URL failed SSL hostname validation. It remains a useful procurement lead, but publication should wait for a stable official route.

Why is KNBS held?

The KNBS page failed certificate-chain validation from this node. Statistics context is useful, but this draft keeps the link out of clean evidence.

Can KRA iTax be used as open company data?

Use KRA iTax as tax-service context for known entities. It is not a general open bulk company register or marketing-contact source.

What does KIPI add?

KIPI adds intellectual-property enrichment for entities with trademarks, patents or related records. It is useful but partial.

What do CMA and CBK add?

They add regulated-sector context for capital-market and financial entities. They should be stored with subset flags.

What does the Kenya Gazette add?

It adds legal-notice and official-publication context. Record-level use should cite specific notice dates and references.

What does GLEIF add for Kenya?

GLEIF adds public LEI records for entities that have legal-entity identifiers. It helps global matching but does not cover every Kenyan company.

Can public Kenya company data be reused commercially?

Possibly, but only under the specific source terms, access model and field-level privacy limits. Official source access is not automatic unrestricted redistribution.

Can registry data be used for cold email marketing?

No automatic permission follows from public or official access. Email, phone and contact-role data need a separate lawful basis, suppression process and contact-data compliance review.

Why use CompaniesData for Kenya?

Because source links alone do not solve normalization, deduplication, provenance, update tracking, controlled-workflow tagging, enrichment joins and delivery format.

Is Kenya publication-ready now?

This draft is ready for editorial review, but no public update was made in this cycle. Publication should happen only after final source-live checks and full indexing/crawler QA.

Official Sources

• Business Registration Service – Business Registration Service, Government of Kenya
• BRS Companies Registry – Business Registration Service
• BRS eCitizen portal – Business Registration Service / eCitizen
• Kenya Revenue Authority iTax – Kenya Revenue Authority
• Kenya Industrial Property Institute – Kenya Industrial Property Institute
• Capital Markets Authority Kenya licensees – Capital Markets Authority Kenya
• Central Bank of Kenya – Central Bank of Kenya
• Kenya Gazette – National Council for Law Reporting / Kenya Law
• GLEIF LEI records for Kenya – global official LEI system