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

El Salvador has a useful official company-data ecosystem, but it should be read as a controlled official-source stack rather than a simple open bulk register. The strongest route starts with Centro Nacional de Registros, the CNR Registro de Comercio service page, eCNR online services and CreaEmpresa. Those sources establish the official registry and business-formalization route. Procurement, tax, regulator, central-bank, legal-publication and LEI sources then enrich the picture.

This 2026 refresh addresses two issues in the older CompaniesData page. First, the live article is below the current editorial depth bar, with an observed public word estimate of 1929 words. Second, several old Wave 9 endpoints no longer resolve reliably. The refresh should use CNR/eCNR/CreaEmpresa as the clean source route and treat the old RegistroComercio, MiEmpresa and Datos.gob.sv domains as source-drift findings, not as clean public evidence.

The commercial value is real: CNR and eCNR help with legal identity, Comprasal helps with public-contract activity, Hacienda helps with tax and public-finance context, SSF and BCR help with regulated-sector context, Diario Oficial helps with legal notices, and GLEIF helps with international identifiers. The legal boundary is equally important. Registry, tax, procurement, officer, beneficial-owner-adjacent, email and phone data are verification or compliance inputs, not marketing-contact permission.

Key Takeaways

• Best official route: CNR, the CNR Registro de Comercio service page, eCNR and CreaEmpresa are the clean registry and workflow stack for a 2026 refresh.
• Best enrichment layer: Comprasal adds supplier, tender and award context, but it only reflects public procurement activity.
• Bulk/API caution: no complete free official Registro de Comercio bulk API or master company-register download was verified in this cycle.
• Privacy caution: tax identifiers, officers, beneficial-owner-adjacent data, supplier contacts, emails and phones require lawful purpose, minimization and retention controls.
• Source drift: legacy registrocomercio.gob.sv, miempresa.gob.sv and datos.gob.sv should not be cited as clean evidence unless they recover in a later live check.
• CompaniesData role: the value is source-aware normalization: legal identity, procurement events, tax context, regulator evidence, legal notices and LEI records with provenance and caveats.

Editorial Methodology

This article follows the CompaniesData source-first editorial standard. Official sources are preferred over private aggregators. Each source is classified by authority, access model, reuse note, limitation and practical business value. The 2026-06-11 source recheck found 12 stable public links, 3 held routes, 0 hard 404/410 failures and 3 soft or controlled-access warnings.

HTTP 200 was not treated as enough. A clean source had to return real content without bot-protection semantics, unresolved DNS, hard failures or obvious access instability. The public CompaniesData page was also checked with browser, Googlebot and Bingbot-style profiles for title, canonical, robots/indexability, source matrix, FAQ, CompaniesData section and challenge-page avoidance.

The methodology separates source layers. A registry authority is not a reusable bulk file. A service portal is not an API licence. A procurement supplier record is not a complete business universe. A tax page is not outreach permission. A regulator list is sector-specific. A gazette notice is documentary evidence, not current-status proof for every company. A LEI record is structured but optional. These distinctions are what make a country article legally useful rather than a thin source list.

Coverage, Access and Update-Risk Analysis

Registry and formalization coverage: CNR, CNR Registro de Comercio, eCNR and CreaEmpresa establish the clean official route. They support company formation and commercial-register workflows, but they do not prove that a complete free registry file can be downloaded or reused without additional terms. A reliable dataset should store which route produced each observation.

Procurement coverage: Comprasal can identify public tenders, awards, buying entities and suppliers. This is useful for supplier intelligence and public-sector market analysis. It is still an event layer. A supplier name needs registry matching before it becomes a verified company profile, and procurement contacts are not sales-prospecting permission.

Tax and public-finance context: Ministerio de Hacienda strengthens identifier and fiscal context, especially for known-entity verification. Tax evidence has higher privacy and purpose-limitation risk. It should be stored in controlled identifier and compliance tables, not exported into uncontrolled marketing workflows.

Regulator, central-bank and gazette coverage: SSF and BCR support financial-sector and statistical context. Diario Oficial supports legal-publication research. These sources are important but partial. They help explain a company, sector or official event; they do not replace the Registro de Comercio route.

Structured identifiers: GLEIF is machine-readable and useful for international entity matching. Coverage is partial and skewed toward entities that need LEIs. A missing LEI is not evidence that a company is inactive or nonexistent.

Update risk: the main update risk is source drift. The old RegistroComercio, MiEmpresa and Datos.gob.sv domains failed DNS checks in every source profile. Future refreshes should monitor whether those domains return, but the publish-safe route should not depend on them today.

Reuse Checklist

