PropertyGuru MY Scraper icon

PropertyGuru MY Scraper

Scrape PropertyGuru.com.my sale and rental listings with 30+ structured fields, including MYR price, built-up area, tenure, nearby transit, property…

Start using this actor on Apify ↗Need a custom scraper?Contact us ↗

PropertyGuru MY Scraper at a glance

PropertyGuru MY 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 psf, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.00 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
$2.00 per 1,000 results (Free plan), from $1.00 on paid plans
Output
Documented below · JSON, CSV, Excel
Inputs
28 options

Scrape PropertyGuru.com.my sale and rental listings with 30+ structured fields, including MYR price, built-up area, tenure, nearby transit, property details, agent information and GPS coordinates. Fast and reliable at scale.

What PropertyGuru MY Scraper can do

  • Two ways to search. Pick a state or federal territory from the dropdown, or type a free text location like "Mont Kiara" or "Bukit Bintang". Paste your own propertyguru.com.my search URL instead if you need filters the built in fields don't cover.
  • Condo, landed, commercial and land. Filter by property type on top of listing type (sale or rent), price range and bedroom count. "Landed" narrows to terrace houses only; for bungalows, semi-D or cluster homes, use URL mode instead.
  • Detail page enrichment on demand. Turn on detail pages to add coordinates, full description, project name, total units, facilities, floor plans and nearby schools to every listing.
  • Project level caching. For condos, the actor fetches one unit's detail page per project and reuses the shared project fields (facilities, coordinates, developer, total units) across every other unit in the same development, cutting the cost of condo heavy runs.
  • All 13 states plus the 3 federal territories. A single dropdown covers every Malaysian state and federal territory, so state wide monitoring needs no manual URL building.
  • Built for schedules. Incremental mode returns only new and changed listings on recurring runs, and a resume option continues one interrupted crawl without re paying for listings you already collected.

Choose what to collect

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

Supported input fields
InputWhat it controls
modestringSearch mode = build URLs from state/search/filters below. URL mode = paste any propertyguru.com.my search URL already refined in a browser (recommended for complex filters).

Choices: search, url

