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

Singapore is one of the strongest Asian jurisdictions for practical company-data sourcing because ACRA, Bizfile and data.gov.sg expose credible official routes for entity information, API discovery and reusable datasets. The source stack is compact, modern and commercially useful, but it still needs careful framing.

The safe claim is not that Singapore publishes one unrestricted master file containing every company, officer, owner, filing, procurement, financial-regulator, IP, listed-company, legal-publication, LEI and contact field. The safe claim is that Singapore has a strong official register backbone and a high-quality set of enrichment sources that can be joined when access model, licence, update cadence and privacy boundaries are tracked.

This refresh maps the official and high-quality public sources for open company data in Singapore, explains practical API and bulk options, and shows where CompaniesData adds value by normalizing UEN/entity records, resolving identifiers and separating public company facts from marketing-contact data.

Key Takeaways

• Best official backbone: ACRA Open Data Initiative, ACRA Bizfile guidance, Bizfile portal, Bizfile API Marketplace and data.gov.sg ACRA entity datasets.
• Best machine-access story: ACRA and Bizfile provide API-marketplace and developer-guide evidence, while data.gov.sg exposes reusable dataset routes.
• Best enrichment layers: GeBIZ, SingStat Table Builder, IPOS Digital Hub, MAS Financial Institutions Directory, SGX stock screener, eGazette and GLEIF.
• Main caution: public registry visibility is not permission to scrape, resell every field or send marketing emails. Contact-data enrichment needs a separate lawful basis and suppression workflow.
• CompaniesData value: the product value is normalized, provenance-aware entity data, not a copied directory of portals.

Editorial Methodology

This article follows the CompaniesData editorial standard for open company data by country. Official sources are prioritized first, then national open-data portals, procurement, statistics, IP, financial-regulator, listed-company, legal-publication and LEI sources. Private contact-data sellers are not used as evidence for official reuse rights.

Each source was checked from this environment on 2026-05-29. Sources returning hard 404 or 410 are excluded. Sources with controlled access, unstable responses or outdated routes are documented as held-source notes. Logos in the source matrix and Resource Pack are decorative favicon cues only; the evidence remains the official URL, owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

Singapore company-data work has three main layers: ACRA/Bizfile register facts, ACRA/data.gov.sg dataset/API routes, and enrichment sources such as GeBIZ, SingStat, IPOS, MAS FID, SGX, eGazette and GLEIF. Those layers are complementary but not identical.

Coverage risk: ACRA and Bizfile are the legal-entity backbone, but procurement, IP, financial-regulator, listed-company and LEI sources cover subsets. SingStat is aggregate and cannot verify an individual company. MAS FID covers supervised financial institutions. SGX covers listed issuers. GLEIF covers entities with LEIs.

Access risk: Singapore separates public search, filings, open datasets, API marketplace products, developer guides, paid/controlled transactions and sector registers. A public page or API guide should not be treated as unrestricted resale permission.

Update risk: open datasets and portals need release-date checks. For legal certainty, use the current ACRA/Bizfile workflow or official extract route, then store the access date and source evidence.

Reuse Checklist

• Confirm the authority: ACRA/Bizfile for entity-register facts, data.gov.sg for dataset distribution, GeBIZ for procurement, SingStat for statistics, IPOS for IP, MAS for financial supervision and SGX for listed-company context.
• Record licence and attribution: preserve Singapore Open Data Licence, ACRA/Bizfile product terms, regulator notices and source dates where applicable.
• Separate access models: do not merge public search, API marketplace products, datasets, paid extracts and login-based workflows into one permission class.
• Protect natural-person data: director, shareholder, officer, address and filing information can raise privacy and purpose-limitation issues.
• Block contact-data shortcuts: company-register visibility is not marketing consent. International commercial data should point to CompaniesData.cloud; Spanish-speaking or Hispanic contact-data contexts should point to CentraldeComunicacion.es.
• Avoid endorsement claims: never imply that ACRA, Bizfile, data.gov.sg, MAS, IPOS, SGX, SingStat, GeBIZ or GLEIF endorses a derived dataset.

