Open Company Data in Cote d’Ivoire: Official Sources, APIs and Reuse Rights

Cote d’Ivoire has enough official and high-quality public evidence for a serious open company data reference article, but it should not be presented as a simple free bulk register. The cleanest public source stack starts with the official IDU directory, adds business-formalities context through GUCE, uses the national open-data portal for dataset discovery, relies on procurement and legal-publication sources for enrichment, and then adds OAPI, GLEIF and EITI where those sources match the use case.

The important editorial boundary is that several historically relevant routes are not clean enough to link as publication evidence from this environment. OHADA/RCCM, Tribunal RCCM, DGI, INS, CEPICI and BRVM remain source-mapped, but the current draft keeps them in a held-source section because of timeouts, TLS validation failures, access markers or redirect behaviour. That approach gives readers the commercial map without overstating source reliability.

This draft is written as a deep refresh candidate for the existing CompaniesData country article. It keeps the canonical title and slug, raises the content above the current depth bar, and uses only publication-safe or conditional-public links from the latest source recheck. No WordPress update or indexing submission is made by this draft artifact.

Key Takeaways

• Best first source: use the Annuaire IDU as the official identifier lookup layer, then reconcile with formalities, procurement, legal publication and enrichment sources.
• No complete bulk claim: no complete free official RCCM or company-register bulk API was confirmed in this recheck.
• Open-data value: data.gouv.ci is useful for dataset discovery, but every dataset still needs its own licence, scope and freshness review.
• Commercial enrichment: procurement, OAPI, GLEIF and EITI can improve matching, sector context and compliance review, but they are partial layers.
• Contact-data boundary: registry, tax, procurement, officer, beneficial-owner, phone or email fields are not sales-prospecting permission.

Editorial Methodology

This article uses a source-first methodology. Each source is classified by authority, access model, reuse rights, business value and limitation. Official sources are preferred over private aggregators. High-quality international sources such as GLEIF and EITI are used only where they add verifiable reference data or transparency context. Sources that returned hard failures, unstable TLS, access-control markers or bot-sensitive behaviour are not linked in the main evidence matrix even when they remain relevant for manual research.

The recheck date is 2026-06-09T13:00:11Z. The working assumption is conservative: a public HTTP 200 alone is not enough. A source must be stable enough for publication, have a clear authority role, and support the exact claim made in the article. For Cote d’Ivoire, this means that IDU can be called an official identifier lookup, GUCE can be called a business-formalities context source, procurement can be called a supplier/award enrichment source, and GLEIF can be called a global LEI subset. It does not mean that a complete national company master file is freely reusable.

The article also separates company identity, compliance context and marketing/contact use. A field that is visible in a public or official workflow may still be personal data, restricted administrative data, login-protected data, non-reusable data or data that lacks consent for outreach. CompaniesData.cloud can normalize and enrich company records, but the source matrix must preserve these provenance and lawful-use boundaries.

Coverage, Access and Update-Risk Analysis

Cote d’Ivoire’s company-data coverage is fragmented across identifier lookup, formalities services, open-data discovery, procurement, legal publications, IP, LEI and sector transparency. That is commercially useful because multiple independent sources can confirm different parts of a business record. It also creates update risk because no single verified open bulk feed was found for the full population of companies.

Coverage risk: IDU and formalities sources are stronger for entity identity and workflow context than for exhaustive downloadable coverage. Procurement only covers suppliers and awards. OAPI covers entities with IP records. GLEIF covers LEI-holding entities. EITI covers extractive-sector transparency context. A practical dataset should therefore label every field with source provenance and avoid representing the merged result as a government-provided master register.

Access risk: some important routes remain browser/manual QA candidates. OHADA RCCM timed out from this node, the Tribunal RCCM route failed TLS validation, CEPICI redirected through a service layer, DGI showed an access marker, and INS/BRVM had TLS issues. Those routes may be usable by a human in a browser or from another network, but they are not clean automated publication evidence today.

Update risk: open-data catalogues and procurement portals can change schemas, URLs and update cadence. Legal publications are durable but not live status records. GLEIF has a mature API and bulk model, but it covers only LEI entities. For production use, a refresh policy should monitor source availability, last-observed timestamps, schema drift and the gap between official publication dates and CompaniesData normalization dates.

Reuse Checklist

