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

Tanzania has a strong official company-data source stack, but it should be described as controlled official lookup plus official enrichment rather than a single free bulk company database. The core route is the Business Registrations and Licensing Agency (BRELA), especially the ORS public search and the BRELA Online Services portal. Around that core, NeST and PPRA add procurement activity, TRA adds taxpayer and TIN context, NBS adds Statistical Business Register and business-statistics context, Bank of Tanzania and CMSA add regulated-sector layers, DSE adds listed-company profiles, and GLEIF adds LEI matching for covered entities.

The previous CompaniesData Tanzania page was useful as a country map, but Wave 182 estimated it at about 1,841 words and flagged the newer depth requirements as missing. This article rebuilds the article as a deep reference page with methodology, coverage risk, reuse checklist, source-by-source analysis, practical manual/API/bulk options, missing data gaps, a recommended data model, CompaniesData normalization value, expanded FAQ, a source matrix, a Resource Pack and stable favicon cues.

The safe editorial claim is specific: Tanzania offers credible official routes for verification, service workflows and enrichment. The unsafe claim is that all registered companies can be downloaded freely, reused without terms, or converted into sales-prospecting contact lists. Any production dataset should preserve source provenance, access dates, access-model limits and lawful-use notes beside every normalized record.

Key Takeaways

• Primary registry source: BRELA is the official business-registration and licensing authority, with ORS and BOS providing public search and service workflows.
• Public lookup is real but scoped: BRELA ORS describes free search, but also limits public search to companies and business names registered or updated through ORS.
• Best enrichment layers: NeST/PPRA, TRA, NBS, Bank of Tanzania, CMSA, DSE and GLEIF add procurement, tax, statistics, regulator, market and identifier context.
• No complete bulk claim: this cycle did not verify a complete free official company-register bulk download or unrestricted public company API.
• Contact-data boundary: public registry, tax, procurement, officer, address, email or phone data is not permission for marketing 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 with browser, Googlebot and Bingbot-style profiles. A source is treated as clean linked evidence only when it returns a usable public response and the returned content matches expected semantics. Sources with timeouts, challenge pages, status failures, semantic mismatches or crawler profile issues remain in the research map but are held from the clean matrix until manual review.

The article is also checked against the current CompaniesData country-page standard: minimum 2,400 words, preferred 2,800 to 3,800 for commercially important jurisdictions, visible Key Takeaways, methodology, coverage and update-risk analysis, reuse checklist, source matrix, source-by-source deep dives, practical access options, missing data gaps, recommended data model, CompaniesData value, Resource Pack, official sources and FAQ.

Claims are constrained by evidence type. A registry authority page proves official authority, not necessarily open bulk reuse. A service portal proves a transaction route, not public data rights. A procurement portal proves supplier activity, not the full company universe. A tax portal can support known-entity validation, but not contact-data permission. Listed-company, regulator and LEI sources enrich subsets and should be modelled separately.

Coverage, Access and Update-Risk Analysis

Registry coverage: BRELA is the core company and business-registration authority. ORS provides the strongest public lookup evidence because it describes free search for registration number, address and current status where a company or business name was registered or updated through ORS. BOS explains online registration, company management, filing returns and information services. The National Business Portal helps users understand BRELA’s role in local companies, foreign companies and certificates. These sources are strong for verification and access workflows, but they should not be overstated as a complete public bulk file.

Tax coverage: TRA and the taxpayer portal support TIN registration, taxpayer services and tax-clearance context around known businesses. This layer can improve entity verification and compliance screening. It is also purpose-sensitive. Tax identifiers and taxpayer-service outputs should carry privacy, retention and lawful-use notes and should never be treated as permission for lead lists or outreach.

Procurement coverage: NeST and PPRA are valuable because they expose procurement workflows, tenders, awards, contract management and supplier participation. Procurement is commercially useful for public-sector sales intelligence and supplier activity, but it covers events and participants. Supplier names should be matched back to BRELA identity with confidence scoring rather than treated as standalone companies.

Statistics and regulated-sector coverage: NBS provides official business statistics and Statistical Business Register reporting context. Bank of Tanzania lists and supervises financial institutions. CMSA adds capital-market authority context. DSE covers listed-company and securities-market profiles. GLEIF provides structured LEI records for covered entities. These layers improve enrichment, market sizing and cross-border matching, but all are partial and need scope notes.

Update risk: Tanzania’s sources may change through BRELA platform migration, ORS/BOS search changes, NeST route changes, TRA portal updates, NBS report reorganizations, regulator redesigns or crawler treatment differences. A public material update should rerun source-live QA, article crawler QA, sitemap XML checks, source-logo rendering and indexing workflows after publication.

