PropertyGuru SG Scraper

PropertyGuru SG Scraper at a glance

PropertyGuru SG Scraper is a ready-to-run Apify actor from abotapi for collecting real estate data. Its documented output includes id, title, change type (incremental mode), price and price label, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $1.80 per 1,000 results on the Apify Free plan and from $0.80 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Real Estate, Automation, Developer Tools
Region: Asia
Pricing: $1.80 per 1,000 results (Free plan), from $0.80 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 30 options

From $0.80/1K. Scrape PropertyGuru.com.sg sale and rental listings with 30+ structured fields, including price, PSF, floor area, tenure, nearby MRT stations, property details, agent information and GPS coordinates. Fast and reliable at scale.

What PropertyGuru SG Scraper can do

Two ways to build a search. Pick filters (district, property type, price, bedrooms) or paste a PropertyGuru search URL you already refined in your browser. URL mode ignores the filter fields entirely.
60+ structured fields per listing. Price, PSF, floor area, tenure, GPS coordinates, nearest MRT stations, agent and agency details, project facts and nearby schools.
Detail-page enrichment on demand. Switch it on for coordinates, description, project name, TOP year, total units, facilities, floor plans and nearby schools, or switch it off for a lighter search-only run.
Sale and rent, every residential type. Condo, HDB flat and landed house, both listing types.
Project-aware. Once a condo project's shared details are captured from one unit, later units in the same project can fall back to them if their own detail page fails to load, so project facts stay populated even when some detail pages fail to load.
Clear pass or fail. A run that cannot reach the site stops with a clear message instead of quietly returning an empty dataset.

Choose what to collect

These inputs let you configure PropertyGuru SG Scraper - Property Listings, Prices & Agents. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string	Search mode = build URLs from district/search/filters below. URL mode = paste any propertyguru.com.sg search URL already refined in a browser (recommended for complex filters). Choices: search, url
`urls`array	URLs to scrape. Provide propertyguru.com.sg search, single-listing, or project URLs. Tip: open propertyguru.com.sg in your browser, apply filters, then paste the resulting URL here. In URL mode, all the filter fields below are ignored. Search URLs (any district/freetext/price/sort filter, any property type path, paged /2, /3..., or the popular-location /in--d links) are paginated like a normal search. A single listing URL (/listing/for-sale-... or /listing/for-rent-...) is scraped directly as one record. A project/new-launch page (/project/...) is followed to that project's own for-sale/for-rent listings. Agent profile pages and a market=commercial filter are not supported (commercial listings live on the separate commercialguru.com.sg site) and are skipped with a warning in the run log rather than returning unrelated or mislabeled data.
`listing_type`string	Type of listing to search for. Search mode only. Choices: sale, rent
`property_type`string	Filter by property type. Note: commercial properties are on commercialguru.com.sg, not supported here. Choices: condo, hdb, landed
`search`string	Free-text location search (e.g. 'Orchard', 'Jurong', 'Tampines', 'Sentosa Cove'). Use this OR district code, not both.
`district`string	A Singapore district: a plain area name (e.g. 'Orchard', 'Bukit Timah', 'Tampines') or a D-code (D01-D28, e.g. D09). Bare numbers are also accepted for back-compat (e.g. '9' = D09). Use this OR freetext search, not both. An unrecognized value fails the run with an error rather than silently searching all of Singapore.
`min_price`integer	Minimum price in Singapore Dollars

Show 23 more inputs

