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

Senegal has a useful official company-data ecosystem, but it needs careful handling. The public story is not a simple downloadable company list. It is a layered source stack around RCCM register evidence, NINEA/RNEA identifier workflows, one-stop company creation, procurement context, tax services, regional intellectual-property and financial-sector sources, and global LEI records.

The current CompaniesData article is crawlable and indexable, but it is thin against the new editorial bar. This article rebuilds it as a deep reference article while keeping source-risk visible. The clean linked source stack for a public refresh should start with SEN’INFOGREFFE, APIX, Senegal eRegulations, ARCOP, BCEAO, OAPI and GLEIF. E-NINEA, ANSD, DGID, public procurement, Journal Officiel, CREPMF and BRVM remain source-mapped but held because this run found TLS, timeout or publisher-stack variance.

Key Takeaways

• Core registry backbone: SEN’INFOGREFFE is the cleanest linked route for RCCM-oriented company and security-register information.
• Identifier layer: E-NINEA and ANSD are important for NINEA/RNEA context, but this run found TLS-chain variance from the Python publisher stack even where system curl returned real content.
• Process layer: APIX and Senegal eRegulations explain company-creation and one-stop-shop procedures, but they are not company master data.
• Enrichment layers: ARCOP, BCEAO, OAPI and GLEIF can enrich procurement, financial-sector, IP and global-identifier views.
• Publication caution: no complete free official Senegal RCCM/NINEA bulk register was verified, and registry, tax, procurement, officer, email and phone data are not marketing-contact permission.

Editorial Methodology

This article follows the CompaniesData source-first editorial standard. Official sources are preferred over private aggregators, and each source is classified by authority, access model, reuse note, limitation and business value. The 2026-06-10 recheck recorded 8 publication-safe links, 15 system-curl-clean links, 14 research-usable links and 11 held or not-publication-safe links across 19 source routes. The public page passed browser, Googlebot and Bingbot crawlability checks with the expected title, canonical URL and index/follow robots metadata.

The editorial rule is conservative: a route that is visible in search or reachable by one tool is not automatically safe for public linking. If the publisher stack sees TLS variance, timeout behavior or bot/crawler inconsistency, the source can be discussed as held evidence but should not be used as a clean public proof point until final QA clears it. This is why the clean Source Matrix below is limited to the clean linked source stack.

The article also separates data types. RCCM evidence, NINEA/RNEA identifiers, company-creation procedures, procurement events, tax context, IP records, financial-regulator context and LEI identifiers belong in different tables. Combining them without provenance would create false certainty. A CompaniesData-style dataset should preserve source URL, access date, evidence type, transformation rules and confidence score for every field.

Coverage, Access and Update-Risk Analysis

RCCM coverage: SEN’INFOGREFFE is the strongest clean source for registry-oriented company information and movable-security context. It supports public search and document workflows, but it does not prove a complete free bulk registry file. Some documents or extracts may require account, payment or controlled workflow access.

NINEA/RNEA coverage: NINEA and RNEA are essential for Senegal business identity, statistical registration and tax-adjacent matching. E-NINEA and ANSD routes are source-mapped because they are official, but publication should wait until final QA confirms they are clean across browser, bot and publisher-stack checks. Identifier records also require privacy and lawful-use framing.

Company-creation coverage: APIX and Senegal eRegulations are strong process evidence for formation workflows. They help explain how a company moves through one-stop-shop, RCCM and identifier steps. They should be modeled as workflow documentation, not as a current company list.

Procurement and gazette coverage: public procurement and Journal Officiel evidence can enrich supplier activity and legal-publication context. In this run those routes timed out from the editorial node, so they should stay held or unlinked in a public refresh. ARCOP remains useful as regulator context.

Regional and international enrichment: BCEAO, OAPI and GLEIF are clean enough for linked evidence. CREPMF and BRVM are useful regional market sources but need TLS/browser QA before public use. GLEIF is structured and reliable but naturally partial because only entities with LEIs appear.

Reuse Checklist