Reuse Checklist

• Preserve provenance: store source name, authority, URL, access date, profile result and route for every field.
• Separate terms: BRELA main pages, ORS search, BOS services, TRA, NeST, PPRA, NBS, BOT, CMSA, DSE and GLEIF can have different reuse rules.
• No endorsement: do not imply that any Tanzanian authority endorses a derived CompaniesData dataset.
• Bulk caution: do not claim complete free official BRELA bulk data without direct official evidence for fields, licence and update cadence.
• Privacy controls: flag officers, directors, owners, TINs, addresses, emails, phones and other natural-person fields for purpose and retention review.
• Marketing separation: registry identity, tax context and procurement visibility are not consent for cold email, phone outreach or sales-prospecting enrichment.
• Update tracking: retain last-seen status, parser version, source route and field limitations beside normalized records.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
BRELA main portal	Business Registrations and Licensing Agency	public portal / registry and IP service guidance	BRELA website, service and document terms	Authority portal and service guidance; it does not prove unrestricted full-register bulk reuse.
National e-Procurement System of Tanzania	Government of Tanzania / PPRA	public tenders, awarded contracts and e-procurement workflows	NeST and PPRA terms and procurement-publication rules	Procurement is a supplier-event subset, not the national company register.
NeST published tenders	Government of Tanzania / PPRA	public tender listings and filters	NeST tender-publication terms	Tender participants are a subset and need matching back to registry identity.
PPRA NeST service page	Public Procurement Regulatory Authority	public service description / e-registration / e-tendering / e-contract management	PPRA and NeST terms	Service description, not a downloadable company master file.
TRA taxpayer portal	Tanzania Revenue Authority	taxpayer login, TIN registration and tax-service portal	TRA portal terms and privacy rules	Taxpayer systems require purpose, privacy and retention controls.
Tanzania Revenue Authority	Tanzania Revenue Authority	tax portal / taxpayer services / compliance information	TRA terms and privacy rules	Tax context is not marketing permission and may involve protected taxpayer data.
TRA starting business guidance	Tanzania Revenue Authority	public guidance / TIN and tax-clearance workflow context	TRA guidance terms	Guidance route only; not company-register coverage or marketing permission.
Bank of Tanzania licensed institutions	Bank of Tanzania	public list of licensed/supervised institutions	Bank of Tanzania publication terms	Financial sector subset only.
Capital Markets and Securities Authority	Capital Markets and Securities Authority Tanzania	public regulator site / market and licensing context	CMSA terms and publication rules	Capital-market subset only.
Dar es Salaam Stock Exchange	Dar es Salaam Stock Exchange	market site / listed securities / trade participants / market data	DSE terms and market-data rules	Listed companies are a small, public-market subset.
DSE listed company profiles	Dar es Salaam Stock Exchange	public listed-company profiles and financial statements route	DSE issuer-page and market-data terms	Issuer pages cover only listed entities.
GLEIF LEI records for Tanzania	Global Legal Entity Identifier Foundation	public JSON API	GLEIF API terms	LEI coverage is partial and skewed toward financial or cross-border entities.

Source-by-Source Deep Dives

BRELA main portal

Authority: Business Registrations and Licensing Agency. Type: official business registration and licensing authority. Access model: public portal / registry and IP service guidance. Reuse note: BRELA website, service and document terms.

BRELA is the primary Tanzanian business-registration authority layer. Use it for registration and IP authority context, but do not present the main portal as a complete reusable bulk register.

Main limitation: Authority portal and service guidance; it does not prove unrestricted full-register bulk reuse.

National e-Procurement System of Tanzania

Authority: Government of Tanzania / PPRA. Type: official e-procurement portal. Access model: public tenders, awarded contracts and e-procurement workflows. Reuse note: NeST and PPRA terms and procurement-publication rules.

Use this source as one evidence layer with provenance, access model and limitation.

Main limitation: Procurement is a supplier-event subset, not the national company register.

NeST published tenders

Authority: Government of Tanzania / PPRA. Type: official published-tenders route. Access model: public tender listings and filters. Reuse note: NeST tender-publication terms.

NeST and PPRA provide procurement-event evidence: tenders, awards, suppliers, procuring entities and workflow context. Store procurement as events and match suppliers back to registry identity.

Main limitation: Tender participants are a subset and need matching back to registry identity.

PPRA NeST service page

Authority: Public Procurement Regulatory Authority. Type: official procurement authority service description. Access model: public service description / e-registration / e-tendering / e-contract management. Reuse note: PPRA and NeST terms.

NeST and PPRA provide procurement-event evidence: tenders, awards, suppliers, procuring entities and workflow context. Store procurement as events and match suppliers back to registry identity.