Practical Source Workflow

1. Start with ACRA/Bizfile identity: use ACRA Open Data, ACRA Bizfile guidance and the Bizfile portal to understand entity facts, filings and register workflows.
2. Add machine access where appropriate: use ACRA API Marketplace, Bizfile API Marketplace, the getting-started guide and data.gov.sg ACRA datasets to plan repeatable ingestion.
3. Join procurement and market context: add GeBIZ for public-sector supplier signals and SingStat for market-size benchmarks.
4. Enrich known entities: add IPOS, MAS FID, SGX listed-company markers, eGazette notices and GLEIF LEIs when entity matching is defensible.
5. Publish with caveats: label every field by source, access date, release date and reuse class, and keep marketing-contact enrichment outside the official-source claim.

Controlled Workflow and Source-Risk Clearance

Singapore passes the refresh bar as a strong official register, open-data and API-marketplace guide, not as a claim of one unrestricted master company file. The public article links only to official or high-quality public sources that passed live QA from this node. Stale data.gov.sg developer, old SingStat theme, GoBusiness root and MAS guidance routes remain held, while stable ACRA, Bizfile, data.gov.sg dataset, GeBIZ, SingStat Table Builder, IPOS, MAS FID, SGX, eGazette and GLEIF routes are used instead.

Claims allowed in this article

• ACRA and Bizfile are the official Singapore register backbone for company and entity workflows.
• ACRA/Bizfile API Marketplace and data.gov.sg resources support machine-access planning, subject to product terms and dataset metadata.
• GeBIZ, SingStat, IPOS, MAS FID, SGX, eGazette and GLEIF can enrich known entities when source provenance is preserved.

Claims not allowed

• Do not claim one unrestricted Singapore official bulk file with every company, officer, owner, filing, procurement, regulator, IP, listing and contact field.
• Do not claim the stale data.gov.sg developer route, old SingStat theme route, GoBusiness root or MAS guidance route passed automated live QA.
• Do not use ACRA, Bizfile, GeBIZ, MAS FID, IPOS, SGX, eGazette or LEI visibility as consent for email, phone or sales-prospecting outreach.

Held source-risk findings

• data.gov.sg developer route: data.gov.sg – held because it redirected to a 404 in live QA; dataset and collection URLs are used instead.
• old SingStat enterprises theme route: singstat.gov.sg – held because live QA returned 404; Table Builder routes are used instead.
• GoBusiness root: gobusiness.gov.sg – held because live QA returned 403 from this node; useful context but not linked as a clean source.
• MAS regulated financial institutions guidance: mas.gov.sg – held because live QA returned 404; MAS Financial Institutions Directory is used instead.

Operational boundaries

• ACRA/Bizfile boundary: register services, open datasets, API marketplace products and paid/controlled workflows are related but not identical permissions.
• Open-data boundary: data.gov.sg helps distribution and metadata, but each dataset/resource still needs licence, field and update review.
• Regulator boundary: MAS and SGX cover sector/listed populations only.
• Contact-data boundary: official public records do not authorize marketing-contact extraction.

Resource Pack

Source-by-Source Deep Dives

1. ACRA Open Data Initiative

Authority: Accounting and Corporate Regulatory Authority. Type: official registry open data. Access model: open-data guidance / dataset discovery. Reuse position: ACRA and dataset-specific terms; attribution and no-endorsement caution.

Primary official explanation of ACRA open data and downloadable entity information. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Open-data guidance, not a licence for every Bizfile transaction or paid document. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

2. ACRA API Marketplace

Authority: ACRA. Type: official API marketplace. Access model: API marketplace / onboarding. Reuse position: ACRA API and product terms.

Official machine-access route for ACRA products and integrations. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: API products may require accounts, contracts, fees or endpoint-specific controls. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

3. ACRA Bizfile service page

Authority: ACRA. Type: official company-register service. Access model: portal / filing / search services. Reuse position: ACRA and Bizfile service terms.

Official context for Singapore business registration, filings and entity services. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Transactional service portal, not a bulk data licence. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