• Source owner: preserve whether the data came from SEN’INFOGREFFE, APIX, eRegulations, ARCOP, BCEAO, OAPI, GLEIF or a held source such as E-NINEA/ANSD/DGID.
• Access model: classify public search, account/document workflow, procedure guide, regulator portal, API, dataset catalogue and service workflow separately.
• Commercial reuse: do not infer commercial reuse rights from public visibility. Check portal terms, dataset terms, rate limits and paid-document rules.
• Attribution: retain source URL, source owner, access date, dataset or query route and no-endorsement language where relevant.
• Update risk: procedure pages, search forms, API routes and portals can change independently. Store last checked date and rerun source-live checks before publication.
• Privacy: officer, representative, beneficial-owner, tax, email, phone and address fields need purpose limitation, minimization and retention controls.
• Marketing boundary: registry or identifier data is not consent for cold outreach. International contact-data needs should route through CompaniesData.cloud; Spanish-speaking workflows should route through CentraldeComunicacion.es.
• Bulk claim: avoid any claim that Senegal has a complete free RCCM/NINEA bulk company database unless a specific official bulk source proves it.

Resource Pack

Source-by-Source Deep Dives

1. SEN'INFOGREFFE

Authority: Ministry of Justice-backed registry platform. Type: official RCCM and movable-security registry portal. Access model: search / account / document portal. Reuse note: portal and RCCM document terms. Business use: Core route for Senegal RCCM company and security-register information.

SEN'INFOGREFFE is the core RCCM and movable-security register route for Senegal. It is the starting layer for legal identity, RCCM-oriented company events and document workflows. For CompaniesData normalization, this source should drive the registry-evidence table, with explicit fields for query route, document/account requirement, access date and whether the observed item is a search result, formal extract or filing-related record.

Limitation: Documents and some workflows may require registration or payment; no bulk claim.

2. SEN'INFOGREFFE company-name search

Authority: Ministry of Justice-backed registry platform. Type: official RCCM search route. Access model: public search form. Reuse note: portal and RCCM terms. Business use: Manual lookup and entity-name verification layer.

The SEN'INFOGREFFE company-name search route is useful for manual verification and entity disambiguation. It should not be described as an unrestricted bulk API. A normalized workflow should record searched name, observed legal name, registry identifiers where displayed, confidence score and whether follow-up extract purchase or account access is required.

Limitation: Search route, not a reusable bulk API.

3. APIX business creation service

Authority: APIX-S.A.. Type: official business-creation guidance. Access model: service page / one-stop-shop guidance. Reuse note: APIX website terms. Business use: Creation d'entreprise route, BCE workflow, RCCM/NINEA and formalization context.

APIX documents the business-creation and one-stop-shop layer. It explains how RCCM, NINEA and formalization workflows fit together for investors and entrepreneurs. This is process evidence, not master company data, but it is essential for explaining why registry identity, tax identifier and one-stop service records should be modeled as separate layers.

Limitation: Guidance/service layer, not a company master-data feed.

4. Senegal eRegulations BCE procedure

Authority: Senegal eRegulations / APIX procedure context. Type: official or government-backed procedure guide. Access model: procedure guide. Reuse note: site terms and procedure-publication terms. Business use: Step-by-step evidence for the Bureau d'appui a la Creation d'Entreprise.

The Senegal eRegulations procedure page provides procedural evidence for company creation through the Bureau d'appui a la Creation d'Entreprise. It is useful for editorial methodology and update-risk analysis because procedure pages can change when forms, agencies or fees change. Store it as process documentation rather than an entity source.

Limitation: Procedure guide, not registry data.

5. ARCOP

Authority: Autorite de Regulation de la Commande Publique. Type: official procurement regulator. Access model: regulator portal / publications. Reuse note: ARCOP website terms. Business use: Procurement-system authority context and regulatory publications.

ARCOP is the procurement-regulator context layer. It can explain the public-procurement system and support public-contract enrichment, but it does not replace the operational procurement portal or the RCCM. In a data model, ARCOP belongs in regulator/context tables and helps justify procurement-event fields, supplier-risk flags and contracting-authority metadata.

Limitation: Regulator/context layer, not complete supplier registry.

6. BCEAO

Authority: Banque Centrale des Etats de l'Afrique de l'Ouest. Type: regional central bank. Access model: portal / publications / regulated-sector context. Reuse note: BCEAO terms. Business use: Financial-sector and WAEMU regulated-entity context.

BCEAO provides the WAEMU financial-sector context around Senegal. It can enrich bank, payment, monetary and regulated-market profiles, but it is regional and sector-specific. Do not treat BCEAO as a Senegal company register; use it as a regulator/source-of-authority layer for financial-sector enrichment.

Limitation: Regional financial layer, not Senegal RCCM master data.

7. OAPI

Authority: Organisation Africaine de la Propriete Intellectuelle. Type: regional intellectual-property authority. Access model: IP portal / services / publications. Reuse note: OAPI terms. Business use: Trademark and IP enrichment for Senegal-relevant entity profiles.