Main limitation: Service description, not a downloadable company master file.

TRA taxpayer portal

Authority: Tanzania Revenue Authority. Type: official taxpayer portal. Access model: taxpayer login, TIN registration and tax-service portal. Reuse note: TRA portal terms and privacy rules.

TRA routes support TIN and taxpayer-service context for known entities. Treat taxpayer fields as fiscal evidence with privacy, purpose and retention controls, never as marketing permission.

Main limitation: Taxpayer systems require purpose, privacy and retention controls.

Tanzania Revenue Authority

Authority: Tanzania Revenue Authority. Type: official tax authority portal. Access model: tax portal / taxpayer services / compliance information. Reuse note: TRA terms and privacy rules.

TRA routes support TIN and taxpayer-service context for known entities. Treat taxpayer fields as fiscal evidence with privacy, purpose and retention controls, never as marketing permission.

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

TRA starting business guidance

Authority: Tanzania Revenue Authority. Type: official business tax guidance. Access model: public guidance / TIN and tax-clearance workflow context. Reuse note: TRA guidance terms.

TRA routes support TIN and taxpayer-service context for known entities. Treat taxpayer fields as fiscal evidence with privacy, purpose and retention controls, never as marketing permission.

Main limitation: Guidance route only; not company-register coverage or marketing permission.

Bank of Tanzania licensed institutions

Authority: Bank of Tanzania. Type: official supervised institution list. Access model: public list of licensed/supervised institutions. Reuse note: Bank of Tanzania publication terms.

The Bank of Tanzania adds supervised financial-institution evidence. It is a high-value regulated-sector layer, but covers only entities under central-bank scope.

Main limitation: Financial sector subset only.

Capital Markets and Securities Authority

Authority: Capital Markets and Securities Authority Tanzania. Type: capital markets regulator. Access model: public regulator site / market and licensing context. Reuse note: CMSA terms and publication rules.

CMSA adds capital-market regulator context for market participants and securities supervision. It is sector-specific enrichment.

Main limitation: Capital-market subset only.

Dar es Salaam Stock Exchange

Authority: Dar es Salaam Stock Exchange. Type: regulated exchange / listed-company context. Access model: market site / listed securities / trade participants / market data. Reuse note: DSE terms and market-data rules.

DSE is the listed-company and market-data layer. It supports issuer enrichment, but listed entities are a small subset of registered businesses.

Main limitation: Listed companies are a small, public-market subset.

DSE listed company profiles

Authority: Dar es Salaam Stock Exchange. Type: listed-company profile route. Access model: public listed-company profiles and financial statements route. Reuse note: DSE issuer-page and market-data terms.

DSE is the listed-company and market-data layer. It supports issuer enrichment, but listed entities are a small subset of registered businesses.

Main limitation: Issuer pages cover only listed entities.

GLEIF LEI records for Tanzania

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

GLEIF provides structured LEI records for covered Tanzanian entities. It helps global matching; lack of an LEI is not evidence that a company does not exist.

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

Held Source-Risk Findings

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

• BRELA ORS public search: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=200 semantic=False challenge=False; bingbot status=200 semantic=False challenge=False
• BOS Portal: held. Reason: browser status=200 semantic=False challenge=False; googlebot status=200 semantic=False challenge=False; bingbot status=200 semantic=False challenge=False
• Tanzania National Business Portal register a business: held. Reason: browser status=503 semantic=False challenge=False; googlebot status=503 semantic=False challenge=False; bingbot status=503 semantic=False challenge=False
• NBS business statistics and SBR reports: held. Reason: browser status=200 semantic=False challenge=True; googlebot status=200 semantic=False challenge=True; bingbot status=200 semantic=False challenge=True
• Bank of Tanzania: held. Reason: browser status=ReadTimeout semantic=False challenge=True; googlebot status=ReadTimeout semantic=False challenge=True; bingbot status=ReadTimeout semantic=False challenge=True

Practical Manual, API and Bulk Options

Manual registry verification: start with BRELA ORS public search for known names or registration references, then use BOS or BRELA service routes for filings, returns and information services. Store the search route, search term, result date, identifier, status and source limitation. Treat detailed information services, certificates and filings as controlled workflows unless their terms clearly permit reuse.

Business-service routing: use the National Business Portal to explain the steps and agency responsibilities for local-company registration, foreign-company registration and business certificates. It is useful for practical guidance, but field-level evidence should still point to BRELA/ORS/BOS or the relevant source system.

Procurement enrichment: use NeST published tenders, awarded contracts and PPRA workflow pages for supplier and contracting-process signals. Store procurement as events: procuring entity, supplier, tender, award, contract stage, value where published, date, source URL and match confidence. Procurement records should be reconciled against registry identity before deduplication.