• Source owner: record whether each observation came from CNR, Registro de Comercio service pages, eCNR, CreaEmpresa, Comprasal, Hacienda, SSF, BCR, Diario Oficial or GLEIF.
• Access model: separate institutional portal, service workflow, online lookup, procurement portal, tax portal, regulator publication, official gazette and LEI API records.
• Terms and licence: keep CNR service terms, Comprasal terms, Hacienda privacy limits, regulator terms, gazette terms and GLEIF attribution/no-endorsement conditions with each dataset.
• Completeness claim: do not claim a complete free Registro de Comercio bulk dataset unless a current official source explicitly provides one.
• Privacy flag: mark officers, representatives, beneficial-owner-adjacent data, tax identifiers, addresses, emails, phones and supplier contact details as sensitive or contact-sensitive.
• Marketing boundary: official access to registry, tax, procurement, regulator, gazette or LEI data does not create permission for sales outreach.
• Source drift: keep dead or unstable legacy endpoints in research notes, not in the clean public source matrix.
• Audit trail: retain exact URL, query route, access date, transformation step, reviewer status and source confidence for every normalized record.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Centro Nacional de Registros	Centro Nacional de Registros	institutional portal / registry services	CNR terms, service rules and privacy limits	Institutional portal; it is not proof of a complete free reusable registry bulk file.
CNR Registro de Comercio service page	Centro Nacional de Registros / Registro de Comercio	service page / registry workflow guidance	CNR and Registro de Comercio service terms	Service guidance and registry workflow context, not an unrestricted bulk-download licence.
eCNR Registro de Comercio online services	Centro Nacional de Registros / Registro de Comercio	online services / search and transactional workflows	eCNR service terms and official-record caveats	Online search and service access must be separated from certified records and bulk reuse.
eCNR Denominacion de Sociedades	Centro Nacional de Registros / Registro de Comercio	online lookup	eCNR service terms and official-record caveats	Lookup evidence only; not a complete company master file and not redistribution permission.
CreaEmpresa CNR	Centro Nacional de Registros	online business formalization workflow	CNR CreaEmpresa service terms	Workflow service, not open bulk company data.
Comprasal	Ministerio de Hacienda / UNAC	procurement portal / tenders / awards	Comprasal and tender-specific terms	Procurement subset only and not complete registry coverage.
Ministerio de Hacienda	Ministerio de Hacienda	portal / taxpayer services / public finance	Hacienda terms and tax privacy limits	Tax identifiers, emails and phone numbers are not marketing-contact permission.
Superintendencia del Sistema Financiero	Superintendencia del Sistema Financiero	regulated-entity context / notices / publications	SSF terms	Sector-specific layer only.
Banco Central de Reserva	Banco Central de Reserva de El Salvador	publications / statistics / financial context	BCR terms and source-specific reuse notes	Mostly aggregate/statistical and not a company-register source.
Diario Oficial	Imprenta Nacional / Diario Oficial	official publication downloads	Diario Oficial terms	Document layer, not current-status proof for every company.
GLEIF LEI records for El Salvador	Global Legal Entity Identifier Foundation	public API	GLEIF API terms	LEI coverage is partial and skewed toward financial and cross-border entities.
Transparencia Fiscal Datos Abiertos	Ministerio de Hacienda	open-data catalogue / downloads	dataset-specific terms	Not a registry master file; live access can be slow or timeout-prone and needs final browser QA.

Source-by-Source Deep Dives

1. Centro Nacional de Registros

Authority: Centro Nacional de Registros. Type: official registry authority. Access model: institutional portal / registry services. Reuse note: CNR terms, service rules and privacy limits. Business use: Primary official authority for registry routes, including commerce and IP context.

CNR is the institutional anchor for El Salvador company-data work. It is the official registry authority that ties together commercial-register services and other registry functions. In a normalized dataset, CNR should be stored as the authority layer: source owner, source URL, access date, registry service route and evidence type. The safe claim is that CNR is the official route. The unsafe claim is that the CNR home page itself provides a complete free company master file.

Limitation: Institutional portal; it is not proof of a complete free reusable registry bulk file.

2. CNR Registro de Comercio service page

Authority: Centro Nacional de Registros / Registro de Comercio. Type: official commercial-register service page. Access model: service page / registry workflow guidance. Reuse note: CNR and Registro de Comercio service terms. Business use: Official route for commercial-register services and filings context.

The CNR Registro de Comercio service page is the clearest official route for explaining commercial-register workflows. It is useful for service scope, filings context and the practical route a user follows before obtaining official records. It should be modeled as registry workflow evidence, not as an unrestricted bulk dataset. A public article should keep service guidance, search observations and certified-record requests separate.

