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

Peru is a controlled-access but commercially useful official-source market for open company data. It should not be described as a country with one complete free legal-company bulk register. The practical stack is SUNARP for legal-person registry authority, directory/search and registry-publicity workflows; SUNAT for RUC lookup and reduced RUC bulk download; OECE/SEACE and RNP for public-procurement supplier evidence; PNDA/gob.pe for open-data governance; INEI for business-demography context; SBS and SMV for regulated-entity layers; Diario Oficial El Peruano for legal-publication evidence; and GLEIF for LEI cross-checks.

This refresh upgrades the older Peru page from a short caveated source map into a deep CompaniesData reference article. It separates registry authority from tax identifiers, tax bulk from legal-company bulk, procurement suppliers from all companies, and public company evidence from private marketing-contact enrichment.

Key Takeaways

• Best legal-registry authority: SUNARP is the official registry authority and the best starting point for legal-person registration and registry-publicity workflows.
• Best free registry lookup: the SUNARP National Directory of Legal Persons is a monthly updated referential search route, not certified registry publicity.
• Best tax identifier layer: SUNAT RUC search and the reduced RUC download are useful for RUC validation and entity resolution, but they are tax data rather than legal-register records.
• Best open-data/procurement layer: OECE/SEACE open data and RNP provide supplier, award and public-procurement context.
• CompaniesData value: production use needs identifier normalization, legal-name matching, source-date tracking, SUNARP/SUNAT separation, privacy flags and contact-data boundaries.

Editorial Methodology

This article follows the CompaniesData country-source method. Official authority pages and live public-service routes are prioritized over private aggregators. Each source is classified by authority, type, access model, reuse position and limitation. A source is not treated as a general company register unless it actually provides legal-entity registration evidence. A source is not treated as bulk unless there is a stable download or API route that can be verified.

Each linked source was checked from this environment on 2026-06-09. Direct routes that returned unstable catalogue behaviour are held instead of linked as clean evidence. Logos are decorative favicon cues only; source owner, official URL, access model and reuse note remain the evidence.

Coverage, Access and Update-Risk Analysis

SUNARP boundary: SUNARP is the legal-register authority and provides services, directory/search and registry-publicity workflows. The National Directory is useful because it is free, referential and monthly updated, but it explicitly does not replace the official registry-publicity index search.

Partida boundary: free partida consultation can support document-level review, but it uses identity validation and viewing limits and states that the result is referential rather than certified evidence for administrative or judicial procedures.

Statistics boundary: SUNARP and INEI statistics help with market coverage, entity categories and business demography. They are not record-level legal-company data.

SUNAT boundary: SUNAT RUC search and reduced RUC downloads can support tax-identifier validation and bulk matching. They must be kept separate from SUNARP legal evidence, and fields tied to natural persons, addresses or tax status need privacy review.

Procurement boundary: OECE/SEACE and RNP are strong public-procurement layers. They identify suppliers, awards, procedures and eligibility contexts, but procurement participants are not the whole Peruvian company universe.

Regulator boundary: SBS and SMV add high-value financial and securities-regulated subsets. They improve confidence for regulated firms but cannot be generalized to all businesses.

Contact-data boundary: registry, RUC, procurement, gazette, regulator and LEI fields do not create permission for cold email, phone lists, WhatsApp outreach or sales-prospecting contact enrichment. Contact enrichment needs separate consent, legitimate-interest assessment, suppression handling, opt-out and privacy review.

Reuse Checklist

• Authority: store whether a field came from SUNARP, SUNAT, OECE/SEACE, RNP, PNDA, INEI, SBS, SMV, El Peruano or GLEIF.
• Access route: separate search, directory, registry-publicity preview, XLSX statistics, RUC lookup, RUC download, procurement dataset, supplier consultation, PDF report, regulator directory and LEI API.
• Coverage: distinguish legal persons, tax registrants, public-procurement suppliers, regulated financial entities, securities-market participants and LEI holders.
• Freshness: store source access date, directory update cadence, RUC download date, procurement dataset date, report year and transformation date.
• Privacy: flag natural-person, address, representative, tax-status and contact-like fields before redistribution or enrichment.
• Marketing: never convert SUNAT, SUNARP, RNP or procurement evidence into an outreach list without a separate lawful basis.
• Auditability: keep official source fields and CompaniesData enrichment fields in separate columns.

