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

The Philippines has one of the better official company-data source stacks in Southeast Asia, but it is not a single open bulk company register. A serious source map has to separate Securities and Exchange Commission corporation and partnership records, DTI business-name registration, Philippine Business Databank cross-register context, PhilGEPS procurement data, Open Data Philippines, IPOPHL intellectual-property records, financial-sector directories, insurance-regulator lists and GLEIF legal-entity identifiers.

This deep refresh is written for analysts, KYB teams, data buyers and market-research users who need a practical reference article rather than a thin directory page. It explains which Philippine sources are official, which are API or search friendly, which are procurement or sector-specific enrichment layers, and which claims remain blocked by API limits, Data Privacy Act considerations, source terms, registry fragmentation and marketing-contact rules.

The live CompaniesData article is already public at https://companiesdata.cloud/open-company-data-philippines.html, but the Wave 7 version predates the current editorial standard. The 2026-06-09 source recheck found 11 publication-safe official or high-quality sources, 4 held routes, no hard 404/410 failures and 5 clean critical SEC/BNRS/PhilGEPS routes. Held routes in this run are: DTI BNRS business-name search, DTI BNRS services, Philippine Statistics Authority, Insurance Commission regulated entities.

Key Takeaways

• Best core source: SEC is the central official source for corporations and partnerships, with API Marketplace, documentation, eSearch and eSPARC evidence.
• Registry split: DTI BNRS business names are not the same as SEC-registered corporations, and Philippine Business Databank is a cross-register discovery layer rather than a complete bulk file.
• Procurement strength: PhilGEPS notices and PhilGEPS Open Data analytics provide strong supplier and tender enrichment, but procurement suppliers are a subset.
• Controlled-source caution: BNRS, PSA and Insurance Commission routes were held in this automated run and should be manually verified before being used as clean links.
• Contact-data boundary: SEC, DTI, PhilGEPS, regulator and IP records are not permission to build unsolicited email, phone or sales-prospecting lists.

Editorial Methodology

The CompaniesData country method starts with official sources first. Each source is classified by authority, access model, reuse note, business use, limitation and live-check result. A link is used as clean evidence only when it returns stable content or data without an access challenge, hard 404/410, bot-protection page or misleading soft-block response.

For the Philippines, this means treating SEC, DTI, PhilGEPS, data.gov.ph, IPOPHL, BSP, Insurance Commission, PSA and GLEIF as separate layers. They are not interchangeable. SEC proves corporation and partnership registration context; DTI proves business-name registration context; PhilGEPS proves procurement participation; IPOPHL proves IP ownership; BSP and Insurance Commission prove regulated-sector status; GLEIF proves partial cross-border legal-entity identification.

Source logos and favicons in this draft are decorative trust cues only. They help readers scan the Resource Pack and Source Matrix, but the evidence remains the official URL, source owner, access model, reuse note and limitation. Any final publication must keep those fields visible on the page.

Coverage, Access and Update-Risk Analysis

SEC corporation and partnership layer: SEC API Marketplace is the most important route for structured company information because it describes official company-information APIs and package limits. SEC eSearch is the public search route and eSPARC is a registration workflow route. A deep article can be assertive that SEC is central, but it should not imply every SEC field is freely bulk-downloadable.

DTI business-name layer: DTI BNRS is relevant for business names and sole-proprietor-style registrations. It should not be merged into SEC corporation data without a source-type flag. In this run, the BNRS search and services routes returned 403 from the automated node, so they remain source-relevant but not publication-clean until manual browser QA clears them.

Cross-register layer: Philippine Business Databank is useful because it points toward cross-register identity across agencies. It is not a substitute for the SEC register, DTI BNRS, CDA records, LGU permits or tax records. Use it as discovery and matching context, with coverage and field-depth caveats.

Procurement layer: PhilGEPS is a high-value enrichment source. Procurement notices, supplier records and analytics help identify companies active in public-sector markets, but they are not a complete universe of Philippine businesses. Procurement fields should be stored in separate tables with tender, notice, supplier and award identifiers.

Open-data and statistics layer: Open Data Philippines supports public dataset discovery. PSA is a valuable statistics authority, but the PSA route was held in this automated run because it returned a challenge page. If PSA is used in a public refresh, use a verified stable page or keep it as manual-review context.

Regulator and IP layer: IPOPHL, BSP and Insurance Commission add sector and rights context. IPOPHL and BSP passed live QA; Insurance Commission was held. These layers enrich specific subsets and should not be used to infer full registry coverage.