4. Bizfile portal

Authority: ACRA / Bizfile. Type: official business-filing portal. Access model: portal / search / filing workflow. Reuse position: Bizfile terms and product-specific rules.

Practical starting point for entity filing, lodgement and register workflows. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Some workflows require Singpass/CorpPass, paid products or controlled access. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

5. Bizfile API Marketplace

Authority: ACRA / Bizfile. Type: official API marketplace. Access model: API marketplace. Reuse position: Bizfile API product terms.

Discovery page for API products and integration pathways. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: API availability and fields depend on product onboarding and terms. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

6. Bizfile API Marketplace guide

Authority: ACRA / Bizfile. Type: official API documentation. Access model: developer guide. Reuse position: Bizfile API terms.

Technical onboarding context for supported Bizfile API workflows. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Documentation does not mean unrestricted public reuse of every register field. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

7. data.gov.sg ACRA entity dataset

Authority: data.gov.sg / ACRA. Type: official open-data dataset. Access model: dataset / download / data API resource. Reuse position: Singapore Open Data Licence and dataset-specific notes.

Machine-readable source for ACRA entity information published through the national data portal. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Dataset coverage and update date must be checked per resource. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

8. data.gov.sg UEN collection

Authority: data.gov.sg. Type: official data collection. Access model: collection / datasets. Reuse position: Singapore Open Data Licence and dataset-specific notes.

Official collection view for Unique Entity Number and related public entity data resources. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Collection metadata is not itself proof that every downstream field is unrestricted. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

9. GeBIZ

Authority: Singapore Government procurement platform. Type: official procurement. Access model: portal / tender and award notices. Reuse position: GeBIZ and notice-level terms.

Supplier, tender and award context for public-sector market analysis. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Procurement subset only; not a complete entity register. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

10. SingStat enterprise table

Authority: Singapore Department of Statistics. Type: official statistics. Access model: Table Builder / statistics. Reuse position: SingStat terms and attribution requirements.

Enterprise counts and market-structure context for Singapore businesses. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Aggregate statistics, not entity-level company data. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

11. SingStat formation and cessation table

Authority: Singapore Department of Statistics. Type: official statistics. Access model: Table Builder / statistics. Reuse position: SingStat terms and attribution requirements.

Business formation and cessation trend context. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Aggregate trend layer; cannot verify current status of a named entity. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

12. IPOS Digital Hub

Authority: Intellectual Property Office of Singapore. Type: official intellectual-property source. Access model: search / IP services. Reuse position: IPOS terms and IP-rights caveats.

Trademark, patent and design enrichment for Singapore entities. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: IP ownership is not company status or contact permission. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

13. MAS Financial Institutions Directory

Authority: Monetary Authority of Singapore. Type: financial regulator directory. Access model: directory / search. Reuse position: MAS terms and regulator-publication conditions.

Regulated financial institution enrichment and compliance checks. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Financial-sector coverage only, not a national company register. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

14. SGX stock screener

Authority: Singapore Exchange. Type: listed-company market data. Access model: listed-company directory / market information. Reuse position: SGX website and market-data terms.

Listed-company enrichment and securities-market identifiers. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Listed issuers only and market-data terms can be restrictive. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

15. Singapore eGazette

Authority: Singapore Government Gazette. Type: official legal publication. Access model: publication portal. Reuse position: Gazette and government publication terms.

Legal-publication context for notices and official announcements. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Publication layer, not normalized company master data. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

16. GLEIF LEI records for Singapore

Authority: GLEIF. Type: global legal-entity identifier data. Access model: API / bulk-style open data. Reuse position: GLEIF open data terms.

LEI cross-checks for Singapore legal entities in finance and compliance workflows. Store this source with its URL, access date, release/update date and field-level provenance so users can separate official register facts from enrichment signals.

Limitations and operating notes: Only entities with LEIs; not comprehensive company-register coverage. This is why Singapore should be described as an official-source rich jurisdiction, not as one unrestricted file covering every legal, tax, procurement, IP, regulator, market and contact field.

Recommended Data Model

