Singapore Government Data API avatar

Singapore Government Data API

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Singapore Government Data API

Singapore Government Data API

Search Singapore business, housing, procurement, health, and court datasets in one run. Get structured Singapore records fast.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

kane liu

kane liu

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

10 days ago

Last modified

Share

Singapore Government Data Search

Search Singapore business, housing, procurement, health, and court datasets in one run — without checking six separate government portals yourself.

  • ✅ Search 6 Singapore government sources across ACRA, HDB, GeBIZ, MOH, and the Singapore Courts
  • ✅ Pull business entities, HDB resale records, procurement awards, inpatient capacity data, MOH portal links, and judgments-hub links
  • ✅ Use one search term across all sources and get back structured rows you can export
  • ✅ Pay only for what you use: $0.003 per record
  • ✅ Free $5 Apify credit on signup = ~1,600 records to start with

If you need to verify a Singapore company, check HDB resale activity in a town, look up GeBIZ awards, or pull MOH and judiciary references for downstream research, the slow part is never the data itself. The slow part is jumping between different portals, different schemas, and different search flows. This Actor turns that into one search box and one export.


What you can do with it

1. Verify a Singapore company by name or UEN

If you work with suppliers, vendors, or counterparties in Singapore, the first question is usually simple: does this entity exist, and what status is it in? The ACRA source inside this Actor lets you search registered entities by company name or UEN and pull back the core registry details you normally have to hunt down manually.

To run this, all you fill in are two simple fields in the Apify input form at the top of this page:

What you enter:

WhatExample
Search termsDBS
Max results per source20

Click Start. Within seconds, the Actor queries the Singapore ACRA dataset and returns matching business rows:

What you get back:

UENBusiness nameEntity typeStatusIssue date
196800306EDBS BANK LTD.Public Company Limited by SharesRegistered1968-01-01
53012345XDBS CONSULTING PTE. LTD.Exempt Private Company Limited by SharesRegistered2009-07-14
53345678MDBS DIGITAL SERVICES LLPLimited Liability PartnershipRegistered2021-03-02

This is the quickest way to do a first-pass Singapore company check before a deeper KYB or sourcing workflow. Instead of checking BizFile, copying rows, and normalizing the fields yourself, you start with one clean export.


2. Check HDB resale activity by town, block, or street

If you are researching neighborhoods, pricing trends, or public-housing turnover in Singapore, HDB resale records are one of the easiest ways to ground the discussion in actual transactions. Search a town name or a street, and this Actor pulls matching resale rows from the HDB dataset without you having to filter the data.gov.sg portal yourself.

Here is a simple example:

What you enter:

WhatExample
Search termsTampines
Max results per source50

The Actor searches HDB resale records and returns transaction rows like these:

What you get back:

MonthTownFlat typeStreetFloor areaPrice
2026-02TAMPINES4 ROOMTAMPINES ST 2192 sqmS$538,000
2026-02TAMPINES5 ROOMTAMPINES AVE 4113 sqmS$675,000
2026-01TAMPINESEXECUTIVETAMPINES ST 43146 sqmS$810,000

This is useful for market scans, content research, internal dashboards, and quick pricing sanity checks. You are not building a full valuation model here. You are answering practical questions faster: what is trading in this area, in what flat types, and at what price range?


3. Pull Singapore government procurement awards from GeBIZ

If you sell into Singapore government agencies, track public spending, or study supplier activity, the GeBIZ awards source gives you a fast way to search award-level procurement rows. That means tender number, agency, supplier name, award date, and awarded amount in Singapore dollars.

To run this, you can use a buyer name, supplier name, or tender keyword:

What you enter:

WhatExample
Search termsMinistry of Health
Max results per source30

The Actor searches GeBIZ awards and returns rows like these:

What you get back:

Tender no.TitleAgencyAwardeeAward amountAward date
MOH000ETT20300012Supply of medical consumablesMinistry of HealthABC MEDICAL PTE. LTD.S$482,00014/03/2026
MOH000ETT20300027Facilities maintenance servicesMinistry of HealthXYZ ENGINEERING PTE. LTD.S$1,240,00027/03/2026
MOH000ETT20300031Digital records support servicesMinistry of HealthSG SYSTEMS PTE. LTD.S$355,00002/04/2026