• Check source authority: prefer IDU, GUCE, data.gouv.ci, procurement, SGG, OAPI, GLEIF and EITI over unsourced mirrors.
• Record licence or terms: capture dataset-level terms for open-data entries and portal/service terms for non-download sources.
• Preserve provenance: keep source URL, access date, extraction method, matched identifier and confidence score.
• Respect no-endorsement language: do not imply that an official source endorses a commercial dataset.
• Separate public data from marketing use: do not treat identifiers, procurement participation, officer names or tax context as outreach consent.
• Avoid unsupported completeness claims: say partial, source-mapped or enrichment layer unless a complete official bulk source is verified.
• Hold unstable routes: do not link OHADA/RCCM, Tribunal RCCM, DGI, INS or BRVM as clean evidence until route QA clears.

Source Matrix

Source	Type	Authority	Access model	Reuse note	Boundary
Annuaire IDU Cote d'Ivoire	official business identifier lookup	identifier/tax / official registry context	public search	portal terms / official-use caveats	Identifier layer; not a full registry bulk dataset.
GUCE CEPICI page	official business formalities context	official government	service portal	GUCE terms	Service layer only; not open bulk register.
Cote d'Ivoire Open Data Portal	official open data	official open data	data catalogue	dataset-specific terms	Company microdata coverage varies by dataset.
Cote d'Ivoire Open Data Datasets	official open-data catalogue	official open data	catalogue / dataset search	dataset-specific terms	No complete company-register bulk dataset confirmed in this recheck.
Cote d'Ivoire Public Procurement	official procurement	official procurement	procurement portal	procurement portal terms	Procurement subset only.
Secretariat General du Gouvernement Cote d'Ivoire	official legal publication	legal publication / gazette	legal texts / journal officiel	SGG terms	Legal-publication layer, not current registry status.
e-Impots Cote d'Ivoire	tax e-services portal	identifier/tax	e-services portal	tax privacy and service terms	Service layer only; not marketing permission and not a company master dataset.
OAPI	regional IP office	official IP	search / publications	OAPI terms	Regional IP layer only.
GLEIF Cote d'Ivoire LEI records API	global legal entity identifier reference data	high-quality global LEI authority	API / bulk reference data	GLEIF open data licence with attribution and no-endorsement conditions	LEI subset only; not a national company register and not a marketing-contact source.
EITI Cote d'Ivoire country page	high-quality beneficial-ownership and extractive-sector transparency context	high-quality international transparency source	public report / country profile	EITI website terms	Context only; BO information must not be treated as open marketing/contact data.

Source logos are decorative favicon cues only. The evidence remains the official URL, source owner, access model and reuse note.

Source-by-Source Deep Dives

1. Annuaire IDU Cote d'Ivoire

Authority: identifier/tax / official registry context. Type: official business identifier lookup. Access: public search. Reuse: portal terms / official-use caveats. Business use: Business identifier verification cross-checked with official administrations.. Boundary: Identifier layer; not a full registry bulk dataset.

The IDU directory is the cleanest first verification layer because it is tied to the national business identifier workflow. It is useful when an analyst needs to reconcile a local name, identifier and official administrative footprint before moving into enrichment sources. It should not be described as a complete company-register bulk feed: the safe claim is narrower, namely that IDU is an official identifier lookup and business-directory context layer. In a production data model, IDU evidence belongs in provenance fields with the lookup date, matched identifier, normalized legal name and confidence score, not as proof that every active company has been captured in a reusable master file.

2. GUCE CEPICI page

Authority: official government. Type: official business formalities context. Access: service portal. Reuse: GUCE terms. Business use: Single-window and CEPICI service context.. Boundary: Service layer only; not open bulk register.

The GUCE CEPICI page helps explain the business-formalities route and the single-window context around company creation. It is a service and procedure source rather than a downloadable register. Editorially, it supports the article’s explanation of how local company formation, investor services and administrative workflows connect to registry research. For data operations, it is best used to define field expectations, process boundaries and manual due-diligence routes. It should not be scraped or marketed as an open list of companies, officers or contacts.

3. Cote d'Ivoire Open Data Portal

Authority: official open data. Type: official open data. Access: data catalogue. Reuse: dataset-specific terms. Business use: Government open-data discovery.. Boundary: Company microdata coverage varies by dataset.

The national open-data portal is the discovery layer for public datasets. Its value is not that it proves a complete company database exists, but that it gives a reusable catalogue entry point for datasets that may support entity enrichment, procurement, geography, sector context or administrative transparency. Each dataset still needs its own licence and freshness review. In a CompaniesData workflow, portal records are treated as dataset-level evidence with publisher, update date, licence note and schema mapping, while company-level claims are made only when a dataset actually exposes company or supplier entities.

4. Cote d'Ivoire Open Data Datasets