Tax, regulator and market enrichment: use TRA for TIN and taxpayer-service context, Bank of Tanzania for supervised financial institutions, CMSA for capital-market authority context, DSE for listed companies and GLEIF for LEI records. Keep each as an enrichment table with source-specific confidence and privacy notes.

API and bulk status: GLEIF is a clean structured API for LEI-covered entities. NeST may expose structured procurement views. This cycle did not verify a complete official open company-register bulk download, so bulk registry reuse should remain blocked until a direct BRELA or official open-data route is verified.

Missing Data Gaps

• Complete registry bulk: no complete free official BRELA company-register bulk file was verified.
• ORS scope: public ORS search has a coverage note tied to companies and business names registered or updated through ORS.
• Beneficial ownership: no complete lawful public beneficial-ownership dataset was cleared for automatic publication.
• Field-level terms: search previews, filings, information services and certificates may have different access and reuse conditions.
• Procurement matching: supplier names from tenders or awards may not align cleanly with registry identities.
• Contact enrichment: official company identity does not provide business email, phone or lead-list permission.

Recommended Data Model

A Tanzania company-data product should use a registry-first core with separate enrichment layers. The core table should include normalized legal name, registration number where public and lawful, business name or company type, status evidence, jurisdiction, source authority, source route, access date and confidence. It should not flatten BRELA, TRA, procurement and listed-company fields into one unqualified profile.

Use separate tables for ORS observations, BOS service documents, TRA taxpayer context, NeST/PPRA procurement events, NBS statistical datasets, Bank of Tanzania supervised institutions, CMSA market participants, DSE issuers and GLEIF LEIs. Each table should preserve source identifiers, source URL, update date, profile result, field limitations and reuse notes.

The matching layer should be conservative. Use official identifiers where available, then normalized names, alternative spellings, addresses, sector, procurement supplier names, regulator evidence, listed-company symbols and LEI metadata. Ambiguous matches should stay reviewable instead of being forced into a single entity.

CompaniesData Normalization and Enrichment Value

CompaniesData adds value in Tanzania by turning scattered public-source evidence into a structured, auditable business dataset. A manual researcher has to move between BRELA, ORS, BOS, TRA, NeST, PPRA, NBS, Bank of Tanzania, CMSA, DSE and GLEIF, each with different formats, field meanings, access models and reuse conditions.

A normalized CompaniesData workflow can standardize legal names, deduplicate entities, preserve provenance, match procurement activity to registry identity, link LEIs and listed-company records, flag taxpayer and natural-person sensitivity, and provide exports for market research, compliance screening, CRM hygiene and analysis. For English and international contact-data needs, the owned route is CompaniesData.cloud. Official-source company identity and compliant contact enrichment remain separate workflows.

Grouped Resource Pack

Official Sources

• BRELA main portal – Business Registrations and Licensing Agency
• National e-Procurement System of Tanzania – Government of Tanzania / PPRA
• NeST published tenders – Government of Tanzania / PPRA
• PPRA NeST service page – Public Procurement Regulatory Authority
• TRA taxpayer portal – Tanzania Revenue Authority
• Tanzania Revenue Authority – Tanzania Revenue Authority
• TRA starting business guidance – Tanzania Revenue Authority
• Bank of Tanzania licensed institutions – Bank of Tanzania
• Capital Markets and Securities Authority – Capital Markets and Securities Authority Tanzania
• Dar es Salaam Stock Exchange – Dar es Salaam Stock Exchange
• DSE listed company profiles – Dar es Salaam Stock Exchange
• GLEIF LEI records for Tanzania – Global Legal Entity Identifier Foundation

FAQ

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

Start with BRELA. Use ORS for public lookup where available, BOS for online service workflows, and BRELA/National Business Portal pages for registration route context.

Does Tanzania have a complete free official company bulk download?

Not verified in this cycle. Public lookup and service workflows exist, but search pages and service portals do not automatically create a complete open bulk API.

Can NeST procurement data replace registry data?

No. NeST and PPRA are valuable for tenders, awards and supplier activity, but procurement participants are a subset. Match suppliers back to BRELA identity where possible.

Can TRA taxpayer data be used for outreach?

No. TRA data is fiscal-context evidence and requires purpose, privacy and source-terms controls. It is not permission for cold email, phone calls or lead lists.

Why include NBS, BOT, CMSA, DSE and GLEIF?

They add statistics, supervised-financial-institution, capital-market, listed-company and global identifier context. Each layer enriches the profile but remains partial.

How does CompaniesData help?

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