LEI layer: GLEIF adds standardized legal-entity identifiers where Philippine entities have LEIs. LEI records are excellent for cross-border matching, but coverage is partial and weighted toward finance, multinational operations and regulated entities.

Reuse Checklist

• Authority check: store whether each field came from SEC, DTI, PBD, PhilGEPS, data.gov.ph, IPOPHL, PSA, BSP, Insurance Commission or GLEIF.
• Access-model check: mark API subscription, search, registration workflow, open-data catalogue, procurement portal, directory or public API.
• Licence and terms check: preserve dataset terms, API package limits, site terms and no-endorsement wording.
• Source-date check: keep access date, source update date where available, local ingestion date and parser version.
• Registry-split check: do not merge SEC corporations, DTI business names, cooperatives, LGU permits and PhilGEPS suppliers without source-type flags.
• Privacy check: flag officers, representatives, addresses, contact-like fields and natural-person-adjacent data for Data Privacy Act and GDPR-style review.
• Marketing check: treat registry identity and private contact enrichment as different products with different lawful-basis requirements.
• Bulk-claim check: do not state that a complete free official company-register bulk file exists unless a source proves it directly.

Resource Pack

Source-by-Source Deep Dives

1. SEC API Marketplace

Authority: Securities and Exchange Commission Philippines. Type: official company API marketplace. Access model: API subscription / free and paid packages. Reuse note: SEC API terms and Data Privacy Act caveats.

Company information lookup, registration status, addresses, SEC numbers, filings and reportorial context. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: API limits, subscription tiers and source terms apply; not a free complete bulk database. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

2. SEC API documentation

Authority: Securities and Exchange Commission Philippines. Type: official API documentation. Access model: PDF / API documentation. Reuse note: SEC API terms.

Field and endpoint evidence for official company-information APIs. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Documentation only; endpoint access and quotas are controlled by SEC API terms. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

3. SEC eSearch

Authority: Securities and Exchange Commission Philippines. Type: official company search. Access model: search / electronic SEC records. Reuse note: SEC eSearch terms and Data Privacy Act limits.

Corporation and partnership verification through official SEC search. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Search access; document retrieval and API access may be separate products. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

4. SEC eSPARC

Authority: Securities and Exchange Commission Philippines. Type: official company-registration workflow. Access model: registration / e-services portal. Reuse note: SEC service terms.

Company registration workflow context for corporations and partnerships. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Registration service, not a reusable company master file. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

5. Philippine Business Databank

Authority: Philippine government business portal. Type: official cross-register business databank. Access model: search / business repository. Reuse note: PBD site terms and Data Privacy Act limits.

Cross-registry business identity context across DTI, SEC, CDA and LGUs. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Coverage, field depth and update cadence need source-by-source verification. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

6. PhilGEPS notices portal

Authority: Philippine Government Electronic Procurement System. Type: official procurement portal. Access model: portal / notices / supplier procurement context. Reuse note: PhilGEPS terms.

Tender, award and procurement-participant enrichment. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Procurement-only layer; suppliers are not the full registered-company universe. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

7. PhilGEPS Open Data analytics

Authority: Philippine Government Electronic Procurement System. Type: official procurement open-data analytics. Access model: open-data analytics / supplier and tender reports. Reuse note: PhilGEPS open-data and portal terms.

Open procurement metrics, notices and supplier/award context. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Procurement analytics layer, not company-register master data. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

8. Open Data Philippines

Authority: Government of the Philippines. Type: official open-data portal. Access model: catalogue / datasets. Reuse note: dataset-specific open-data terms.

National open-data discovery and public-sector dataset context. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Company microdata may be limited or absent; dataset terms control reuse. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

9. IPOPHL

Authority: Intellectual Property Office of the Philippines. Type: official intellectual-property office. Access model: search / services / publications. Reuse note: IPOPHL website and database terms.

Trademark, patent and design enrichment for entity resolution. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: IP records are a separate rights layer, not company-register status. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

10. BSP directories

Authority: Bangko Sentral ng Pilipinas. Type: financial regulator directories. Access model: directories / supervised financial institutions. Reuse note: BSP website terms.

Bank and supervised financial institution enrichment. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: Sector-specific and not the general company register. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

11. GLEIF LEI records for the Philippines

Authority: global official LEI system. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions.