Authority: official open data. Type: official open-data catalogue. Access: catalogue / dataset search. Reuse: dataset-specific terms. Business use: Dataset-level discovery for reusable public-sector data.. Boundary: No complete company-register bulk dataset confirmed in this recheck.

The national open-data portal is the discovery layer for public datasets. Its value is not that it proves a complete company database exists, but that it gives a reusable catalogue entry point for datasets that may support entity enrichment, procurement, geography, sector context or administrative transparency. Each dataset still needs its own licence and freshness review. In a CompaniesData workflow, portal records are treated as dataset-level evidence with publisher, update date, licence note and schema mapping, while company-level claims are made only when a dataset actually exposes company or supplier entities.

5. Cote d'Ivoire Public Procurement

Authority: official procurement. Type: official procurement. Access: procurement portal. Reuse: procurement portal terms. Business use: Tender, supplier and award enrichment.. Boundary: Procurement subset only.

The procurement portal is commercially useful because award notices and supplier references can confirm that an entity participates in public-sector markets. It is not a general population register. Procurement data should be modelled as transactional evidence: buyer, supplier, tender, award, date, amount where available, procurement identifier and source URL. Reuse must respect the portal terms and the fact that tender participation is not consent for sales outreach. It is a strong enrichment layer when combined with IDU or registry evidence.

6. Secretariat General du Gouvernement Cote d'Ivoire

Authority: legal publication / gazette. Type: official legal publication. Access: legal texts / journal officiel. Reuse: SGG terms. Business use: Legal and company-law context.. Boundary: Legal-publication layer, not current registry status.

The Secretariat General government site is a legal-publication layer. It helps validate company-law context, decrees, official notices and legal framework changes, but it does not provide live company status. This type of source is useful in a reference article because it explains why registry records, tax identifiers and procurement evidence need to be interpreted inside Ivorian and OHADA legal context. In a data model, legal publication evidence should be linked to laws, notices and effective dates rather than merged into a company master record without interpretation.

7. e-Impots Cote d'Ivoire

Authority: identifier/tax. Type: tax e-services portal. Access: e-services portal. Reuse: tax privacy and service terms. Business use: Tax services and compliance workflow context.. Boundary: Service layer only; not marketing permission and not a company master dataset.

The e-Impots route is an official tax-services context source. It can help explain identifier and compliance workflows, but tax-service access is sensitive and is not a public marketing-data permission layer. The article therefore treats it as conditional context, not as a clean source for extracting contact lists, taxpayer universes or private compliance information. Any operational use should separate public company identity data from tax, login, declaration and payment data.

8. OAPI

Authority: official IP. Type: regional IP office. Access: search / publications. Reuse: OAPI terms. Business use: Trademark, patent and IP enrichment.. Boundary: Regional IP layer only.

OAPI is the regional intellectual-property layer. It can enrich company research when a business owns marks, patents or other IP records, especially across OHADA and West African markets. It is a partial source, not a company register. IP records help with disambiguation, brand matching and risk review, but the absence of an OAPI record does not mean an entity is inactive. The safe modelling choice is to store IP evidence as a separate enrichment table linked by normalized names, applicants, addresses and dates.

9. GLEIF Cote d'Ivoire LEI records API

Authority: high-quality global LEI authority. Type: global legal entity identifier reference data. Access: API / bulk reference data. Reuse: GLEIF open data licence with attribution and no-endorsement conditions. Business use: Cross-border identifier enrichment for Ivorian entities that have LEIs.. Boundary: LEI subset only; not a national company register and not a marketing-contact source.

GLEIF is a high-quality global reference dataset for Legal Entity Identifiers. It is valuable because the API and bulk framework are explicit and because LEI records carry standardized names, addresses, registration authority links and status fields. For Cote d’Ivoire, it is only a subset of entities that need or have LEIs, usually tied to financial-market, cross-border or regulated activities. It should be labelled as open LEI reference data with attribution and no-endorsement caveats, not as the national registry.

10. EITI Cote d'Ivoire country page

Authority: high-quality international transparency source. Type: high-quality beneficial-ownership and extractive-sector transparency context. Access: public report / country profile. Reuse: EITI website terms. Business use: Context for extractive-sector transparency and beneficial-ownership limitations.. Boundary: Context only; BO information must not be treated as open marketing/contact data.

EITI is useful for extractive-sector transparency and beneficial-ownership context, especially when company data research touches mining, oil, gas or state-revenue questions. It is not a generic contact-data source and it should not be used to infer permission for outreach. In this draft it is kept as high-quality public context with strict privacy and lawful-use caveats. Any beneficial-ownership discussion must remain bounded by the exact public record, the sector scope and the applicable legal basis.