Limitation: Service guidance and registry workflow context, not an unrestricted bulk-download licence.

3. eCNR Registro de Comercio online services

Authority: Centro Nacional de Registros / Registro de Comercio. Type: official commercial-register online services. Access model: online services / search and transactional workflows. Reuse note: eCNR service terms and official-record caveats. Business use: Practical online route for commercial-register checks and service access.

eCNR is the practical online-services layer. It matters because it is closer to day-to-day verification than a general institutional page, but online access is still controlled service access. Store query route, query date, result type and confidence. Do not treat a visible search or transaction screen as redistribution permission for every field.

Limitation: Online search and service access must be separated from certified records and bulk reuse.

4. eCNR Denominacion de Sociedades

Authority: Centro Nacional de Registros / Registro de Comercio. Type: official company-name / society lookup. Access model: online lookup. Reuse note: eCNR service terms and official-record caveats. Business use: Name and society-denomination verification input for entity matching.

The eCNR society-denomination lookup is useful for name checking and entity-resolution workflow. It can help identify naming conflicts, possible legal names or society-denomination evidence. The limitation is narrow scope. A name lookup does not prove complete status, ownership, officers, tax validity or full registry coverage. It belongs as a matching support layer.

Limitation: Lookup evidence only; not a complete company master file and not redistribution permission.

5. CreaEmpresa CNR

Authority: Centro Nacional de Registros. Type: official business-registration workflow. Access model: online business formalization workflow. Reuse note: CNR CreaEmpresa service terms. Business use: Business-registration workflow and incorporation-route context.

CreaEmpresa is the business-formalization workflow layer. It helps readers understand how company formation or registration steps appear in the public digital service environment. For data engineering, CreaEmpresa metadata should inform lifecycle and workflow fields, not replace the Registro de Comercio source of truth. It also reinforces the point that workflow services are not open bulk company data.

Limitation: Workflow service, not open bulk company data.

6. Comprasal

Authority: Ministerio de Hacienda / UNAC. Type: official procurement. Access model: procurement portal / tenders / awards. Reuse note: Comprasal and tender-specific terms. Business use: Supplier, tender and public-contract enrichment.

Comprasal is the procurement enrichment layer. It can add tenders, awards, supplier names, public buyers and contracting events. Procurement data is commercially useful because it shows active public-sector business relationships, but it is only a subset. Supplier evidence should be matched back to CNR or another official identity source before it becomes a verified company profile.

Limitation: Procurement subset only and not complete registry coverage.

7. Ministerio de Hacienda

Authority: Ministerio de Hacienda. Type: tax and public-finance authority. Access model: portal / taxpayer services / public finance. Reuse note: Hacienda terms and tax privacy limits. Business use: Taxpayer, public-finance and procurement-adjacent context for known entities.

Ministerio de Hacienda is the tax and public-finance context. Taxpayer-service material can support known entity verification and compliance workflows, but tax identifiers, fiscal addresses, emails and phone fields need purpose limitation. This layer should never be represented as consent for marketing outreach or as an unrestricted lead list.

Limitation: Tax identifiers, emails and phone numbers are not marketing-contact permission.

8. Superintendencia del Sistema Financiero

Authority: Superintendencia del Sistema Financiero. Type: financial regulator. Access model: regulated-entity context / notices / publications. Reuse note: SSF terms. Business use: Financial regulated-entity enrichment and supervisory context.

SSF is the financial-regulator layer. It is relevant for banks, insurers, securities participants and other supervised entities, but it does not cover the full business population. In a data model, SSF records belong in a regulated-sector table with licence or supervision category, source date, authority and match confidence.

Limitation: Sector-specific layer only.

9. Banco Central de Reserva

Authority: Banco Central de Reserva de El Salvador. Type: central bank and statistics. Access model: publications / statistics / financial context. Reuse note: BCR terms and source-specific reuse notes. Business use: Economic, central-bank and financial-statistics context.

BCR adds central-bank, financial and statistical context. It can support sector analysis and macroeconomic validation, but most BCR outputs are aggregate or financial-market oriented. Treat BCR as context and regulated-sector enrichment, not as company registry identity proof.

Limitation: Mostly aggregate/statistical and not a company-register source.

10. Diario Oficial

Authority: Imprenta Nacional / Diario Oficial. Type: official gazette / legal publications. Access model: official publication downloads. Reuse note: Diario Oficial terms. Business use: Legal notices and official-publication layer for company-life context.