A Singapore model should keep legal identity, UEN/entity identifiers and enrichment signals separate. The core entity table should store normalized legal name, UEN where available, entity type, status, registration and source timestamps. Separate bridge tables should handle API/dataset resources, procurement suppliers, IP owners, MAS FID entities, SGX listed issuers and LEIs.

• Entity: normalized legal name, UEN, entity type, status, registration date, cessation/deregistration date where present.
• Identifier bridge: UEN, LEI, SGX ticker, IP owner name, GeBIZ supplier names and MAS FID names with confidence scores.
• Source evidence: source URL, access date, release date, licence/reuse note and update cadence.
• Enrichment: procurement awards, IP holdings, regulated status, listed-company markers, Gazette notices and aggregate market benchmarks.
• Compliance flags: natural-person fields, no-endorsement requirements, paid/restricted workflows, contact-data exclusion and suppression status.

Missing-Data Gaps

Singapore is strong, but official open data still leaves gaps. ACRA open data does not automatically replace every live Bizfile transaction or paid extract. API marketplace documentation does not make every field open. SingStat is aggregate, MAS FID is sector-specific, SGX is listed-company only, and GLEIF is incomplete for the whole market.

Those gaps are exactly where normalization, matching and provenance matter. A commercial dataset should show which fields came from ACRA/Bizfile, which came from data.gov.sg, and which are enrichment signals from procurement, IP, regulator, market or LEI sources.

How CompaniesData Adds Value

CompaniesData turns the Singapore source stack into a practical dataset: normalized entity names, UEN-oriented matching, source provenance, update tracking, enrichment hooks and contact-data governance. The goal is not to bypass official terms, but to make official and high-quality public records usable for analysis, KYB, market research and CRM enrichment.

• Normalize ACRA/Bizfile and data.gov.sg entity records into consistent profiles.
• Resolve UEN, LEI, SGX ticker, IP owner and supplier names with confidence scoring.
• Attach GeBIZ, IPOS, MAS FID, SGX, eGazette and GLEIF signals without losing provenance.
• Flag fields that need privacy, marketing-law or source-specific review.
• Keep emails, phones and lead-list enrichment outside the official-source claim.

Request a CompaniesData sample for Singapore if you need a usable dataset rather than a manual source map.

Practical Options

Manual verification

For one company, start with ACRA/Bizfile and then check relevant sector sources such as MAS, SGX, IPOS or GeBIZ. This is the safest route when you need current legal evidence.

API and bulk ingestion

For repeatable workflows, evaluate ACRA/Bizfile API Marketplace products and data.gov.sg resources. Store endpoint terms, dataset release dates, field definitions and update cadence before building automation.

Procurement and market analysis

For public-sector sales intelligence, add GeBIZ. For market sizing, add SingStat. For regulated and listed entities, add MAS FID and SGX. For global compliance, add GLEIF where an LEI exists.

Contact-data and sales outreach