Grouped Resource Pack

Practical Manual, API and Bulk Options

Manual verification workflow

1. Start with the company name, local spelling variants and any known IDU, RCCM or tax identifiers.
2. Check IDU for official identifier context and normalize legal form, spelling and address evidence.
3. Use GUCE and business-formalities context to understand registration workflows and source boundaries.
4. Search open-data and procurement sources for supplier, tender, award, geography or sector evidence.
5. Add OAPI, GLEIF and EITI only where the entity appears in those specialized layers.
6. Store every match with source URL, access date, method and confidence rather than flattening all evidence into a single uncontrolled field.

API and bulk workflow

The most reliable API-like evidence in this source map is the GLEIF LEI API for the Cote d’Ivoire country filter. It is valuable for standardized LEI records, but it is not a national registry. The open-data portal may expose dataset-specific downloads or APIs depending on the catalogue entry, but this recheck did not confirm a complete company-register bulk file. Procurement and legal-publication routes should be treated as portal or document workflows unless a stable official feed is verified.

Paid or controlled extracts

Some official registry or RCCM workflows may require manual search, paid extracts, browser sessions or terms acceptance. That can still be legitimate for due diligence, but it is different from open-data reuse. CompaniesData should record paid/controlled evidence separately and should not blend it with open licence datasets without preserving the legal basis, extraction date and downstream-use limitation.

Missing-Data Gaps

• Complete registry bulk: no complete free official RCCM/company-register bulk API was confirmed.
• Current status coverage: legal publications and procurement records are not substitutes for current register status.
• Beneficial ownership: EITI context is sector-specific and sensitive; it is not a general BO download or marketing source.
• Officer and contact fields: public visibility does not create consent for cold email, phone lists or sales-prospecting enrichment.
• Route stability: held RCCM, DGI, INS and BRVM routes need browser/manual QA before they can support public links.
• Freshness: dataset update cadence varies by source and must be checked at dataset or portal level.

Recommended Data Model

A practical Cote d’Ivoire company dataset should be provenance-heavy. Recommended core fields include normalized legal name, local name variants, country, jurisdiction, legal form, IDU or other official identifiers where observed, RCCM reference where lawfully obtained, address components, activity/sector fields, status when supported by the source, source URL, source authority, access date and confidence score. Enrichment tables should be separate for procurement awards, IP records, LEI records, legal publications and transparency records.

Identity table: store stable company names, identifiers, legal form, jurisdiction and source confidence. Source evidence table: store each source observation with timestamp, URL, access method, licence note and extraction limitations. Enrichment tables: store procurement, OAPI, GLEIF and EITI records as separate observations linked back to the entity. Compliance flags: store privacy, beneficial-ownership, tax, marketing-contact and source-terms cautions as explicit fields.

This design prevents a common data-quality error: treating every public record as if it had the same authority, freshness and reuse right. It also makes downstream exports safer because users can filter by source type and lawful-use boundary.

CompaniesData Normalization and Enrichment Value

CompaniesData.cloud adds value where official sources are useful but fragmented. A raw analyst workflow has to move between IDU, GUCE, data.gouv.ci, procurement, legal publications, OAPI, GLEIF and EITI. A normalized workflow turns that into a consistent entity graph with deduplicated names, country codes, source provenance, update tracking, matched identifiers, enrichment layers and clear reuse cautions.

For Cote d’Ivoire, the strongest CompaniesData value proposition is not “we found a single secret list.” It is “we normalize official and high-quality public evidence without hiding the boundaries.” That matters for commercial research, market mapping, procurement intelligence, supplier verification, financial services onboarding, sanctions/compliance screening and sector analysis. It also matters for avoiding misuse: public company data is not automatically permission to buy or sell private contact lists.

Request a CompaniesData sample for Cote d’Ivoire if you need a structured dataset with provenance instead of a manual list of portals.

Held Source-Risk Findings

The following sources remain important for research, but they are not linked as clean evidence in the main article until route reliability, terms or manual browser QA clears. This is a publication-quality control, not a claim that the sources are unofficial.