Diario Oficial is the legal-publication layer. It can support company-life research, official notices and documentary context, especially for changes that appear in official publications. It is not a current-status register for every company. Gazette evidence should keep publication date, issue reference, title and source URL separate from registry identity fields.

Limitation: Document layer, not current-status proof for every company.

11. GLEIF LEI records for El Salvador

Authority: Global Legal Entity Identifier Foundation. Type: LEI API. Access model: public API. Reuse note: GLEIF API terms. Business use: Cross-border legal-entity identifier enrichment for entities with LEIs.

GLEIF provides standardized LEI records for entities that participate in the global LEI system. It is the most machine-readable structured source in this stack, but coverage is partial and often weighted toward financial or cross-border entities. Use it for enrichment and matching, not as evidence that non-LEI companies do not exist.

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

12. Transparencia Fiscal Datos Abiertos

Authority: Ministerio de Hacienda. Type: official fiscal open-data page. Access model: open-data catalogue / downloads. Reuse note: dataset-specific terms. Business use: Fiscal open-data context and public-finance enrichment.

The fiscal open-data route can add public-finance context where it is stable, but this source should be used carefully because it is not a company master table. If retained in a future public refresh, every dataset should receive its own licence, field and freshness review before any reuse claim.

Limitation: Not a registry master file; live access can be slow or timeout-prone and needs final browser QA.

Held Source-Risk Findings

Current result: three legacy Wave 9 endpoints are held as source-drift findings. They are not linked as clean evidence in this refresh article because all source profiles failed DNS resolution. This is a source-maintenance finding, not a claim that the underlying institutions are invalid.

• Legacy RegistroComercio.gob.sv endpoint: held after live-check result ConnectionError. Reason: HTTPSConnectionPool(host='www.registrocomercio.gob.sv', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("HTTPSConnection(host='www.registrocomercio.gob.sv', port=443): Failed to resolve 'www.registrocomercio.gob.sv' ([Errno 11001] getaddrinfo failed)")).
• Legacy MiEmpresa.gob.sv endpoint: held after live-check result ConnectionError. Reason: HTTPSConnectionPool(host='miempresa.gob.sv', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("HTTPSConnection(host='miempresa.gob.sv', port=443): Failed to resolve 'miempresa.gob.sv' ([Errno 11001] getaddrinfo failed)")).
• Legacy Datos.gob.sv endpoint: held after live-check result ConnectionError. Reason: HTTPSConnectionPool(host='www.datos.gob.sv', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("HTTPSConnection(host='www.datos.gob.sv', port=443): Failed to resolve 'www.datos.gob.sv' ([Errno 11001] getaddrinfo failed)")).

The publish-safe article should use CNR, CNR Registro de Comercio, eCNR and CreaEmpresa instead of those legacy domains unless a later browser and bot-profile recheck proves that the endpoints resolve again.

Practical Manual, API and Bulk Options

Manual lookup workflow

For a single El Salvador entity, begin with the CNR and Registro de Comercio route. Use eCNR and CreaEmpresa to understand online service and formalization context, then enrich carefully with Comprasal supplier evidence, Hacienda tax/public-finance context, SSF regulated-sector records, BCR statistics or financial context, Diario Oficial notices and GLEIF LEI matches where available.

API and structured-data workflow

GLEIF is the cleanest structured API in this source stack. Comprasal may support structured procurement work depending on portal access and terms, but it is procurement-only. The registry layer should be described as controlled official service/search access unless a current CNR or Registro de Comercio bulk/API licence is verified.

Bulk-data workflow

This cycle did not verify a complete free official company-register bulk file. A safe bulk workflow therefore depends on licensed access, official reusable datasets with clear terms, or CompaniesData normalization with provenance controls. Bulk outputs should separate legal identity, procurement events, tax identifiers, regulator status, gazette notices and LEI matches.

Contact-data workflow

For international audiences, the owned route for normalized company-data work is CompaniesData.cloud. For Spanish-speaking or Hispanic contact-data workflows, the owned route is CentraldeComunicacion.es. Official public records may support verification, but they do not authorize cold outreach, phone lists or unrestricted sales prospecting.

Missing Data Gaps

• No complete bulk registry proof: this review did not confirm a complete free official Registro de Comercio bulk API or master company file.
• Legacy source drift: older RegistroComercio, MiEmpresa and Datos.gob.sv endpoints failed DNS checks and should be replaced in public content.
• Procurement subset: Comprasal only covers public procurement participation, not all active companies.
• Sector bias: SSF, BCR and GLEIF skew toward regulated, financial or internationally active entities.
• Documentary limits: Diario Oficial notices are useful legal evidence but do not replace current registry status checks.
• Privacy-sensitive fields: natural-person-adjacent roles, tax identifiers, addresses, emails and phones require field-level review before reuse.