More input fields
Input	What it controls
`max_price`integer	Maximum price in Singapore Dollars
`bedrooms`integer	Number of bedrooms (0=Studio)
`sort`string	Sort results by date (newest), price, or price per sqft Choices: date, price, psf
`sort_order`string	Sort direction Choices: asc, desc
`enable_detail_pages`boolean	Fetch each listing's detail page for richer attributes: latitude/longitude, full description, project name, TOP year, total units, facilities, floor plans, nearby schools, and virtual tours. Recommended. Applies regardless of search mode (Search or URL).
`fetch_reviews`boolean	Opt-in: fetch the full review list from each listing's linked project page and agent profile page (reviewer, rating, date, text, replies where the site has them). Adds one reviews array to the listing row and bills a review-enrichment surcharge per 10 reviews collected -- never charged unless this is on.
`max_reviews_per_listing`integer	Cap on reviews collected per listing (combined project + agent reviews), when Fetch Reviews is on.
`max_properties`integer	Maximum number of properties to scrape (0=unlimited)
`max_pages`integer	Maximum number of search result pages to scrape (20 listings per page)
`session_ttl_seconds`integer	Internal: how often the scraper refreshes its connection state. Hidden from the form because picking a safe value is the scraper's job, not the user's; still accepted from the API so existing saved inputs and schedules keep working unchanged.
`reuse_project_cache`boolean	Internal: when enabled, the scraper caches project-level fields (project_name, TOP year, total_units, facilities, nearby_schools, coordinates, developer, tenure) from the first listing in each condo project and reuses them as a fallback if a later same-project listing's detail page fails to load. Every listing is still fetched individually, so per-listing fields such as price_label, description and unit details are always captured accurately. Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
`dataset_name`string	Internal: custom dataset name (empty = the default dataset). Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
`clear_dataset`boolean	Internal: clear the dataset before scraping. Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
`detail_concurrency`integer	Internal: number of parallel detail-page fetches. Hidden from the form because picking a safe rate is the scraper's job, not the user's; still accepted from the API so existing saved inputs and schedules keep working unchanged.
`resumeFromRunId`string	Paste a previous run ID or dataset ID to continue a large crawl of listings without returning or charging for listings already collected there. Use this after an interrupted run, or when continuing a search pull in another run. For recurring daily monitoring of the same search, use Incremental mode below instead.
`incrementalMode`boolean	Turn this on for daily or recurring monitoring. The first run returns all matching listings as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED listings. Turn on "Emit unchanged" or "Emit expired" only when you also want those listings returned (and billed). State is kept separately for each search/filter/URL and detail-page setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.
`stateKey`string	Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the search/filter/URL and detail-page settings, different searches then never mix state with each other.
`emitUnchanged`boolean	Off by default. Turn on to also return listings that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want the full snapshot every run.
`emitExpired`boolean	Off by default. Turn on to also return listings that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search, not when Max pages/properties capped it, a page was blocked, or Resume was used. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking.
`ignoreFieldsForChanges`array	Output field names that should NOT make a listing count as UPDATED. recency is always ignored, because it is a relative-age render ("37m ago") that ticks over on every re-scrape even though nothing about the listing changed. Add nested field paths with a dot (for example agent.phone) to ignore only that exact nested field, or a bare name (for example description) to ignore it anywhere it appears. Ignored fields are still returned in the output.
`mcpConnectors`array	Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON, the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
`notionParentPageUrl`string	URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idID (text)

titleTitle (text)

changeTypeChange type (incremental mode) (text)

price_formattedPrice (text)

price_labelPrice Label (text)

price_psfPSF (text)

bedroomsBeds (number)

bathroomsBaths (number)

floor_areaArea (sqft) (number)

land_areaLand size (sqft) (number)

tenureTenure (text)

districtDistrict (text)

Show 17 more fields

nearby_mrtMRT (text)

posted_datePosted (text)

urlURL (link)

changedFieldsChanged fields (incremental mode) (array)

firstSeenAtFirst seen (incremental mode) (date)

lastSeenAtLast seen (incremental mode) (date)

latitudeLat (number)

longitudeLng (number)

location_sourcelocation_source

district_codedistrict_code

regionregion

agent_nameagent_name

agent_idagent_id

agent_licenseagent_license

agency_nameagency_name

developerdeveloper