Resource Pack

Source-by-Source Deep Dives

1. SUNARP

Authority: Superintendencia Nacional de los Registros Publicos. Type: official legal registry authority. Access model: services / publications / registry guidance. Reuse position: SUNARP service terms and registry-publicity limits.

Primary authority for Peru legal registries, including persons juridicas services and publications. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Authority page is not a bulk-data licence or full downloadable company register. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

2. SUNARP online services

Authority: SUNARP. Type: official registry service hub. Access model: online service hub / registry procedures. Reuse position: service-specific terms and controlled-access caution.

Routes users to inscription, registry-publicity and company-related services. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Service access is procedural and may require identity validation or paid certificates. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

3. SUNARP National Directory of Legal Persons

Authority: SUNARP. Type: official legal-person search. Access model: free monthly-updated search / directory. Reuse position: referential consultation; SUNARP publicity-search caveat.

Free reference route to check whether a legal person is registered or whether a name is already adopted. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: The page states the directory does not replace SUNARP index-search registry publicity. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

4. SUNARP free registry-partida consultation

Authority: SUNARP. Type: official registry document preview service. Access model: free online preview with DNI validation and viewing limits. Reuse position: referential consultation, no administrative/judicial value warning.

Document-level verification path for registry entries and acts. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Limited preview workflow; not a redistribution API or certified registry extract. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

5. SUNARP legal-person statistics

Authority: SUNARP. Type: official registry statistics. Access model: XLSX publications / statistical reports. Reuse position: official statistics/publication terms and attribution caution.

Business-demography and registry-activity context for legal-person categories. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Aggregate/statistical reports do not provide entity-level legal master data. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

6. SUNAT RUC search

Authority: SUNAT. Type: official tax identifier lookup. Access model: web search / known identifier or name workflows. Reuse position: tax-service terms, privacy and purpose-limitation caution.

RUC status and taxpayer verification for known entities. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Tax lookup is not a legal-register bulk file and is not marketing consent. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

7. SUNAT reduced RUC guide

Authority: SUNAT. Type: official tax bulk-download documentation. Access model: documentation / download guidance. Reuse position: SUNAT terms, tax-data and personal-data caution.

Explains the reduced RUC download route and use boundaries. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Reduced RUC fields are tax-registration context, not full corporate documents. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

8. SUNAT reduced RUC download

Authority: SUNAT. Type: official tax bulk download. Access model: download page. Reuse position: SUNAT terms, tax-data and personal-data caution.

Bulk tax-identifier context for entity resolution and status checks where lawful. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: The padron is reduced and tax-oriented; it does not replace SUNARP legal evidence. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

9. OECE open procurement data service

Authority: Organismo Especializado para las Contrataciones Publicas Eficientes. Type: official procurement open-data service. Access model: open-data portal / downloads. Reuse position: OECE/SEACE open-data terms and dataset-specific limitations.

Open datasets about public contracts, suppliers, consortia, entities and awards. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Procurement participants are not the whole company universe. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

10. SEACE orientation

Authority: OECE / SEACE. Type: official procurement system documentation. Access model: orientation / public procurement system guidance. Reuse position: public-procurement transparency and portal terms.

Context for supplier, procedure and award data recorded through SEACE. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: System records are procurement evidence, not legal-company registry records. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

11. RNP consultation

Authority: Registro Nacional de Proveedores. Type: official supplier register lookup. Access model: supplier-registration consultation. Reuse position: RNP consultation terms and supplier-data privacy caution.

Supplier eligibility and public-procurement registration context. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: RNP only covers public-procurement supplier status. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

12. Peru open-data policy page