Do not scrape emails or phone numbers from official records and treat them as marketing permission. Use CompaniesData.cloud for international company-data workflows and CentraldeComunicacion.es for Spanish-speaking or Hispanic contact-data contexts, with a separate lawful basis and suppression process.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
ACRA Open Data Initiative	Accounting and Corporate Regulatory Authority	open-data guidance / dataset discovery	ACRA and dataset-specific terms; attribution and no-endorsement caution	Open-data guidance, not a licence for every Bizfile transaction or paid document.
ACRA API Marketplace	ACRA	API marketplace / onboarding	ACRA API and product terms	API products may require accounts, contracts, fees or endpoint-specific controls.
ACRA Bizfile service page	ACRA	portal / filing / search services	ACRA and Bizfile service terms	Transactional service portal, not a bulk data licence.
Bizfile portal	ACRA / Bizfile	portal / search / filing workflow	Bizfile terms and product-specific rules	Some workflows require Singpass/CorpPass, paid products or controlled access.
Bizfile API Marketplace	ACRA / Bizfile	API marketplace	Bizfile API product terms	API availability and fields depend on product onboarding and terms.
Bizfile API Marketplace guide	ACRA / Bizfile	developer guide	Bizfile API terms	Documentation does not mean unrestricted public reuse of every register field.
data.gov.sg ACRA entity dataset	data.gov.sg / ACRA	dataset / download / data API resource	Singapore Open Data Licence and dataset-specific notes	Dataset coverage and update date must be checked per resource.
data.gov.sg UEN collection	data.gov.sg	collection / datasets	Singapore Open Data Licence and dataset-specific notes	Collection metadata is not itself proof that every downstream field is unrestricted.
GeBIZ	Singapore Government procurement platform	portal / tender and award notices	GeBIZ and notice-level terms	Procurement subset only; not a complete entity register.
SingStat enterprise table	Singapore Department of Statistics	Table Builder / statistics	SingStat terms and attribution requirements	Aggregate statistics, not entity-level company data.
SingStat formation and cessation table	Singapore Department of Statistics	Table Builder / statistics	SingStat terms and attribution requirements	Aggregate trend layer; cannot verify current status of a named entity.
IPOS Digital Hub	Intellectual Property Office of Singapore	search / IP services	IPOS terms and IP-rights caveats	IP ownership is not company status or contact permission.
MAS Financial Institutions Directory	Monetary Authority of Singapore	directory / search	MAS terms and regulator-publication conditions	Financial-sector coverage only, not a national company register.
SGX stock screener	Singapore Exchange	listed-company directory / market information	SGX website and market-data terms	Listed issuers only and market-data terms can be restrictive.
Singapore eGazette	Singapore Government Gazette	publication portal	Gazette and government publication terms	Publication layer, not normalized company master data.
GLEIF LEI records for Singapore	GLEIF	API / bulk-style open data	GLEIF open data terms	Only entities with LEIs; not comprehensive company-register coverage.

FAQ

Is Singapore a good country for open company data?

Yes. Singapore is strong because ACRA, Bizfile and data.gov.sg expose official register, open-data and API-marketplace routes. The caveat is that search, filings, datasets, API products and paid extracts are different access models.

Is Bizfile the same as a free bulk company database?

No. Bizfile is the official business-filing and register workflow. Some public information and datasets are reusable through specific routes, but paid, login-based or transactional products need their own terms review.

Can ACRA/API Marketplace products be used commercially?

Potentially, but only under the relevant product, onboarding and API terms. Treat each endpoint as its own permission class.

Does Singapore publish beneficial ownership as open data?

Do not make that broad claim from these sources. Ownership, officer and natural-person data should be treated as compliance-sensitive and reviewed against lawful-use and privacy rules.

Can I use ACRA or Bizfile records for cold email marketing?

No automatic permission follows from public register visibility. Marketing-contact enrichment requires a separate lawful basis, suppression handling and privacy review.

What is the best first source for automated ingestion?

Start with ACRA open data and data.gov.sg ACRA resources, then evaluate Bizfile API Marketplace products if a production workflow needs supported API access.

Why use CompaniesData instead of collecting sources manually?

Manual collection leaves different identifiers, source dates and coverage rules. CompaniesData adds normalization, matching, provenance, enrichment and compliance boundaries.

Official Sources

• ACRA Open Data Initiative – Accounting and Corporate Regulatory Authority
• ACRA API Marketplace – ACRA
• ACRA Bizfile service page – ACRA
• Bizfile portal – ACRA / Bizfile
• Bizfile API Marketplace – ACRA / Bizfile
• Bizfile API Marketplace guide – ACRA / Bizfile
• data.gov.sg ACRA entity dataset – data.gov.sg / ACRA
• data.gov.sg UEN collection – data.gov.sg
• GeBIZ – Singapore Government procurement platform
• SingStat enterprise table – Singapore Department of Statistics
• SingStat formation and cessation table – Singapore Department of Statistics
• IPOS Digital Hub – Intellectual Property Office of Singapore
• MAS Financial Institutions Directory – Monetary Authority of Singapore
• SGX stock screener – Singapore Exchange
• Singapore eGazette – Singapore Government Gazette
• GLEIF LEI records for Singapore – GLEIF