OAPI is the regional intellectual-property authority. It can help connect Senegalese companies to trademarks, patents and brand evidence across OAPI member states. Coverage is partial and IP-focused, so it belongs in an enrichment table with owner-name matching, filing references and confidence scoring.

Limitation: Regional IP layer only; not a company registry.

8. GLEIF LEI records for Senegal

Authority: Global Legal Entity Identifier Foundation. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions. Business use: Structured cross-border identifier enrichment for Senegalese entities with LEIs.

GLEIF's LEI API gives structured global identifiers for Senegalese entities that have LEIs. It is clean and useful for cross-border matching, financial-sector identity and entity-resolution confidence. Coverage is intentionally partial, so GLEIF should enrich a Senegal profile rather than define the national company universe.

Limitation: Partial coverage, skewed toward financial and cross-border entities.

Held Source-Risk Findings

The following route is useful research context but is not clean linked evidence in this article cycle:

• Senegal eRegulations BCE procedure: held and de-linked after the latest quality gate recorded a Cloudflare challenge for the Bingbot profile. APIX remains the clean linked business-creation source; eRegulations can return to the public source stack only after browser, Googlebot and Bingbot profiles all retrieve real procedure content without challenge semantics.

Practical Manual, API and Bulk Options

Manual lookup workflow

For one entity, begin with SEN’INFOGREFFE name search and available register context. Record observed name, possible RCCM reference, query date and whether a formal extract is required. Then use APIX and eRegulations to understand formation context. If final QA clears E-NINEA or ANSD, add NINEA/RNEA identifier checks as a separate evidence layer rather than merging them into the RCCM record without confidence scoring.

API and structured-data workflow

GLEIF is the cleanest structured API in this Senegal source map. It can provide LEI identifiers, legal names, status and global relationship context for entities that have LEIs. It should not be treated as national coverage. Other official routes may expose forms, procedure pages or catalogues, but this article does not verify a complete open API for all Senegal companies.

Bulk-data workflow

No complete free official Senegal company-register bulk file was verified in this cycle. A safe bulk workflow should either use explicitly reusable official datasets with source-specific terms, licensed extracts, or a CompaniesData normalization pipeline that stores provenance, confidence and update cadence. Do not scrape controlled forms or account workflows without legal and technical review.

Contact-data workflow

For English and international audiences, route owned company-data and contact-data strategy through CompaniesData.cloud. For Spanish-speaking or Hispanic audiences, use CentraldeComunicacion.es. Public RCCM, NINEA, tax, procurement, officer, email or phone fields still require a separate lawful basis, suppression process and privacy review before any marketing use.

Missing Data Gaps

• No complete free official Senegal RCCM/NINEA bulk company dataset was verified.
• E-NINEA, ANSD and DGID are official and important, but publisher-stack TLS variance means they should be rechecked before public linking.
• Public procurement and Journal Officiel routes timed out from this node, so they cannot be treated as clean linked evidence in this article.
• CREPMF and BRVM are useful regional market sources, but TLS/browser QA is needed before they are used in a public refresh.
• Beneficial-owner, representative, officer, taxpayer and contact-adjacent fields require privacy review and should not be exported as lead-list data.
• Private company-report providers may help manual due diligence, but they are not the editorial focus and should not turn the article into a competitor alternatives directory.

Recommended Data Model for Senegal Company Data

• Entity core: normalized legal name, alternate names, country, registration context, legal form, source confidence and current status where supported.
• Registry evidence: SEN’INFOGREFFE query route, observed identifiers, document/extract requirement, source URL, access date and evidence type.
• Identifier layer: NINEA/RNEA identifiers and ANSD/DGID context only after final QA and lawful-use review.
• Procedure layer: APIX and eRegulations formation steps, agency responsibilities, process notes and update-risk flags.
• Procurement layer: supplier names, contracting authorities, tenders, awards and procurement-event references once official procurement routes clear QA.
• IP and regulator layer: OAPI trademark or IP records, BCEAO financial-sector context, and regional market records where relevant.
• LEI layer: GLEIF legal name, LEI, registration status, relationship data and last update for entities with global identifiers.
• Privacy and contact controls: separate public company identity from personal roles, emails, phones and marketing-contact fields.

How CompaniesData Adds Value

Senegal’s company-data challenge is not absence of official information. The challenge is fragmentation. RCCM, NINEA/RNEA, formation procedures, procurement context, tax services, IP, financial-sector sources and LEI records all answer different questions. CompaniesData adds value by turning those layers into a consistent, auditable dataset.

