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

Bolivia has commercially useful official company-data routes, but it is not a jurisdiction where a buyer should assume that the core company register is available as a complete free bulk download. The safest publishable source map treats SEPREC as the official Registro de Comercio authority but keeps direct SEPREC routes de-linked until Bingbot source access is stable; the clean linked evidence stack then uses procurement, tax, IP, regulator, statistics and LEI sources. That combination can support high-quality entity matching, but each field needs a source label and a lawful-use boundary.

The practical conclusion is nuanced. Bolivia is publishable as a deep reference article when the article frames SEPREC as controlled official context, keeps currently challenged SEPREC routes de-linked, uses SICOES as procurement enrichment, treats NIT and regulator data as compliance or verification context, and avoids presenting public records as sales-prospecting consent. For a normalized company database, the value is not merely copying public pages. The value is source-aware normalization: cleaning names, preserving identifiers, separating registry evidence from enrichment evidence, and flagging fields that need privacy review.

Key Takeaways

• Best registry anchor: SEPREC is the official Registro de Comercio authority, but direct SEPREC portal links are held in this update because Bingbot receives Cloudflare challenge pages. The safe claim remains controlled portal/search/service access, not a complete open bulk API.
• Best enrichment layer: SICOES can add public-procurement supplier, tender and award context, but it only covers public-sector contracting activity.
• Identifier caution: NIT and taxpayer context are useful for verification but must not be treated as marketing-contact permission.
• Held routes: SEPREC, SEPREC Mi Empresa, SEPREC Tramites, Bolivia Datos Abiertos and Gaceta Oficial are retained as research context but not linked as clean evidence in this cycle because source-live checks produced bot-protection, timeout or access-control warnings.
• CompaniesData value: The strongest dataset is a normalized, source-attributed model that separates legal identity, procurement, tax, IP, regulator, statistics and LEI evidence.

Editorial Methodology

This article is built from an official-source-first review. The clean linked source stack was rechecked on 2026-06-14 with an editorial profile and, when required, browser, Googlebot and Bingbot-style source profiles. A source was treated as clean only when it returned real content without obvious bot-protection semantics, hard 404/410 errors or access instability. HTTP 200 alone was not enough. The review also checked the existing public CompaniesData page for indexability, title/canonical semantics and approximate depth, because a page can be reachable but still fail the current editorial bar.

Sources were classified by authority, access model, reuse note, business use and limitation. Official registry and government routes were prioritized over private aggregators. Non-registry sources were included only when they add a distinct evidence layer: procurement participation, tax identifier context, intellectual property, regulator status, economic statistics or LEI identity. Where a route was unstable, it was held out of the clean source matrix rather than forced into the article.

Coverage, Access and Update-Risk Analysis

Bolivia’s company-data coverage should be understood as a layered system. SEPREC and related service portals are the primary official routes for company registration and filings. They are strong for authority, workflow and manual verification, but they do not prove the existence of a complete free reusable master file. That is the central update-risk issue: a company profile can be verified through official portals while bulk reuse, redistribution and refresh automation remain limited.

SICOES improves commercial usefulness because procurement records show companies that bid for or win public contracts. That is valuable for supplier intelligence, public-sector exposure and market analysis. It should not be used as a substitute for the commercial register. A supplier name in procurement may need deduplication, transliteration cleanup, entity-type parsing and registry matching before it can be merged into a company master record. Procurement data is also time-sensitive: tenders and awards can become stale faster than registry identity fields.

Tax, regulator and IP layers add verification depth but raise privacy and lawful-use questions. NIT or taxpayer evidence can confirm an identifier in a compliance workflow, but it is not a permission signal for outreach. ASFI covers financial-sector supervision, not every Bolivian company. SENAPI covers rights owners and filings, not the full legal-entity population. INE provides aggregate context rather than row-level company identity. GLEIF provides structured identifiers for entities with LEIs, but coverage is partial.

Reuse Checklist

