realestate.com.au Scraper | AU Sale Rent Sold API avatar

realestate.com.au Scraper | AU Sale Rent Sold API

Pricing

from $3.00 / 1,000 results

Go to Apify Store
realestate.com.au Scraper | AU Sale Rent Sold API

realestate.com.au Scraper | AU Sale Rent Sold API

Scrape realestate.com.au Australian sale, rent, and sold listings by suburb/city. Extract prices, beds, baths, land size, agencies, photos & URLs — realestate.com.au API alternative.

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

17 hours ago

Last modified

Share

realestate.com.au Scraper — AU Sale, Rent & Sold Listings

Scrape realestate.com.au for-sale, rental, and sold property listings by Australian suburb or city — then download structured data as Excel, CSV, or JSON.

This Actor is a practical realestate.com.au API alternative for market research, investor comps, rental screening, agency monitoring, and lead lists. Enter a location such as Melbourne, VIC, choose sale, rent, sold, both, or all, and get listing rows with prices, beds, baths, land size, agency, photos, and direct listing URLs.

Thin Actor + Cloud Run worker. Worker URL is config (WORKER_BASE_URL), not hardcoded-only — migrate the worker by updating Actor env without a code change. Set WORKER_PROVIDES_PROXY=1 when the worker supplies its own PROXY_URL.

  • Pull Australian homes for sale, rentals, and sold results from realestate.com.au
  • Filter by property type (house, unit, apartment, land, rural, retirement, and more), beds, and price
  • Optionally enrich listings from detail pages, or scrape specific property URLs
  • Export to Excel / CSV / JSON, or connect Make, n8n, Zapier, Python, or Apify MCP / API
  • Pay per event — Actor start + each Dataset listing; platform compute is included (you do not pay separate Apify usage)

What does the realestate.com.au Scraper do?

It turns a realestate.com.au search (or detail URLs) into a clean Apify Dataset of Australian residential listings.

Under the hood, the Actor:

  1. Validates your input (location, listing type, filters, optional detail URLs)
  2. Calls a managed Cloud Run worker that unlocks realestate.com.au pages (Kasada-aware)
  3. Collects search-result and/or detail listing data across sale / rent / sold channels
  4. Normalizes records into Dataset rows with preview fields (name, type, status, country, authority)
  5. Writes RUN_SUMMARY (and ERROR_SUMMARY on failure) to the key-value store

You run the Actor like any other Apify Actor — schedule it, call it from the API, or plug it into automations. No local browser or proxy setup is required.


What data can you extract from realestate.com.au?

Data pointSaleRentSold
Address / listing name
Listing ID & property type
Price / rent display
Beds / baths / parking
Land / building size (when shown)
Suburb, state, postcode
Agency / authority
Listing URL & main image
Description & inspections (when present)

Every Dataset row includes source = realestate.com.au and country = Australia. A RUN_SUMMARY record reports counts, provider, and warnings.


What you can do with it

1. Scrape Australian homes for sale

Enter a suburb/city like Melbourne, VIC, set listingType to sale, and get structured rows with price, beds, baths, agency, and a direct listing URL — ready for comps or investor shortlists.

2. Scrape Australian rentals

Set listingType to rent. Rows include weekly rent display, beds/baths, parking, and agency when present.

3. Scrape sold property results

Set listingType to sold to pull recently sold listings for pricing analysis and comparable sales.

4. Cover multiple channels or locations in one run

Use listingType = both or all, add extra suburbs in locations, and optionally filter by propertyTypes, beds, and price.

5. Scrape specific property detail pages

Paste one or more realestate.com.au property URLs into detailUrls to skip search and fetch those listings directly.

6. Feed AU property data into automations

Schedule the Actor and send the Dataset to Sheets, Slack, CRM, Make, n8n, Zapier, or an AI agent via Apify MCP / API.


How to scrape realestate.com.au (no code required)

  1. Click Try for free on this Actor page
  2. Enter a location (Melbourne, VIC or Sydney, NSW)
  3. Choose sale, rent, sold, both, or all
  4. Optionally set property types, beds/price filters, and max results
  5. Click Start — open the Dataset tab when the run finishes

Start with maxResults: 5–10 to verify the market, then scale up.


How much does it cost to scrape realestate.com.au?

This Actor uses pay-per-event pricing. You are charged for:

EventPrice
Actor Start (apify-actor-start)$0.005 per start
Result (apify-default-dataset-item)$3.00 / 1,000 listings ($0.003 each)

Platform usage costs are included — you do not pay separate Apify compute/proxy usage for this Actor on top of the event prices above.

Example cost estimates

Listings collectedApprox. event cost*
100~$0.31
1,000~$3.01
10,000~$30.01

*Assumes one Actor start at default memory billing for start events, plus $0.003 per Dataset item. Exact start billing can scale with allocated memory (one start event per GB, minimum one).

Free Apify trial credit can cover a small test run — try maxResults: 5 first.

