# realestate.com.au & Domain Scraper — Buy, Rent, Sold (`he_work/au-property-listings`) Actor

For-sale, rental and sold listings from realestate.com.au and Domain in one run, merged into one row per property: address, parsed price, beds, baths, parking, land size, agency, agents, coordinates and both links.

- **URL**: https://apify.com/he_work/au-property-listings.md
- **Developed by:** [HE Work](https://apify.com/he_work) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.76 / 1,000 properties

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## realestate.com.au & Domain Scraper — Buy, Rent, Sold

> ✅ **Checked daily.** An automated test runs this Actor on the Apify cloud every day and checks that it still returns real data, so if the website changes and something breaks, it's caught the same day and fixed.

Collect **for-sale, rental and sold listings from realestate.com.au and Domain in one run**, cleaned into one schema and **merged into one row per property** when a home is listed on both portals.

### What you get

- Address (street, suburb, state, postcode) and, from Domain, latitude/longitude
- Property type, bedrooms, bathrooms, parking, land size (m²)
- Price as shown (`"$1,998,000"`, `"Auction"`, `"$650 per week"`) **plus parsed numbers**: `price`, `price_min`, `price_max`, `price_period`
- Status tags (under offer, new, auction date, sold date), agency and agent names, description (realestate.com.au), main image
- Both listing IDs and links when a property appears on both sites (`sources: ["domain", "realestate"]`)

### Input

| Field | Default | Description |
|---|---|---|
| `locations` | – | Suburbs as `Suburb, STATE postcode`, e.g. `Paddington, QLD 4064` |
| `listingType` | `buy` | `buy`, `rent` or `sold` |
| `sites` | both | `realestate`, `domain` |
| `maxPages` | `2` | Search-result pages per suburb per site (25 per page on realestate.com.au, 20 on Domain) |
| `maxListings` | `200` | Hard cap on results for the run |
| `mergeAcrossSites` | `true` | One row per property across both portals |
| `proxyConfiguration` | Apify residential, AU | Required: both portals block datacenter IPs |

### Output example

```json
{
  "address": "11 Norwood Tce, Paddington, Qld 4064",
  "suburb": "Paddington", "state": "QLD", "postcode": "4064",
  "lat": -27.458227, "lng": 152.99,
  "listing_type": "buy", "property_type": "House",
  "beds": 6, "baths": 3, "parking": 2, "land_size_m2": 890,
  "price_text": "Auction", "price": null,
  "agency": "SpinksCo Residential - Brisbane",
  "sources": ["domain", "realestate"],
  "realestate_id": "152841840", "domain_id": "2021301466",
  "realestate_url": "https://www.realestate.com.au/property-house-qld-paddington-152841840",
  "domain_url": "https://www.domain.com.au/11-norwood-terrace-paddington-qld-4064-2021301466"
}
```

The run's `OUTPUT` record lists every search (site × suburb) with pages read, listings found and any error.

### Example output

One item from a real run (long texts shortened):

```json
{
  "address_key": "13/11 mort st|paddington|4064",
  "address": "13/11 Mort Street, Paddington, QLD 4064",
  "street": "13/11 Mort Street",
  "suburb": "Paddington",
  "state": "QLD",
  "postcode": "4064",
  "lat": -27.460844,
  "lng": 153.00171,
  "listing_type": "buy",
  "property_type": "Apartment / Unit / Flat",
  "beds": 1,
  "baths": 1,
  "parking": 1,
  "land_size_m2": 47,
  "price_text": "New Price - $530,000+",
  "price": 530000,
  "price_min": 530000,
  "price_max": 530000,
  "price_period": null,
  "status_tag": "Updated",
  "auction_date": null,
  "sold_date": null,
  "agency": "Ray White Paddington",
  "agents": [
    "Luke Dawson"
  ],
  "description": "Positioned for a premier Paddington lifestyle, this bright and light inviting apartment delivers the perfect balance of location, low-maintenance ease and ev…",
  "image": "https://rimh2.domainstatic.com.au/Pr_3ukWNi7AxLsKxjXJs5TpxSyQ=/720x540/filters:format(webp):quality(85)/2021153379_3_1_260914_045619-w2000-h1335",
  "sources": [
    "domain",
    "realestate"
  ],
  "realestate_id": "152328376",
  "realestate_url": "https://www.realestate.com.au/property-apartment-qld-paddington-152328376",
  "domain_id": "2021153379",
  "domain_url": "https://www.domain.com.au/13-11-mort-street-paddington-qld-4064-2021153379",
  "scraped_at": "2026-11-05T02:24:18.104114+00:00"
}
```

### Alerts & workflows

Ready-made workflow: **New property listings → Google Sheets + alert**. No Make or Zapier needed — set it in the input and schedule the Actor (e.g. daily).

1. Give the run a **Watch list name** (e.g. `my-watch`). Every run with that name remembers every listing (by address) with its price text; each item gets `change_status` = `new`, `changed` or `unchanged` (changed items also carry `previous_value`).
2. Turn on **Only new / changed items** to skip — and not pay for — items you've already seen.
3. Add one or more destinations; after each run you get a digest of what's new or changed:
   - **Slack**: an incoming-webhook URL.
   - **Telegram**: bot token (from @BotFather) + chat ID.
   - **Discord**: a channel webhook URL.
   - **Email**: an address (sent with Apify's send-mail Actor).
   - **Google Sheets**: open your sheet → Extensions → Apps Script, paste the script below, Deploy → New deployment → Web app (execute as you, access: anyone), and paste the web app URL into the input. Each new / changed item is appended as a row.

```javascript
function doPost(e) {
  var rows = JSON.parse(e.postData.contents).rows || [];
  var sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  if (!rows.length) return ContentService.createTextOutput("0");
  var head = sheet.getLastRow() ? sheet.getRange(1, 1, 1, sheet.getLastColumn()).getValues()[0] : [];
  if (!head.length) { head = Object.keys(rows[0]); sheet.appendRow(head); }
  rows.forEach(function (r) { sheet.appendRow(head.map(function (h) { return r[h] === undefined ? "" : r[h]; })); });
  return ContentService.createTextOutput(String(rows.length));
}
```

Secrets (webhook URLs, bot tokens) are stored encrypted by Apify.

### How it compares

| | This Actor | Typical alternative |
|---|---|---|
| Fields per result | 32 (see *Example output*) | Varies by actor |
| Freshness | Read live from the source when the run starts | Varies |
| Reliability | Tested daily by an automated run on the Apify cloud (see the top of this page) | — |
| Price | $0.90 per 1,000 propertys | $0.90–$2.99 per 1,000 results (comparable Actors on the Apify Store, 6 Nov 2026) |

### Pricing

Pay per result, no monthly fee:

- **$0.90 per 1,000 propertys**: One property delivered to your dataset (a home listed on both sites counts once).
- $0.002 per run (start).

Bronze plans pay 5% less, Silver 10% less, Gold and above 15% less.

**Examples:** 1,000 propertys = $0.90; 10,000 = $9.00.

### FAQ

**How do I run it on a schedule?** Create a task with your input and add a schedule in Apify Console (e.g. daily at 6 am). Each run writes a fresh dataset.

**How do I get the data?** Download the dataset as JSON, CSV, Excel, XML or HTML from the run page, or read it with the Apify API / Python and JavaScript clients. Integrations (Google Sheets, Make, Zapier, n8n, webhooks) work out of the box.

**Do I need proxies or an account on the site?** No. Proxies are handled inside the Actor and included in the price; no login is needed.

**What if a run returns fewer results than expected?** Check the run's key-value store `OUTPUT` record (when present) for a per-request report, then open an issue on the Issues tab with the run link and we'll look into it.

**Is it legal?** The Actor only collects publicly available data. You are responsible for using it in line with the website's terms, copyright and data-protection rules (GDPR, CCPA) — don't collect personal data you have no legal basis for.

### Notes

- Data comes from public search-result pages; the actor doesn't log in.
- Use the listings in line with the portals' terms and Australian privacy law, especially agent contact details.

# Actor input Schema

## `locations` (type: `array`):

One per line, as 'Suburb, STATE postcode', e.g. 'Paddington, QLD 4064'.

## `listingType` (type: `string`):

Which listings to collect.

## `sites` (type: `array`):

Search one or both portals.

## `maxPages` (type: `integer`):

realestate.com.au shows 25 listings per page, Domain 20.

## `maxListings` (type: `integer`):

Hard cap on results (and on what you pay) for the whole run.

## `mergeAcrossSites` (type: `boolean`):

One row per property when it's listed on both portals, with both links.

## `proxyConfiguration` (type: `object`):

Both portals block datacenter IPs; an Apify AU residential proxy is required.

## `watchListName` (type: `string`):

Any name, e.g. 'qld-tenders'. Runs with the same name compare against each other: items get change_status new / changed / unchanged.

## `onlyNewItems` (type: `boolean`):

With a watch list name: skip (and don't charge for) items that were already seen and haven't changed.

## `slackWebhookUrl` (type: `string`):

Slack incoming-webhook URL. Gets a digest of new / changed items after each run.

## `telegramBotToken` (type: `string`):

From @BotFather. Use together with the chat ID.

## `telegramChatId` (type: `string`):

Chat, group or channel ID that receives the digest (e.g. -1001234567890).

## `discordWebhookUrl` (type: `string`):

Discord channel webhook URL. Gets the digest.

## `googleSheetsWebAppUrl` (type: `string`):

Deploy the 10-line Apps Script from the README in your sheet and paste its web app URL: every new / changed item is appended as a row.

## `notifyEmail` (type: `string`):

Email address for the digest (sent with Apify's send-mail Actor).

## Actor input object example

```json
{
  "locations": [
    "Paddington, QLD 4064"
  ],
  "listingType": "buy",
  "sites": [
    "realestate",
    "domain"
  ],
  "maxPages": 1,
  "maxListings": 20,
  "mergeAcrossSites": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "AU"
  },
  "watchListName": "my-watch-list",
  "onlyNewItems": false,
  "notifyEmail": "you@example.com"
}
```

# Actor output Schema

## `listings` (type: `string`):

Dataset of properties: address, parsed price, features, agency, agents, coordinates and links to each portal.

## `report` (type: `string`):

Searches run (site x suburb), pages read, listings found and any errors.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "locations": [
        "Paddington, QLD 4064"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "AU"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("he_work/au-property-listings").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "locations": ["Paddington, QLD 4064"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "AU",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("he_work/au-property-listings").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "locations": [
    "Paddington, QLD 4064"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "AU"
  }
}' |
apify call he_work/au-property-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,he_work/au-property-listings"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HKbRMl90dphHhdVdQ/builds/FOZ43uOe2bFvjNkKp/openapi.json