urlsarrayURLs to scrape. Supports a search results page, a category path (e.g. /condo-for-sale), a location path (e.g. /condo-for-sale/in-kuala-lumpur-58jok), a new-launch/project collection page, a single listing detail page, an agent profile page (resolved to that agent's own sale + rent listings), and a paginated start (e.g. /property-for-sale/2?...). Tip: open propertyguru.com.my in your browser, apply filters, then paste the resulting URL here. An unsupported URL shape logs a loud warning instead of silently returning 0 items. In URL mode, all the filter fields below are ignored.
listing_typestringType of listing to search for. Search mode only.

Choices: sale, rent

property_typestringFilter by property type. 'condo' covers condominiums and apartments; 'landed' narrows to terrace houses (the most common landed sub-type; for bungalow/semi-D/cluster use a free-text location instead); 'commercial' covers shop/office/factory; 'land' covers residential land plots.

Choices: condo, landed, commercial, land

statestringMalaysian state or federal territory. Pick this OR the free-text location, not both. Use 'Kuala Lumpur' for KL, 'Selangor' for the surrounding state.

Choices: kuala-lumpur, selangor, penang, johor, perak, kedah, pahang, negeri-sembilan, terengganu, kelantan, perlis, melaka, sabah, sarawak, putrajaya, labuan

searchstringFree-text location search (e.g. 'Mont Kiara', 'Bangsar', 'Cyberjaya', 'Bukit Bintang', 'Iskandar Puteri'). Use this OR the state dropdown, not both.
min_priceintegerMinimum price in Malaysian Ringgit
Show 21 more inputs
More input fields
InputWhat it controls
max_priceintegerMaximum price in Malaysian Ringgit
bedroomsintegerNumber of bedrooms (0=Studio)
sortstringSort results by date (newest), price, or price per sqft

Choices: date, price, psf

sort_orderstringSort direction

Choices: asc, desc

enable_detail_pagesbooleanFetch each listing's detail page for richer attributes: latitude/longitude, full description, project name, total units, facilities, floor plans, and nearby schools. Recommended. Applies regardless of search mode (Search or URL).
max_propertiesintegerMaximum number of properties to scrape (0=unlimited)
max_pagesintegerMaximum number of search result pages to scrape (20 listings per page)
detail_concurrencyintegerInternal: number of parallel detail-page fetches. Picking a safe rate is the scraper's job, not the user's; higher values are faster but may trigger rate limiting. Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
session_ttl_secondsintegerInternal: how often the scraper refreshes its connection state. The default of 10 minutes comfortably covers typical runs. Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
reuse_project_cachebooleanInternal: when enabled, the scraper caches project-level fields (project_name, total_units, facilities, nearby_schools, coordinates, developer, tenure) from the first listing in each condo project and reuses them on subsequent listings in the same project. Every listing is still tracked accurately; per-listing fields such as price and description come from the listing card. Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
dataset_namestringInternal: 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_datasetbooleanInternal: clear the dataset before scraping. Hidden from the form; still accepted from the API so existing saved inputs and schedules keep working unchanged.
resumeFromRunIdstringPaste 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.
incrementalModebooleanTurn 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 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.
stateKeystringOptional. 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 settings, different searches then never mix state with each other.
emitUnchangedbooleanOff 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.
emitExpiredbooleanOff 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.
ignoreFieldsForChangesarrayOutput field names that should NOT make a listing count as UPDATED. recency is always ignored, because it is a relative-age render ("8m ago") that changes on every fetch even when nothing else about the listing does. For a field nested inside a list like nearby_mrts/nearby_schools, use a dotted path, e.g. nearby_schools.distance_km, to ignore it within every entry of that list rather than the whole list at once. Ignored fields are still returned in the output, they just never trigger an UPDATED row or appear in changedFields by themselves.
mcpConnectorsarrayOptionally 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).
notionParentPageUrlstringURL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
maxNotifyListingsintegerCap 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_psfPSF (text)
bedroomsBeds (number)
bathroomsBaths (number)
floor_areaArea (sqft) (number)
tenureTenure (text)
stateState (text)
nearby_mrtNearest Transit (text)
posted_dateposted_date
Show 14 more fields
urlURL (link)
changedFieldsChanged fields (incremental mode) (array)
firstSeenAtFirst seen (incremental mode) (date)
lastSeenAtLast seen (incremental mode) (date)
latitudeLat (number)
longitudeLng (number)
location_sourcelocation_source
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": 36124001,
  "title": "Mont Kiara Pelangi",
  "address": "Jalan Kiara, Mont Kiara, Kuala Lumpur",
  "listing_type": "sale",
  "property_type": "Condo",
  "price": 680000,
  "price_formatted": "RM 680,000",
  "currency": "MYR",
  "price_psf": "RM 680 psf",
  "bedrooms": 3,
  "bathrooms": 2,
  "floor_area": 1000,
  "tenure": "Freehold",
  "state": "Kuala Lumpur",
  "city": "Kuala Lumpur",
  "nearby_mrt": "5 min (450 m) to Sri Hartamas MRT",
  "agent_name": "Kevin Chai",
  "agent_license": "PEA1234",
  "agency_name": "ABC Realty Sdn Bhd",
  "posted_date": "30 Jul 2026",
  "images": [
    "https://my1-cdn.pgimgs.com/listing/36124001/UPHO.157827896.V800/a.jpg"
  ],
  "image_count": 8,
  "url": "https://www.propertyguru.com.my/property-listing/mont-kiara-pelangi-36124001",
  "status": "active",
  "latitude": 3.1698,
  "longitude": 101.6509,
  "project_name": "Mont Kiara Pelangi",
  "total_units": 545,
  "facilities": [
    "Swimming Pool",
    "Gymnasium",
    "24-hour Security"
  ]
}

Ways to use this data

  • Property portals and listing aggregators: pull structured MYR pricing, area and location data to power a search or comparison site.
  • Investment and market research: track price per square foot, tenure and bedroom mix across states to spot undervalued areas.
  • Lead generation for agents and agencies: collect agent names, licenses and contact details alongside the listings they represent.
  • Recurring monitoring: schedule the actor on a saved search (a state, a project, a price band) and get only new, updated or reappeared listings on each run.
  • Mapping and location apps: feed latitude and longitude, nearest transit and nearby schools into a map based property tool.

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 MY Scraper return?

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

How much does PropertyGuru MY Scraper cost?

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

Can I get only new or changed 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 Emit unchanged listings.

Why does incremental mode sometimes return nothing?

If nothing changed since the last run, that is the expected result: incremental mode suppresses UNCHANGED listings by default, so a quiet run legitimately returns zero rows while still recording that it scanned everything.

Why did my run fail or return nothing?

If the site refuses access, the actor uses its bounded access retries and then stops with a clear "please retry" message if access remains blocked. Run it again in a few minutes. A resumeFromRunId value that does not point to a valid run or dataset in your account also fails the run immediately, before anything is scraped or charged.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.

Ready to collect with PropertyGuru MY Scraper?

Run it on Apify with your own input and export the results as JSON, CSV or Excel.