Free Apify plan limits (set by this Actor's developer)

LimitFree Apify planPaid Apify plan
Runs of this Actor10 totalUnlimited
Listings per run200Up to schema max (500)

These caps are enforced in Actor code (not by Apify). Upgrade to a paid Apify plan for unlimited runs.


Input

Open the Input tab for the full form. Common fields:

FieldDescription
locationAustralian suburb/city + state, e.g. Melbourne, VIC
locationsExtra locations in the same run
listingTypesale / rent / sold / both / all
propertyTypesOptional: house, unit, apartment, land, rural, retire, …
minBeds / maxBedsBedroom filters
minPrice / maxPricePrice filters (AUD)
maxResultsCap on listings (1–500; free plan also capped at 200/run)
maxPagesCap on search pages per location/channel (1–80)
enrichDetailsOpen detail pages for richer fields (slower)
detailUrlsSkip search; scrape these property URLs
failoverAllow worker provider failover (default true)
workerBaseUrlOptional https override (allowlisted hosts only)

proxyConfiguration may appear in the form for compatibility but is ignored — unlock/proxy traffic is handled by the managed worker.

Free Apify plan: up to 10 runs of this Actor and 200 listings per run. Upgrade to a paid Apify plan for unlimited runs. (Limits set by the Actor developer.)

Example input

{
"location": "Melbourne, VIC",
"listingType": "sale",
"propertyTypes": ["apartment"],
"minBeds": 2,
"maxResults": 20,
"maxPages": 2,
"enrichDetails": false,
"failover": true
}

Output example

You can download the Dataset as JSON, CSV, Excel, or HTML.

{
"name": "1211/12 Queens Road",
"type": "Apartment",
"status": "for_sale",
"country": "Australia",
"authority": "First National Real Estate Central - CARLTON",
"listingId": "148388492",
"listingType": "sale",
"address": "1211/12 Queens Road",
"fullAddress": "1211/12 Queens Road, Melbourne, Vic 3004",
"suburb": "Melbourne",
"state": "Vic",
"zipCode": "3004",
"priceDisplay": "$500,000 Private Sale",
"beds": 2,
"baths": 1,
"parking": 1,
"propertyType": "Apartment",
"listingUrl": "https://www.realestate.com.au/property-apartment-vic-melbourne-148388492",
"imageUrl": "https://i2.au.reastatic.net/800x600/.../image.jpg",
"source": "realestate.com.au"
}

Key-value store records:

  • INPUT_ECHO — normalized non-secret input
  • RUN_SUMMARY — counts, provider, diagnostics, timestamps
  • ERROR_SUMMARY — structured failure details when a run fails

How to scrape realestate.com.au with Python or the Apify API

from apify_client import ApifyClient
client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("lentic_clockss/realestate-com-au-scraper").call(
run_input={
"location": "Sydney, NSW",
"listingType": "sold",
"maxResults": 10,
"maxPages": 1,
}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["listingUrl"], item.get("priceDisplay"))

You can also schedule runs, set webhooks, or connect the Dataset to Make / Zapier / n8n from the Apify Console.


Our scrapers are ethical and do not extract private user data such as email addresses, gender, or private contact details that are not publicly shown on listing pages. They only extract what is publicly available on realestate.com.au listing cards and property pages.

You should still be aware that results can include personal data (for example agent names). Personal data is protected by the Australian Privacy Act, the GDPR in the EU, and other regulations. You should not scrape personal data unless you have a legitimate reason. If you are unsure, consult your lawyers. See also Apify’s guidance on the legality of web scraping.


FAQ

Does this Actor replace the official realestate.com.au API?

There is no broadly available public listing API for most third-party use cases. This Actor is an API alternative that returns structured JSON/CSV/Excel you can use in research and automations.

Why do some sold listings put the price in priceDisplay?

The worker normalizes sale/rent/sold displays into priceDisplay for a consistent schema. soldPriceDisplay may be empty even when a sold price string is present in priceDisplay.

Do I need Apify Proxy?

No. Proxy / unlock traffic is handled by the managed worker. The proxyConfiguration input field is ignored.

Why did my free-plan run stop after 10 runs?

This Actor allows 10 runs and 200 listings per run for free Apify plan users. That limit is set by the Actor developer (not Apify). Upgrade to a paid Apify plan for unlimited runs.

Can I scrape commercial property or Flatmates?

Not in this Actor. Coverage is residential sale / rent / sold on realestate.com.au (including common residential property types such as house, unit, land, rural, and retirement).

Where can I get help?

Open an issue on the Actor’s Issues tab in Apify Console with your run ID and a short description. Include a sample input when possible.


Tips for better results

  • Prefer specific suburbs (Richmond, VIC) when you need local comps; use CBD/city names for broader coverage
  • Keep maxPages low while testing; raise it after you confirm filters
  • Use propertyTypes + beds/price filters to reduce noise before scaling maxResults
  • Enable enrichDetails only when you need LDP-only fields — it increases run time

Built for Australian property data workflows on the Apify platform — scheduling, monitoring, API access, and Dataset exports included.