Property AU Scraper

Scrape Australian property listings with rich detail-page enrichment. Each listing record comes back with far more than the usual "address + price + beds".

Two ways to run it

Listing mode (default). Describe what you want with structured filters:

{
  "mode": "listing",
  "search": "southbank",
  "listing_type": "buy",
  "propertyTypes": ["HOUSE", "APARTMENT"],
  "priceMin": 500000,
  "priceMax": 900000,
  "bedroomsMin": 2,
  "max_properties": 100,
  "max_pages": 5
}

search accepts a suburb name, postcode, or city: southbank, 3006, brisbane, melbourne. Ambiguous or misspelled queries fail fast rather than running against the wrong location.

URL mode. Paste search URLs directly and let the scraper walk them forward:

{
  "mode": "url",
  "urls": [
    "https://www.example.com/search/?locations=Melbourne%2C+VIC+3000&propertyStatus=FOR_SALE&pageNumber=2"
  ],
  "max_properties": 60,
  "max_pages": 3
}

Pagination walks forward from the URL's own ?pageNumber=N. Pass pageNumber=2 with max_pages=3 and you get pages 2, 3 and 4.

Filters (listing mode)

Field	Notes
listing_type	buy, rent, or sold
propertyTypes	HOUSE, APARTMENT, TOWNHOUSE, VILLA, LAND, ACREAGE, RURAL, BLOCK_OF_UNITS, RETIREMENT
priceMin / priceMax	AUD
bedroomsMin / bathroomsMin
landSizeMin	square metres
carSpacesMin
excludeUnderOffer	buy only
sortBy	NEW_DESC (default), PRICE_ASC, PRICE_DESC, RELEVANCY, NEXT_AUCTION, NEXT_INSPECTION

In URL mode these filters are ignored. Encode them directly in your URLs.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape — the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record — not the full JSON. Each item becomes one entry with a title (the listing's name / address) and its key fields flattened to plain text (price, beds/baths, agent, URL, …). Nested objects are collapsed to their main value (e.g. an address object → its full-address text) and long lists are trimmed to the first few names. The complete, full-fidelity record always stays in the Apify dataset — the connector copy is a readable digest for browsing in your app.

• Notion → one page per item (title + a summary body), created under the page you set in notionParentPageUrl.
• Linear / Airtable / other → one record/issue per item with the same title + fields.

How to enable:

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip — the export only runs when a connector is selected.

Proxy

A residential proxy is required for complete results. Runs without a residential proxy still complete, but return a reduced dataset. Set the proxy to RESIDENTIAL + AU country in Proxy Configuration.

Limits & dataset

• max_properties: hard cap on results (0 = unlimited)
• max_pages: per URL page budget (0 = unlimited)
• dataset_name: custom dataset name; omit or use default for the default dataset
• clear_dataset: wipe the dataset before the run

Tips

• Start small. Set max_properties: 10 for a first run to verify your filters before scaling up.
• Use URL mode for complex filters. Build a search on the site, copy the URL, and paste it into urls.
• max_pages is a per URL budget. If you pass three URLs and set max_pages: 5, the scraper walks up to 5 pages for each of them.