• Keep source provenance: store source name, URL, access date, evidence type and retrieval route for every field.
• Do not overstate bulk rights: describe SEPREC as controlled official portal/search access unless a current official bulk licence is verified.
• Separate enrichment from identity: procurement, IP, regulator, statistics and LEI layers should not overwrite registry identity without match confidence.
• Apply privacy controls: NIT, officers, beneficial owners, emails, phones and contact fields require lawful purpose, minimization and retention limits.
• Refresh before publication: rerun source-live and crawler-access checks before any WordPress update or indexing submission.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
SEPREC	Servicio Plurinacional de Registro de Comercio	official registry portal / services	SEPREC portal terms and Bolivian registry-service rules	Controlled portal access; no complete free official bulk company-register dataset verified.
SEPREC Mi Empresa	Servicio Plurinacional de Registro de Comercio	company portal / search / services	SEPREC portal terms and service rules	Portal workflow, not an unrestricted company master API or bulk licence.
SEPREC Tramites	Servicio Plurinacional de Registro de Comercio	procedure portal / filings	SEPREC service terms	Procedure access; not reusable company-register bulk data.
SICOES	Sistema de Contrataciones Estatales	tenders / awards / supplier context	SICOES terms and public-procurement publication rules	Procurement subset only; not a whole-economy company register.
Servicio de Impuestos Nacionales	Servicio de Impuestos Nacionales	tax portal / taxpayer services	tax privacy and service terms	Tax identifiers and taxpayer data are not marketing-contact permission.
SENAPI	Servicio Nacional de Propiedad Intelectual	IP portal / services	SENAPI terms	IP records are partial and do not represent all active companies.
ASFI	Autoridad de Supervision del Sistema Financiero	regulator website / supervised-entity context	ASFI terms	Sector-specific; does not cover the full company population.
Instituto Nacional de Estadistica Bolivia	Instituto Nacional de Estadistica	statistics / reports	INE terms	Aggregate/statistical layer, not legal-entity master data.
GLEIF LEI records for Bolivia	Global Legal Entity Identifier Foundation	public API	GLEIF API terms	LEI coverage is partial and skewed toward financial/cross-border entities.

Source-by-Source Deep Dives

SEPREC

Authority: Servicio Plurinacional de Registro de Comercio. Access model: official registry portal / services. Reuse note: SEPREC portal terms and Bolivian registry-service rules. Main limitation: Controlled portal access; no complete free official bulk company-register dataset verified.

SEPREC is the anchor authority for Bolivia company-register work. It gives the article a defensible starting point because the source is official and tied to the Registro de Comercio, but the practical access model remains portal and service based. A data product should therefore keep SEPREC fields separate from enrichment fields and preserve source URL, access date, evidence type and retrieval route. The safe claim is that SEPREC is the official registry authority and an official route for registry services; the unsafe claim is that SEPREC publishes a complete free reusable bulk company-register dataset.

SEPREC Mi Empresa

Authority: Servicio Plurinacional de Registro de Comercio. Access model: company portal / search / services. Reuse note: SEPREC portal terms and service rules. Main limitation: Portal workflow, not an unrestricted company master API or bulk licence.

SEPREC Mi Empresa is useful for practical verification because it represents the public-facing service layer where users expect company search or registry-service workflows. It should be treated as controlled official access. That matters for normalization: a portal observation may confirm an entity, a registration workflow or a service route, but it does not automatically grant redistribution rights over every field visible in a screen. Store the access model as portal/search, not bulk API, and keep evidence snapshots tied to a lawful verification purpose.

SEPREC Tramites

Authority: Servicio Plurinacional de Registro de Comercio. Access model: procedure portal / filings. Reuse note: SEPREC service terms. Main limitation: Procedure access; not reusable company-register bulk data.

SEPREC Tramites adds procedure and filing context. It is valuable for explaining what users can do with official services, which lifecycle events may exist and why company data in Bolivia is often procedural as well as registry based. It should not be presented as the master register. In a CompaniesData model, this source informs workflow metadata, filing categories, update-risk notes and manual verification steps rather than a standalone entity table.

SICOES

Authority: Sistema de Contrataciones Estatales. Access model: tenders / awards / supplier context. Reuse note: SICOES terms and public-procurement publication rules. Main limitation: Procurement subset only; not a whole-economy company register.

SICOES is the public-procurement enrichment layer. It can help identify suppliers, tenders, awards, buyers and procurement participation, but it covers companies that interact with public contracting, not every Bolivian legal entity. The article should make that boundary visible. Procurement names need matching against SEPREC or another authority before becoming verified company profiles, and supplier, bidder, buyer or award fields should keep match confidence and tender identifiers.

Servicio de Impuestos Nacionales

Authority: Servicio de Impuestos Nacionales. Access model: tax portal / taxpayer services. Reuse note: tax privacy and service terms. Main limitation: Tax identifiers and taxpayer data are not marketing-contact permission.

