PropertyGuru SG Scraper — Singapore Property Listings

Scrape PropertyGuru.com.sg property listings by district (D01-D28), sale or rent. Returns price, price/psf, bedrooms, bathrooms, floor area, tenure, nearby MRT, agent and agency, posted date, images. Works out of the box, pay per listing.

What it does

PropertyGuru SG Scraper — Singapore Property Listings is a data-collection tool for the real estate category. The inputs let you set the scope and preferences for a run, while the results provide organized records that are easier to review and use.

Input

Provide the values that define the scope and preferences for the run. Review each option before starting so the resulting dataset matches the information you want to analyze or reuse.

Name	Type	Description	Default
district	string	Singapore URA planning-area district code, D01-D28 (e.g. D09 = Orchard / River Valley).	"D09"
enable_detail_pages	boolean	Fetch each listing's own detail page for extra fields (GPS, project name, facilities, nearby schools). Off by default — keeps runs fast and cheap; charges a secondary 'detail-enrichment' event per enriched listing when on.	false
listing_type	string	Whether to scrape for-sale or for-rent listings.	"sale"
max_pages	integer	Safety cap on how many result pages (20 listings/page) to fetch.	5
max_properties	integer	Maximum number of listings to return.	20
mode (required)	string	Scrape mode. Only 'search' is supported today.	"search"
property_type	string	Keep only listings whose property type text contains this (case-insensitive), e.g. 'condo', 'hdb', 'landed'. Leave empty for all types.	""
proxy	object	PropertyGuru.com.sg is geo-locked to Singapore — RESIDENTIAL / country SG is required, not optional.	—

Output

A successful run produces a dataset of structured items collected according to your inputs. You can review the records, use them in analysis, or pass them to another part of your workflow. The exact fields depend on the source data and the options selected for the run.

Usage

1. Open the actor page.
2. Fill in the input values and review the configuration.
3. Run the actor and wait for the collection to finish.
4. Download the results from the dataset and use the records in your preferred workflow.

Pricing

Pricing is pay-per-event, so you pay only for results.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.