is_developer_listingis_developer_listing

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "id": 25100001,
  "title": "The Sample Residences",
  "address": "1 Sample Road, Singapore 238001",
  "short_address": "Orchard / River Valley, Central (D09-10)",
  "url": "https://www.propertyguru.com.sg/listing/for-sale-the-sample-residences-25100001",
  "listing_type": "sale",
  "property_type": "Condo",
  "property_type_text": "Condominium",
  "price": 2800000,
  "price_formatted": "S$ 2,800,000",
  "currency": "SGD",
  "price_psf": "S$ 2,450 psf",
  "price_label": "Negotiable",
  "bedrooms": 3,
  "bathrooms": 2,
  "floor_area": 1140,
  "tenure": "Freehold",
  "developer": "Sample Developments Pte Ltd",
  "is_developer_listing": false,
  "is_verified_listing": true,
  "district": "Orchard",
  "district_code": "D09",
  "region": "Central Region",
  "nearby_mrt": "Orchard MRT",
  "latitude": 1.3039,
  "longitude": 103.8318,
  "location_source": "detail_page",
  "postal_code": "238001",
  "agent_name": "Agent Name",
  "agent_license": "R012345A",
  "agency_name": "Sample Realty Pte Ltd",
  "account_type_code": "CORPORATE",
  "project_name": "The Sample Residences",
  "top_year": 2019,
  "total_units": 250,
  "facilities": [
    "Swimming Pool",
    "Gym",
    "BBQ Pits",
    "24-hour Security"
  ],
  "nearby_schools": [
    {
      "name": "Sample Primary School",
      "distance_km": 0.6,
      "walking_mins": 8,
      "subcategory": "Primary"
    }
  ],
  "posted_date": "3 days ago",
  "image_count": 18
}

Ways to use this data

Real estate agents and agencies: build a live comparison feed of competing listings by district or project for pricing and marketing.
Property investors and analysts: track price, PSF and tenure across districts and condo projects over time.
Rental market research: monitor asking rents, availability and price positioning for a district or project.
Proptech and listing-aggregator products: feed structured Singapore property data into your own search or valuation tool.
Lead generation: collect agent and agency contact details attached to active listings in a target area.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does PropertyGuru SG Scraper return?

The documented output for PropertyGuru SG Scraper includes id, title, change type (incremental mode), price, price label, psf, beds and baths. Availability of each field depends on the source page and the selected mode.

How much does PropertyGuru SG Scraper cost?

It costs $1.80 per 1,000 results on the Apify Free plan and from $0.80 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

What is the difference between Resume and Incremental mode?

They serve different purposes. Resume (resumeFromRunId) continues one specific interrupted run so you don't re-collect or re-pay for listings it already gathered. Incremental mode (incrementalMode) is for scheduling the same search again and again, for example daily, and getting back only the listings that are new, changed, or reappeared since the last run. Use Resume after an interrupted run; use Incremental mode for ongoing monitoring.

Why did my run fail instead of returning an empty dataset?

The run stops with a clear error only when it cannot proceed at all: no connection could be established, access to the site was lost and could not be restored after retries, url mode was chosen with no URLs, an invalid resumeFromRunId was supplied, or resumeFromRunId was combined with Incremental mode for a search that already has saved state (use a different stateKey instead). If the run completes but your search simply matched zero listings, or Incremental mode finds nothing new or changed since the last run, that is a normal successful run with an empty (or smaller) dataset, not a failure.

What happens if my run has a short timeout?

Every listing is saved as soon as its detail page is done, so a run that is stopped early keeps what it already collected. If the run's time limit gets close, the remaining listings from the current search page are returned with their search-card fields only (no detail-page fields) and are not billed for detail-page enrichment, and the run's status message says how many. The Max items run option also caps how many listings are collected. Raise the run timeout or lower Max Properties to get every listing fully enriched.

Can I track only new or updated listings on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated and reappeared listings, and unchanged ones are not billed unless you turn on emitUnchanged.