Authority: Presidencia del Consejo de Ministros / Plataforma Nacional de Datos Abiertos. Type: official open-data portal policy. Access model: open-data orientation / portal route. Reuse position: government open-data model with personal-data exclusions and dataset-specific terms.

National policy and discovery context for open government datasets. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Direct catalogue pages can behave differently from this policy page and each dataset still needs review. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

13. INEI business demography

Authority: Instituto Nacional de Estadistica e Informatica. Type: official statistics / business demography. Access model: statistical compendium / reports. Reuse position: official statistics terms and attribution caution.

Market-size, creation and disappearance context based on the central business directory. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Statistical publications are not entity-level company master data. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

14. INEI Peru Business Structure 2024

Authority: INEI. Type: official statistics report. Access model: PDF report. Reuse position: official statistics publication terms and attribution caution.

Context on enterprise structure and the Central Directory of Companies and Establishments. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Aggregate PDF report, not reusable entity-level records. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

15. SBS supervised financial entities

Authority: Superintendencia de Banca, Seguros y AFP. Type: financial regulator directory. Access model: supervised-entity directory. Reuse position: regulator-publication terms and citation caution.

Financial-sector entity enrichment and supervised-status verification. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Sector-specific subset only. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

16. SMV

Authority: Superintendencia del Mercado de Valores. Type: securities regulator source. Access model: regulated-market information / supervision context. Reuse position: SMV publication and filing-specific terms.

Capital-markets and supervised-issuer context. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Regulated-market subset only; use filings separately where needed. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

17. Diario Oficial El Peruano

Authority: Empresa Peruana de Servicios Editoriales / Diario Oficial El Peruano. Type: official gazette / legal publication. Access model: official publication / legal notices. Reuse position: official-publication and document-specific terms.

Legal-publication and corporate-notice context. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: Gazette publication is event evidence, not a normalized company master. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

18. GLEIF LEI API

Authority: Global Legal Entity Identifier Foundation. Type: global legal-entity identifier API. Access model: API / open LEI data. Reuse position: GLEIF API and open-data terms.

LEI cross-checks for Peruvian entities in finance, KYB and compliance workflows. A production pipeline should store the original URL, access date, identifier, source owner, source-specific terms and parser version before this evidence is joined to a Peru company profile.

Limitations and operating notes: LEI coverage is a regulated/global subset and not comprehensive Peru company coverage. Treat this source as a defined evidence layer, not proof of complete coverage, official endorsement, unrestricted redistribution or contact permission.

Practical Manual, API and Bulk Options

1. Start with SUNARP for legal identity

Use SUNARP authority, directory and registry-publicity services to understand the legal-person record. The National Directory is useful for free referential checks, while registry-publicity workflows and partidas are needed for stronger evidence.

2. Use SUNAT as a tax identifier and matching layer

Use RUC search for individual validation and the reduced RUC download for controlled bulk matching. Store the download date and keep tax fields separate from legal-register fields. Do not treat the reduced RUC file as a complete corporate document source.

3. Add procurement and supplier evidence

OECE/SEACE open data and RNP can add supplier status, awards, procedures, consortia, orders and public-sector activity. This is highly valuable for B2B analytics, but it represents procurement participation rather than the full company universe.

4. Add statistics, regulator and gazette layers

INEI helps estimate business demography and market context. SBS and SMV identify regulated subsets. El Peruano can provide legal-publication evidence, and GLEIF adds a global LEI cross-check for entities that participate in LEI-covered workflows.

Held Source-Risk Findings

• Direct PNDA catalogue group route: the OECE group route on datosabiertos.gob.pe was unstable from this node, so the article links the stable gob.pe OECE service and keeps direct catalogue linking under review.
• Complete free SUNARP legal-company bulk claim: SUNARP has strong services, directory and statistics, but this cycle did not verify one complete unrestricted legal-company bulk file.
• SUNAT/RUC marketing-contact use: RUC data is tax and identifier evidence, not permission for outreach.

Missing Data Gaps