This is not a full tender-management platform. It is the fast extraction layer you use before analysis, outreach, reporting, or internal monitoring. If you just need a searchable export of Singapore government procurement awards, this gets you there much faster than browsing award notices one by one.


4. Compare inpatient capacity by facility segment

Healthcare and policy teams do not always need individual hospital pages first. Sometimes they need the faster top-down view: how many beds are reported across public, not-for-profit, and private segments, and in what facility categories? The MOH inpatient facilities source in this Actor gives you that aggregate view.

To query it, you can use terms like hospital, acute, or private:

What you enter:

WhatExample
Search termsacute
Max results per source20

The Actor returns aggregate MOH rows like these:

What you get back:

Facility typeFacility segmentBed countYear
HospitalPublic8,1232025
HospitalNot-for-Profit1,2452025
HospitalPrivate2,0872025

This source is useful for healthcare market mapping, service-capacity context, and public-health desk research. It is important to be clear about the boundary: these are aggregate counts by segment and facility category, not individual patient records and not a hospital-level directory.


Some Singapore sources are not row-level registries or transaction feeds. They are discovery layers. This Actor includes MOH portal navigation links and Singapore Courts judgments-hub links so you can surface official pages, sections, and references from one search flow instead of manually browsing both sites.

That makes this useful for research assistants, content teams, legal support, and internal knowledge workflows where the question is not “give me all structured records,” but “show me the official pages I should inspect next.”

What you enter:

WhatExample
Search termsjudgment or covid
Max results per source20

The Actor returns discovery rows like these:

What you get back:

SourceLink textURL
Singapore CourtsJudgmentshttps://www.judiciary.gov.sg/judgments
Singapore CourtsSupreme Court Judgmentshttps://www.judiciary.gov.sg/...
MOHInfectious Diseaseshttps://www.moh.gov.sg/...
MOHHealthcare Schemes & Subsidieshttps://www.moh.gov.sg/...

This is intentionally lighter-weight than a full legal or health content corpus. It is a routing tool. You use it to discover the right official pages faster, then decide whether you need deeper extraction or manual review.


How to use (no code required)

  1. Click "Try for Free" at the top of this page
  2. Enter one or more search terms, such as a company name, UEN, town, agency, supplier, or topic keyword
  3. Set how many results you want back from each source
  4. Click Start — the Actor queries all 6 Singapore sources in parallel
  5. Open the Dataset tab and download the results as Excel, CSV, or JSON

That is the whole workflow — type, start, export. You do not have to open ACRA, then data.gov.sg, then GeBIZ, then MOH, then the Singapore Courts site one by one. This Actor gives you one merged result stream with source labels preserved.

The free $5 Apify credit you get on signup covers about 1,600 records at the current price — enough to run real Singapore research and see whether this fits your workflow before paying anything.


What you get back

Each row includes the original source fields plus a small set of metadata that makes mixed-source exports easier to work with.

Typical fields include:

  • Business registry fields — UEN, business name, entity type, status, issue date, address, postal code
  • HDB resale fields — month, town, flat type, block, street, floor area, lease information, resale price
  • Procurement fields — tender number, title, agency, supplier name, award date, awarded amount
  • Health aggregate fields — facility category, segment, bed count, year
  • Discovery-link fields — link text, source URL, court or issuer label
  • Source metadata_product_id, _source, _search_term, _collected_at

Every row keeps enough provenance to tell you where it came from. That matters when you are combining business, property, procurement, health, and legal discovery data in one export and need to separate them again downstream.

Download the full result set as Excel, CSV, or JSON. For manual research, that is usually enough. For internal tools, AI assistants, or automated pipelines, the source-tagged rows are already structured enough to plug into the next step.


Coverage

This Actor currently queries 6 Singapore government data sources in parallel:

SourceWhat it covers
ACRA businessRegistered entities, UEN, entity type, registration status
HDB resalePublic housing resale transactions by town, street, flat type, and price
GeBIZ procurementGovernment procurement award rows, agencies, suppliers, and awarded amounts
MOH inpatient facilitiesAggregate bed counts by institution type and public/private segment
MOH portal linksOfficial MOH navigation links for policies, schemes, and health information
Singapore Courts judgments hubOfficial judgments-hub discovery links, not full judgment text