Servicio de Impuestos Nacionales is the identifier and tax-context layer. NIT-related material is valuable for known-entity verification and compliance workflows, but tax identifiers and taxpayer services are not marketing-contact permission. A proper dataset should flag tax fields as sensitive, keep retention and purpose limitation clear, and avoid implying that tax records authorize prospecting or bulk outreach.

SENAPI

Authority: Servicio Nacional de Propiedad Intelectual. Access model: IP portal / services. Reuse note: SENAPI terms. Main limitation: IP records are partial and do not represent all active companies.

SENAPI is the intellectual-property enrichment layer. Trademark, patent or rights-owner evidence can improve entity resolution, brand matching and group analysis, especially where names vary between registry, brand and procurement records. The limitation is coverage: IP records describe right holders and filings, not the full company universe. They should be stored as enrichment records with filing type, mark, owner name, status, source URL and match confidence.

ASFI

Authority: Autoridad de Supervision del Sistema Financiero. Access model: regulator website / supervised-entity context. Reuse note: ASFI terms. Main limitation: Sector-specific; does not cover the full company population.

ASFI is the financial regulator source. It is useful for regulated banks, insurers, financial intermediaries and supervised-sector context, but it is not the general company register. It belongs in a sector-regulation table with category, licence or register context, date and authority. Regulator pages may include contact or branch information; those fields are compliance evidence, not lead-list permission.

Instituto Nacional de Estadistica Bolivia

Authority: Instituto Nacional de Estadistica. Access model: statistics / reports. Reuse note: INE terms. Main limitation: Aggregate/statistical layer, not legal-entity master data.

INE Bolivia supplies the official statistics layer. It helps validate market size, business demography and economic context, but it normally works at aggregate level. Do not join aggregate statistics to individual companies as if they were registry facts. Instead, use INE as contextual metadata for sector, geography, activity and update-risk analysis.

GLEIF LEI records for Bolivia

Authority: Global Legal Entity Identifier Foundation. Access model: public API. Reuse note: GLEIF API terms. Main limitation: LEI coverage is partial and skewed toward financial/cross-border entities.

GLEIF provides the structured LEI layer for Bolivian entities that have legal entity identifiers. It is excellent for cross-border matching because the API is structured and globally standardized. Coverage is partial, usually weighted toward financial and cross-border entities, so absence of an LEI is not evidence that a company does not exist. Store LEI joins with confidence, source date, legal name and address provenance.

Held Source-Risk Findings

The following official routes are useful research context but are not clean linked evidence in this article cycle:

• SEPREC: held and de-linked because Bingbot receives Cloudflare challenge semantics while browser and Googlebot profiles can retrieve content. SEPREC remains the official Registro de Comercio authority, but direct public linking waits for stable all-profile access.
• SEPREC Mi Empresa: held and de-linked because the company-service route shows the same Bingbot Cloudflare challenge. It remains source-mapped as a controlled workflow, not an open-bulk source.
• SEPREC Tramites: held and de-linked because the procedure route also returns Bingbot Cloudflare challenge semantics. Use it as workflow context only until browser, Googlebot and Bingbot profiles all retrieve real content.

Prior Held Routes

The following routes are useful research context but are not clean linked evidence in this article cycle:

• Bolivia Datos Abiertos: held from clean linking because Company microdata coverage and dataset freshness vary by publisher..
• Gaceta Oficial de Bolivia: held from clean linking because HTTPSConnectionPool(host='www.gacetaoficialdebolivia.gob.bo', port=443): Read timed out. (read timeout=8).

Holding a source is not a claim that the institution is unreliable. It means the automated editorial, browser or bot-profile checks did not return stable evidence that can be used as a clean link today. The route can return after a manual browser check or a later source-live retry clears the access problem.

Practical Manual, API and Bulk Options

Manual verification: Treat SEPREC and Mi Empresa as official registry/service context but keep their direct routes in the held-source track until Bingbot retrieves real content instead of a Cloudflare challenge. Preserve the exact query, source route and access date. If a record is collected through a form or service workflow, record that access model explicitly instead of presenting it as an open dataset.

Procurement enrichment: Use SICOES as a supplier and contracting layer. Capture tender or award identifiers, contracting entity, supplier name, dates and source URL. Match supplier names to registry identity with conservative rules and a confidence score, especially where names include abbreviations, legal forms or Spanish accents.