• Legal-register bulk: no complete unrestricted SUNARP legal-company bulk route was verified in this cycle.
• Certified documents: registry-publicity services, partida preview and certificates can have identity, viewing, fee or evidentiary limits.
• Tax-data semantics: SUNAT fields must be interpreted as tax-registration context, not full corporate history.
• Procurement coverage: OECE/SEACE and RNP are supplier/procurement layers, not comprehensive company registers.
• Regulator coverage: SBS and SMV cover financial and securities-market subsets only.
• Contact data: public evidence is not consent for email, phone or lead-list enrichment.

Recommended Data Model

• Entity core: normalized legal name, RUC where lawful, CompaniesData id, country, legal form, registry context and tax-status context.
• SUNARP evidence: directory/search result route, registry-publicity route, partida metadata, statistical category and access date.
• SUNAT evidence: RUC status, padron source date, taxpayer category and privacy flags.
• Procurement evidence: OECE/SEACE supplier, procedure, award, order, consortia and RNP status fields with separate provenance.
• Enrichment evidence: INEI, SBS, SMV, El Peruano and GLEIF rows joined by normalized name, RUC or other lawful identifiers.
• Risk flags: legal-bulk-not-proven, registry-publicity-required, tax-data-caution, procurement-only, regulator-only, contact-use-blocked and manual-review-required.

How CompaniesData Adds Value

CompaniesData turns Peru’s fragmented official-source stack into a practical dataset by normalizing legal names, RUC values, source dates, registry/procurement/regulator categories and update evidence. It keeps SUNARP legal evidence, SUNAT tax evidence, OECE/RNP supplier evidence, INEI statistics, SBS/SMV regulator records, El Peruano publication references and GLEIF identifiers as separate provenance layers.

For English and international users, CompaniesData.cloud is the preferred owned route: request a CompaniesData sample for Peru. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the preferred owned property. Contact-data enrichment remains separate from official company-data reuse.

No unsafe claim: this article can say Peru has useful SUNARP, SUNAT, OECE/SEACE, INEI, regulator, gazette and LEI sources. It should not imply that SUNARP or SUNAT provides one complete, unrestricted, marketing-ready company bulk file.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
SUNARP	Superintendencia Nacional de los Registros Publicos	services / publications / registry guidance	SUNARP service terms and registry-publicity limits	Authority page is not a bulk-data licence or full downloadable company register.
SUNARP online services	SUNARP	online service hub / registry procedures	service-specific terms and controlled-access caution	Service access is procedural and may require identity validation or paid certificates.
SUNARP National Directory of Legal Persons	SUNARP	free monthly-updated search / directory	referential consultation; SUNARP publicity-search caveat	The page states the directory does not replace SUNARP index-search registry publicity.
SUNARP free registry-partida consultation	SUNARP	free online preview with DNI validation and viewing limits	referential consultation, no administrative/judicial value warning	Limited preview workflow; not a redistribution API or certified registry extract.
SUNARP legal-person statistics	SUNARP	XLSX publications / statistical reports	official statistics/publication terms and attribution caution	Aggregate/statistical reports do not provide entity-level legal master data.
SUNAT RUC search	SUNAT	web search / known identifier or name workflows	tax-service terms, privacy and purpose-limitation caution	Tax lookup is not a legal-register bulk file and is not marketing consent.
SUNAT reduced RUC guide	SUNAT	documentation / download guidance	SUNAT terms, tax-data and personal-data caution	Reduced RUC fields are tax-registration context, not full corporate documents.
SUNAT reduced RUC download	SUNAT	download page	SUNAT terms, tax-data and personal-data caution	The padron is reduced and tax-oriented; it does not replace SUNARP legal evidence.
OECE open procurement data service	Organismo Especializado para las Contrataciones Publicas Eficientes	open-data portal / downloads	OECE/SEACE open-data terms and dataset-specific limitations	Procurement participants are not the whole company universe.
SEACE orientation	OECE / SEACE	orientation / public procurement system guidance	public-procurement transparency and portal terms	System records are procurement evidence, not legal-company registry records.
RNP consultation	Registro Nacional de Proveedores	supplier-registration consultation	RNP consultation terms and supplier-data privacy caution	RNP only covers public-procurement supplier status.
Peru open-data policy page	Presidencia del Consejo de Ministros / Plataforma Nacional de Datos Abiertos	open-data orientation / portal route	government open-data model with personal-data exclusions and dataset-specific terms	Direct catalogue pages can behave differently from this policy page and each dataset still needs review.
INEI business demography	Instituto Nacional de Estadistica e Informatica	statistical compendium / reports	official statistics terms and attribution caution	Statistical publications are not entity-level company master data.
INEI Peru Business Structure 2024	INEI	PDF report	official statistics publication terms and attribution caution	Aggregate PDF report, not reusable entity-level records.
SBS supervised financial entities	Superintendencia de Banca, Seguros y AFP	supervised-entity directory	regulator-publication terms and citation caution	Sector-specific subset only.
SMV	Superintendencia del Mercado de Valores	regulated-market information / supervision context	SMV publication and filing-specific terms	Regulated-market subset only; use filings separately where needed.
Diario Oficial El Peruano	Empresa Peruana de Servicios Editoriales / Diario Oficial El Peruano	official publication / legal notices	official-publication and document-specific terms	Gazette publication is event evidence, not a normalized company master.
GLEIF LEI API	Global Legal Entity Identifier Foundation	API / open LEI data	GLEIF API and open-data terms	LEI coverage is a regulated/global subset and not comprehensive Peru company coverage.