Cross-border legal-entity identifier enrichment for Philippine entities with LEIs. For CompaniesData ingestion, store the official URL, access date, source owner, field-level provenance, API or search-route limitation and update cadence before joining this source to another Philippine entity layer.

Limitation: LEI coverage is partial and skewed toward financial/cross-border entities. Treat this as one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness, unrestricted redistribution or contact-data permission.

Practical Manual, API and Bulk Options

1. SEC API Marketplace route

Use SEC API Marketplace and the SEC API documentation as the structured company-information route. Record the API package, endpoint description, allowed use, quota, pricing or free-tier details, authentication requirements and the exact fields returned. This is the strongest API story, but it is still an API product with limits.

2. SEC eSearch and eSPARC route

Use SEC eSearch for verification and eSPARC for registration-workflow context. These routes support the article’s explanation of official SEC authority, but they should not be presented as bulk-download sources. If a workflow requires documents, filings or certificates, document whether those are public, paid, API-based or manual.

3. DTI BNRS route

Use DTI BNRS for business-name context after manual browser QA clears the current 403 behavior. The article should clearly tell readers that DTI business names are not the same as SEC legal-company registration. The data model should preserve both layers and only merge records when identifiers and names are confidence-matched.

4. Philippine Business Databank route

Use Philippine Business Databank as a cross-register discovery source. It is especially useful for explaining why Philippine company data needs normalization: a business can appear in different government systems with different identifiers, names, addresses, registrations and status fields.

5. PhilGEPS route

Use PhilGEPS notices and Open Data analytics for procurement enrichment. Store tender identifiers, agencies, supplier names, classifications, notices, awards and publication dates separately from core company identity. Supplier participation is a business signal, not proof that the supplier list is the national company register.

6. Enrichment route

Use Open Data Philippines, IPOPHL, BSP, Insurance Commission, PSA and GLEIF as enrichment sources where each route is stable. Each source adds useful context, but each has a specific scope. A production dataset should carry explicit coverage flags such as procurement-only, IP-only, financial-regulated, insurance-regulated, statistics-only or LEI-only.

Held Source-Risk Findings

• DTI BNRS search and services: returned 403 in automated QA. Keep as source-relevant, but verify manually before clean publication.
• Philippine Statistics Authority: returned a challenge page. Use only after a stable source page clears crawl and bot-profile QA.
• Insurance Commission regulated entities: returned a challenge page. Keep held until a stable directory route is verified.
• Complete-bulk claim: blocked. The clean sources support strong API/search/procurement/enrichment discussion, not a single unrestricted full-register bulk file.
• Contact-use claim: blocked. Public authority records do not create permission for unsolicited outreach.

Missing-Data Gaps

• Full register bulk: no clean source in this run proves a complete, free, official full-register bulk company database.
• Beneficial ownership: do not claim complete beneficial-owner visibility from the clean source stack.
• Document images and filings: SEC document access, eSearch and API coverage can differ by product, package and workflow.
• Local permits: LGU permits and local licensing may sit outside SEC, DTI and PhilGEPS source coverage.
• Contact fields: emails, phones, roles and outreach-ready contacts require a separate compliant contact-data workflow.
• Source freshness: API, search, procurement and directory pages can update on different schedules.

Recommended Data Model

• Entity table: CompaniesData id, source legal name, normalized legal name, country, source authority, source type, source URL and access date.
• SEC table: SEC number, registration status, entity type, official address, filing/API source, API package note and last-checked date.
• DTI table: business name, registration scope, BN status, BNRS source route, exact-name-search limitation and manual-review flag.
• Cross-register table: PBD identifiers, matched agency, matched name, confidence score and source-of-match notes.
• Procurement table: PhilGEPS notice id, opportunity id, agency, supplier, tender title, award status, publication date and procurement subset flag.
• IP table: IPOPHL mark or patent identifier, owner string, class/category, status and matching confidence.
• Regulator table: BSP or insurance-regulated entity name, licence category, regulator URL, status and sector flag.
• LEI table: LEI, legal name, registration status, managing LOU, GLEIF update timestamp and Philippine subset flag.
• Compliance flags: API-subscription, paid-document, exact-name-search-only, procurement-only, regulated-sector-only, privacy-review, contact-use-blocked and manual-review-required.

CompaniesData Normalization and Enrichment Value

The Philippines has useful official sources, but users still need a normalization layer. CompaniesData.cloud can turn fragmented SEC, DTI, PBD, PhilGEPS, IPOPHL, BSP and GLEIF records into a practical dataset with consistent names, source provenance, update tracking, confidence scores and lawful-use notes. The goal is not to pretend that every portal is open bulk data; the value is to preserve what each source proves and make the combined record usable.