Tax and identifier checks: Use SIN only for legitimate verification and compliance cases. Do not use NIT or taxpayer context as a marketing list. Store tax evidence separately from contact fields, and make the lawful purpose visible to downstream users.

Bulk/API expectations: GLEIF is the clean structured API in this source stack, but it only covers entities with LEIs. The Bolivia company-register layer should be described as controlled access until a current official SEPREC bulk licence or API is verified. SICOES may support structured procurement work, but procurement is an enrichment subset rather than a complete company universe.

Missing Data Gaps

• Complete register bulk: no verified complete free official SEPREC bulk/API dataset in this cycle.
• Beneficial ownership: beneficial-owner and officer details need explicit privacy and lawful-use review before being surfaced in reusable products.
• Open-data catalogue variance: the national open-data route was held from clean linking today and should be rechecked before being used as evidence.
• Gazette stability: the official gazette route was held from clean linking today; legal notices remain useful context but should not be merged as current registry status without verification.
• Coverage bias: procurement, regulator, IP and LEI sources overrepresent specific subsets of companies.

Recommended Data Model

A Bolivia company profile should use a source-attributed model rather than a single flat table. The core entity table should store normalized legal name, original legal name, legal form when available, jurisdiction, registry/source route, source URL, access date and confidence. A registry-events table should hold filings, procedure context, status evidence and document references. A procurement table should hold SICOES tender and award evidence. A tax/identifier table should hold NIT context only when there is a lawful verification purpose. IP, regulator, statistics and LEI tables should be separate enrichment layers.

The model should also include field-level sensitivity. Public does not mean unrestricted. Officer names, beneficial-owner fields, tax identifiers, emails, phones and addresses can be lawful to verify while still being inappropriate for direct marketing. Contact-data use for English or international audiences should be handled through CompaniesData.cloud, while Spanish-speaking or Hispanic contact-data demand should be routed to CentraldeComunicacion.es rather than private competitor databases.

CompaniesData Normalization and Enrichment Value

CompaniesData adds value by turning a fragmented official-source map into a usable, auditable company-data layer. For Bolivia, that means normalizing Spanish legal names, removing duplicate punctuation and casing, preserving accents where they matter, parsing legal forms, mapping procurement supplier names to registry identity, connecting LEIs where available, and separating official registry evidence from enrichment evidence. The output should let a user see not only a company profile, but also which source supports each claim.

That source-aware approach is especially important in Bolivia because the strongest official sources have different purposes. SEPREC proves registry authority and workflows, but direct SEPREC URLs are held from clean linking in this update because Bingbot source QA still receives Cloudflare challenge pages. SICOES proves procurement participation. SIN supports tax/identifier verification. SENAPI supports IP ownership. ASFI supports regulated financial context. INE supports aggregate business and economic context. GLEIF supports structured global identifiers. None of those layers alone should be sold as a complete universal company register or as a ready-made outreach list.

FAQ

Is there a free official bulk company register for Bolivia?

Not in this recheck. The safe claim is that SEPREC is the official registry authority and provides portal or service access. A complete free official bulk company-register API should not be claimed unless SEPREC publishes current terms that explicitly allow it.

Can SICOES be used as a company database?

SICOES is useful procurement enrichment, not a full company database. It can identify suppliers and public contracting activity, but procurement participation is only one subset of the market.

Can NIT or tax data be used for marketing?

No. Tax identifiers and taxpayer-service context should be treated as verification or compliance material. They are not consent for sales outreach or marketing-contact enrichment.

Why are some official sources held?

A held source may still be official, but the current access test did not return stable clean evidence for publication. The route can be reintroduced after manual browser QA or a later source-live run clears the issue.

What is the safest data-product approach?

Use SEPREC as the registry-authority context, SICOES as procurement enrichment, SIN as controlled identifier context, SENAPI and ASFI as sector layers, INE as aggregate context and GLEIF as partial structured LEI enrichment. Keep the direct SEPREC URLs held until all bot profiles retrieve real source content. Keep provenance and sensitivity flags on every field.

Official Sources

The clean linked evidence stack for this update uses SICOES, Servicio de Impuestos Nacionales, SENAPI, ASFI, INE Bolivia and GLEIF. SEPREC routes are listed as held source-risk context above until Bingbot access clears.

Resource Pack