The main practical point is range. You can start with one query and get business, housing, procurement, health, and legal-discovery results back in one run.

It is also important to be precise about the limits:

  • The MOH inpatient source is aggregate capacity data, not individual hospital profiles
  • The MOH portal source is navigation-link discovery, not a medical database
  • The judiciary source is judgments-hub link metadata, not a full court corpus

That honesty matters because this Actor is strongest when used as a Singapore public-data starting point and routing layer, not when oversold as a full replacement for every individual portal.


Pricing

Pay per record. No subscription.

Billing is simple: there is a small charge when a run starts, plus a per-record charge for each result row the Actor returns.

What triggers a chargeCost
Actor start (each run)$0.005
Each returned record$0.003

To make that feel more concrete, here is what it looks like in real use:

Real-world cost examples:

ScenarioRecordsTotal cost
Quick company check across all 6 sources20$0.065
HDB + procurement scan for one topic100$0.305
Weekly Singapore public-data monitoring run300$0.905
Larger export for a research workflow1,000$3.005

The cost scales linearly — more records means more spend, fewer records means less. No seat minimum, no monthly contract, no “contact sales” gate just to test a Singapore workflow.

$5 free Apify credit = ~1,600 records at the current price, which is enough for real evaluation before you pay anything.

Compared with the alternative, the real savings are often in time, not just raw data fees. The manual path is free in theory, but it costs repeated switching between portals, repeated copy-paste work, and repeated schema cleanup. This Actor is for the moment when that friction starts to matter.


Connect to your tools

You can use this Actor from no-code automations, AI assistants, or standard API workflows. The easiest mental model is simple: one query in, source-tagged rows out.

PlatformHow to connect
Make.comSearch for Apify → choose Run Actor → Actor ID lentic_clockss/singapore-government-data-search
n8nAdd the Apify node → Run Actor → same Actor ID
ZapierUse the Apify integration and trigger a run with your search terms
ChatGPT / Claude / CursorConnect through the Apify MCP endpoint so your assistant can call this Actor inside a chat
Python / custom appsUse the Apify API or SDK and pull dataset items directly

The most common setup is straightforward:

  • Manual research: run it once, then filter the export in Excel
  • Weekly monitoring: schedule the Actor and deliver fresh rows to email, Sheets, or Slack
  • AI workflows: ask an assistant to look up a Singapore company, a housing area, or a procurement keyword and let it call the Actor for you

When to use something else

This Actor is best when you want a broad Singapore public-data starting point. If you already know you need one deep vertical, a narrower tool may be better.

If you need...Use this instead
Only ACRA-style company verification at larger global scaleGlobal Company Search
A full legal research database with complete judgments, citations, and analysisA specialist Singapore legal research product rather than a judgments-hub discovery feed
Detailed private-residential transactions or other gated Singapore sourcesA dedicated source-specific workflow once you have the right access
Pure public-housing analysis onlyThis Actor still works, but you may prefer to filter only the HDB rows downstream

The point of this Actor is breadth and speed, not maximum depth on one source.


FAQ

Q: Where does this data come from?
A: From six Singapore government sources: ACRA business data, HDB resale records, GeBIZ procurement awards, MOH inpatient-facility bed counts, MOH portal navigation links, and Singapore Courts judgments-hub links.

Q: Is this one unified Singapore database?
A: No. It is a single Actor that queries multiple Singapore sources in parallel and returns the results in one export with source metadata attached.

Q: Can I search more than one term in the same run?
A: Yes. The input accepts a list of searchTerms, and each term is queried across all 6 sources.

Q: Does this return full court judgments?
A: No. The judiciary source in this Actor returns judgments-hub discovery links and link metadata, not a full judgment-text corpus.

Q: Does the MOH source include individual patient or hospital records?
A: No patient data is included. The inpatient-facilities source is aggregate capacity data by segment and facility category. The MOH portal source is navigation-link metadata only.

Q: What is the fastest way to use this in practice?
A: Start with one search term and a low maxResultsPerSource, inspect the sources that actually return useful rows, then expand from there.


→ Browse all Actors: apify.com/lentic_clockss


Also Available