FAQ

Is Peru good for open company data?

Peru is useful, but controlled. SUNARP, SUNAT, OECE/SEACE, RNP, INEI, SBS, SMV, El Peruano and GLEIF provide strong official layers, but they do not form one simple unrestricted company bulk register.

Can I download Peru company data in bulk?

SUNAT provides a reduced RUC download that can help with tax-identifier matching. That is not the same as complete SUNARP legal-company bulk data.

Does SUNARP have a free company search?

Yes. The National Directory of Legal Persons is a free referential service and is described as monthly updated. It does not replace official registry-publicity index search or certified documents.

Can SUNAT RUC data replace SUNARP?

No. SUNAT is the tax identifier authority. Use it for RUC validation and tax context, while keeping SUNARP as the legal-register authority.

Are SEACE and RNP company registers?

No. They are procurement and supplier layers. They are valuable for public-sector sales and supplier analytics, but they cover procurement participants.

Can Peru public data be used for cold email?

Not automatically. Registry, tax, procurement and regulator evidence is not consent for marketing outreach.

Why use CompaniesData?

CompaniesData adds normalization, deduplication, source provenance, update tracking, risk flags and delivery formats across the official Peru source stack.

Official Sources

• SUNARP – Superintendencia Nacional de los Registros Publicos
• SUNARP online services – SUNARP
• SUNARP National Directory of Legal Persons – SUNARP
• SUNARP free registry-partida consultation – SUNARP
• SUNARP legal-person statistics – SUNARP
• SUNAT RUC search – SUNAT
• SUNAT reduced RUC guide – SUNAT
• SUNAT reduced RUC download – SUNAT
• OECE open procurement data service – Organismo Especializado para las Contrataciones Publicas Eficientes
• SEACE orientation – OECE / SEACE
• RNP consultation – Registro Nacional de Proveedores
• Peru open-data policy page – Presidencia del Consejo de Ministros / Plataforma Nacional de Datos Abiertos
• INEI business demography – Instituto Nacional de Estadistica e Informatica
• INEI Peru Business Structure 2024 – INEI
• SBS supervised financial entities – Superintendencia de Banca, Seguros y AFP
• SMV – Superintendencia del Mercado de Valores
• Diario Oficial El Peruano – Empresa Peruana de Servicios Editoriales / Diario Oficial El Peruano
• GLEIF LEI API – Global Legal Entity Identifier Foundation