• Normalization: reconcile French-language legal names, accents, abbreviations, trading names and registry-style references.
• Source provenance: preserve exact source, access date, evidence type and field origin for every profile attribute.
• Entity matching: connect RCCM-oriented evidence with NINEA/RNEA, procurement, IP, financial-sector and LEI records using confidence scoring.
• Compliance controls: keep officer, representative, tax, beneficial-owner and contact-adjacent data out of marketing workflows unless a separate lawful basis exists.
• Delivery formats: package Senegal company profiles for analysis, CRM enrichment, KYB review and market research instead of forcing users through portals manually.

Request a CompaniesData sample for Senegal if you need normalized records with source provenance rather than a list of portals.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
SEN'INFOGREFFE	Ministry of Justice-backed registry platform	search / account / document portal	portal and RCCM document terms	Documents and some workflows may require registration or payment; no bulk claim.
SEN'INFOGREFFE company-name search	Ministry of Justice-backed registry platform	public search form	portal and RCCM terms	Search route, not a reusable bulk API.
APIX business creation service	APIX-S.A.	service page / one-stop-shop guidance	APIX website terms	Guidance/service layer, not a company master-data feed.
Senegal eRegulations BCE procedure	Senegal eRegulations / APIX procedure context	procedure guide	site terms and procedure-publication terms	Procedure guide, not registry data.
ARCOP	Autorite de Regulation de la Commande Publique	regulator portal / publications	ARCOP website terms	Regulator/context layer, not complete supplier registry.
BCEAO	Banque Centrale des Etats de l'Afrique de l'Ouest	portal / publications / regulated-sector context	BCEAO terms	Regional financial layer, not Senegal RCCM master data.
OAPI	Organisation Africaine de la Propriete Intellectuelle	IP portal / services / publications	OAPI terms	Regional IP layer only; not a company registry.
GLEIF LEI records for Senegal	Global Legal Entity Identifier Foundation	public API	GLEIF open data licence with attribution and no-endorsement conditions	Partial coverage, skewed toward financial and cross-border entities.

FAQ

Is there a free official bulk company database for Senegal?

Not verified in this cycle. Senegal has official company, identifier, procedure and enrichment sources, but a complete free RCCM/NINEA bulk company file was not confirmed. Bulk, API, paid extract and public-search access should be treated as separate access models.

What is the best first source for Senegal company data?

SEN’INFOGREFFE is the best clean starting point for RCCM-oriented company and security-register evidence. APIX and Senegal eRegulations explain formation workflows. E-NINEA/ANSD and DGID are important but should be rechecked before public linking because of TLS variance in this run.

Can SEN’INFOGREFFE data be reused commercially?

Commercial reuse depends on the specific access route, document type, portal terms and downstream use. Public search visibility is not the same as unrestricted bulk reuse. Preserve source attribution, access date and no-endorsement language.

Can NINEA or tax data be used for marketing?

No automatic marketing permission follows from identifier or tax context. NINEA, RNEA, tax, officer, representative, address, email and phone fields require privacy and marketing-law review before any outreach use.

Why include BCEAO, OAPI and GLEIF?

They enrich company profiles beyond RCCM identity. BCEAO adds financial-sector context, OAPI adds IP and trademark context, and GLEIF adds global legal-entity identifiers for entities that have LEIs. None is a complete Senegal company register.

Why are procurement and Journal Officiel held?

They are relevant sources, but the routes timed out from the editorial node in this QA cycle. The safe approach is to keep them source-mapped and recheck with browser and bot-like profiles before using them as public linked evidence.

What should a production Senegal dataset store?

Store normalized legal identity, source provenance, query route, access date, evidence type, identifier confidence, procedure context, procurement and IP events, LEI matches, privacy flags and update cadence. Do not collapse all source layers into one unqualified record.

How does CompaniesData handle contact data?

CompaniesData separates company identity and official-source evidence from contact-data workflows. Business emails, phone numbers, contact roles, suppression logic and segmentation require their own lawful basis and compliance process.

Official Sources

• SEN'INFOGREFFE – Ministry of Justice-backed registry platform
• SEN'INFOGREFFE company-name search – Ministry of Justice-backed registry platform
• APIX business creation service – APIX-S.A.
• Senegal eRegulations BCE procedure – Senegal eRegulations / APIX procedure context
• ARCOP – Autorite de Regulation de la Commande Publique
• BCEAO – Banque Centrale des Etats de l'Afrique de l'Ouest
• OAPI – Organisation Africaine de la Propriete Intellectuelle
• GLEIF LEI records for Senegal – Global Legal Entity Identifier Foundation