Recommended Data Model

• Legal entity core: legal name, normalized name, country, jurisdiction, entity type, registry route, source authority and confidence score.
• Registry evidence: CNR/eCNR URL, access date, query route, service type, result type and certified-record distinction.
• Procurement events: Comprasal tender ID, buyer, supplier name, award or notice date, amount where lawful, source URL and match confidence.
• Tax context: Hacienda source route, identifier type, verification date, purpose flag and privacy classification.
• Regulator evidence: SSF/BCR category, licence or supervision context, publication date, source URL and sector scope.
• Legal-publication evidence: Diario Oficial issue, notice type, publication date, title, source URL and linked entity confidence.
• LEI enrichment: LEI, legal name, status, address country, managing LOU, GLEIF last update and match confidence.
• Compliance metadata: reuse note, terms note, access model, personal-data flag, contact-data flag, suppression status and reviewer status.

CompaniesData Normalization and Enrichment Value

A manual El Salvador source list is useful, but it does not solve the operational problem. The same organization may appear differently in CNR workflows, procurement notices, tax context, regulator pages, gazette notices and LEI records. CompaniesData adds value by reconciling those observations into source-attributed profiles with normalized names, deduplication, entity-type consistency, country and sector tags, update tracking and field-level caveats.

The important normalization step is restraint. A procurement supplier should not overwrite registry identity without match confidence. A tax identifier should not be exported as a marketing field. A gazette notice should not be treated as current status without registry confirmation. A LEI match should enrich the profile but not exclude entities without LEIs. This source-aware model is more credible for compliance, market intelligence and data partnerships than scraping a flat list of names.

For CompaniesData.cloud users, the practical outcome is a cleaner El Salvador dataset: official-source provenance, controlled-access notes, source-drift handling, no-bulk overclaims, contact-data suppression flags and enrichment hooks for procurement, finance, legal notices and LEI records.

Resource Pack

Official Sources

• Centro Nacional de Registros – Centro Nacional de Registros
• CNR Registro de Comercio service page – Centro Nacional de Registros / Registro de Comercio
• eCNR Registro de Comercio online services – Centro Nacional de Registros / Registro de Comercio
• eCNR Denominacion de Sociedades – Centro Nacional de Registros / Registro de Comercio
• CreaEmpresa CNR – Centro Nacional de Registros
• Comprasal – Ministerio de Hacienda / UNAC
• Ministerio de Hacienda – Ministerio de Hacienda
• Superintendencia del Sistema Financiero – Superintendencia del Sistema Financiero
• Banco Central de Reserva – Banco Central de Reserva de El Salvador
• Diario Oficial – Imprenta Nacional / Diario Oficial
• GLEIF LEI records for El Salvador – Global Legal Entity Identifier Foundation
• Transparencia Fiscal Datos Abiertos – Ministerio de Hacienda

FAQ

What is the best first source for company data in El Salvador?

Start with CNR and the Registro de Comercio route. For practical workflow context, use eCNR and CreaEmpresa. Those sources are stronger and cleaner than the legacy endpoints that failed DNS in this recheck.

Does El Salvador provide a complete free company-register bulk API?

No complete free official Registro de Comercio bulk API was verified in this cycle. The safe public claim is controlled official service/search access plus enrichment from procurement, tax, regulator, gazette and LEI sources.

Can Comprasal be used as a company list?

Comprasal is useful for supplier and public-contract enrichment, but it is not a full company register. It covers procurement activity and should be matched back to registry evidence before becoming verified company identity data.

Are tax or procurement contact details permission for marketing?

No. Registry, tax, procurement, regulator, email and phone fields are verification or compliance evidence. They are not consent for sales outreach, lead lists or unrestricted marketing databases.

Why hold the old RegistroComercio, MiEmpresa and Datos.gob.sv endpoints?

All source profiles failed DNS resolution for those legacy URLs during the 2026-06-11 recheck. They remain useful as source-drift notes, but they should not be linked as clean evidence unless a later source-live QA clears them.

Where should Spanish-speaking contact-data demand go?

For Spanish-speaking or Hispanic contact-data workflows, route to CentraldeComunicacion.es. For international company-data workflows, use CompaniesData.cloud. Do not convert official records into competitor contact-data recommendations.

How should a data team model El Salvador sources?

Use separate tables for registry evidence, procurement events, tax context, regulator records, legal publications and LEI enrichment. Add source URL, access date, access model, reuse note, privacy flag and match confidence to every field.