• OHADA RCCM portal: Route timed out in this recheck; keep as manual/browser QA only. Live-check status: ReadTimeout. Keep source-mapped, but do not link as clean evidence until route QA clears.
• Tribunal de Commerce Abidjan RCCM: TLS validation failed from this node; keep as manual/browser QA only. Live-check status: SSLError. Keep source-mapped, but do not link as clean evidence until route QA clears.
• CEPICI: JS redirect/service layer; use GUCE as cleaner linked evidence unless browser QA clears CEPICI. Live-check status: 307. Keep source-mapped, but do not link as clean evidence until route QA clears.
• Direction Generale des Impots Cote d'Ivoire: Bot/access marker in this recheck; do not use as clean public evidence. Live-check status: 200. Keep source-mapped, but do not link as clean evidence until route QA clears.
• Institut National de la Statistique Cote d'Ivoire: TLS validation failed from this node; keep as manual/browser QA only. Live-check status: SSLError. Keep source-mapped, but do not link as clean evidence until route QA clears.
• BRVM: TLS validation failed from this node; listed-company subset only. Live-check status: SSLError. Keep source-mapped, but do not link as clean evidence until route QA clears.

Allowed and Blocked Claims

Allowed Claims

• Allowed: Use IDU, GUCE/CEPICI context, data.gouv.ci, public procurement, legal-publication, OAPI, GLEIF and EITI as source layers for verification and enrichment.
• Allowed: Describe IDU as an official identifier/business-directory layer, not a complete company-register bulk dataset.
• Allowed: Use procurement, LEI, IP, legal-publication and transparency sources as partial enrichment layers only.
• Allowed: State that beneficial-ownership context is sensitive and not equivalent to marketing/contact permission.

Blocked Claims

• Blocked: Do not claim Cote d'Ivoire has a complete free official RCCM/company-register bulk API.
• Blocked: Do not publish Tribunal/RCCM, OHADA RCCM, DGI, INS or BRVM links as clean evidence until route QA clears SSL/timeouts/challenges.
• Blocked: Do not treat tax, IDU, procurement, officer, beneficial-owner, phone or email fields as sales-prospecting permission.
• Blocked: Do not recommend third-party contact-data competitors for Ivorian lead lists.

Remaining Blockers

• Blocker: The current public article is below the new 2,400-word depth bar and needs a deep rewrite before it can be considered 'perfect'.
• Blocker: RCCM/OHADA route stability is not clean from this node: OHADA timed out and the Tribunal RCCM route failed TLS validation.
• Blocker: DGI displayed an access/bot marker; INS and BRVM failed TLS validation from this node.
• Blocker: No complete free official RCCM bulk/API source was confirmed.
• Blocker: Beneficial-ownership material should stay as high-level transparency context unless lawful public access and privacy limits are cleared.

FAQ

Is there one free official bulk company database for Cote d’Ivoire?

No complete free official RCCM or company-register bulk API was confirmed in this recheck. The safe answer is that Cote d’Ivoire has useful official and high-quality public source layers, but completeness and bulk reuse must be proven source by source.

What is the best starting point for company verification?

The IDU directory is the best first public verification layer because it gives official identifier context. It should be combined with formalities, open-data, procurement, legal-publication and enrichment sources when a use case needs more than identity confirmation.

Can procurement records be used as a company database?

No. Procurement records are useful for supplier and award enrichment, but they cover only entities that appear in procurement workflows and they carry portal-specific reuse limits.

Does GLEIF provide Cote d’Ivoire company data?

GLEIF provides LEI reference records for entities with Legal Entity Identifiers. It is standardized and API-accessible, but it is a subset, not the national register.

Can public company records be used for sales emails or phone lists?

Not by default. Registry, identifier, tax, procurement, officer, beneficial-owner, phone or email data can have privacy and lawful-use limits. For international company-data work, route requests through CompaniesData.cloud and preserve provenance and consent boundaries.

Why are some official sources held out of the public links?

Publication-safe links need stable live access from the QA environment. OHADA/RCCM, Tribunal RCCM, DGI, INS, CEPICI and BRVM remain researched, but this draft does not use them as clean linked evidence because of timeout, TLS, redirect or access-marker issues observed in the latest recheck.

Official Sources

• Annuaire IDU Cote d'Ivoire – identifier/tax / official registry context
• GUCE CEPICI page – official government
• Cote d'Ivoire Open Data Portal – official open data
• Cote d'Ivoire Open Data Datasets – official open data
• Cote d'Ivoire Public Procurement – official procurement
• Secretariat General du Gouvernement Cote d'Ivoire – legal publication / gazette
• e-Impots Cote d'Ivoire – identifier/tax
• OAPI – official IP
• GLEIF Cote d'Ivoire LEI records API – high-quality global LEI authority
• EITI Cote d'Ivoire country page – high-quality international transparency source