For English and international audiences, CompaniesData.cloud is the owned route for company datasets and compliant enrichment context. Request a CompaniesData sample for the Philippines if you need normalized fields rather than a manual list of portals. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the owned route, but that private contact layer remains separate from official registry reuse.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
SEC API Marketplace	Securities and Exchange Commission Philippines	API subscription / free and paid packages	SEC API terms and Data Privacy Act caveats	API limits, subscription tiers and source terms apply; not a free complete bulk database.
SEC API documentation	Securities and Exchange Commission Philippines	PDF / API documentation	SEC API terms	Documentation only; endpoint access and quotas are controlled by SEC API terms.
SEC eSearch	Securities and Exchange Commission Philippines	search / electronic SEC records	SEC eSearch terms and Data Privacy Act limits	Search access; document retrieval and API access may be separate products.
SEC eSPARC	Securities and Exchange Commission Philippines	registration / e-services portal	SEC service terms	Registration service, not a reusable company master file.
Philippine Business Databank	Philippine government business portal	search / business repository	PBD site terms and Data Privacy Act limits	Coverage, field depth and update cadence need source-by-source verification.
PhilGEPS notices portal	Philippine Government Electronic Procurement System	portal / notices / supplier procurement context	PhilGEPS terms	Procurement-only layer; suppliers are not the full registered-company universe.
PhilGEPS Open Data analytics	Philippine Government Electronic Procurement System	open-data analytics / supplier and tender reports	PhilGEPS open-data and portal terms	Procurement analytics layer, not company-register master data.
Open Data Philippines	Government of the Philippines	catalogue / datasets	dataset-specific open-data terms	Company microdata may be limited or absent; dataset terms control reuse.
IPOPHL	Intellectual Property Office of the Philippines	search / services / publications	IPOPHL website and database terms	IP records are a separate rights layer, not company-register status.
BSP directories	Bangko Sentral ng Pilipinas	directories / supervised financial institutions	BSP website terms	Sector-specific and not the general company register.
GLEIF LEI records for the Philippines	global official LEI system	public API	GLEIF open data licence with attribution and no-endorsement conditions	LEI coverage is partial and skewed toward financial/cross-border entities.

FAQ

What is the best first source for company data in the Philippines?

Start with the SEC for corporations and partnerships. SEC API Marketplace, API documentation, eSearch and eSPARC give the strongest official SEC route. Then add DTI BNRS for business names, PhilGEPS for procurement suppliers, and enrichment sources such as IPOPHL, BSP and GLEIF.

Is there a single free official bulk company database for the Philippines?

Not from the clean source set in this recheck. The Philippines has official APIs, search routes, procurement data and open-data context, but a complete free full-register bulk file should not be claimed unless a specific official source proves it.

How should SEC and DTI data be combined?

Keep them separate first. SEC records relate to corporations and partnerships, while DTI BNRS records relate to business names. A normalized dataset can match names and identifiers, but it should retain source type, confidence score and manual-review flags.

Can PhilGEPS be used as a company database?

PhilGEPS is a procurement source. It is excellent for tender, award and supplier enrichment, but it covers a procurement subset and should not be treated as the full company universe.

Can public registry data be used for cold email or phone outreach?

No automatic permission follows from public access. Outreach requires a separate lawful basis, suppression handling, opt-out workflow and privacy review. Registry identity and private contact-data enrichment should remain separate.

Why use CompaniesData instead of manual source collection?

Manual collection is slow because source types, identifiers, names, access models and update schedules differ. CompaniesData adds normalization, deduplication, provenance, source-risk flags, enrichment matching and practical delivery formats.

Official Sources

• SEC API Marketplace – Securities and Exchange Commission Philippines
• SEC API documentation – Securities and Exchange Commission Philippines
• SEC eSearch – Securities and Exchange Commission Philippines
• SEC eSPARC – Securities and Exchange Commission Philippines
• Philippine Business Databank – Philippine government business portal
• PhilGEPS notices portal – Philippine Government Electronic Procurement System
• PhilGEPS Open Data analytics – Philippine Government Electronic Procurement System
• Open Data Philippines – Government of the Philippines
• IPOPHL – Intellectual Property Office of the Philippines
• BSP directories – Bangko Sentral ng Pilipinas
• GLEIF LEI records for the Philippines – global official LEI system