# Aus Properties and Details Scraper (`realestateapi/aus-properties-and-details-scraper`) Actor

Parses Australian property listings when current source access and intended use are permitted. Requests default to off; live field coverage remains unverified.

- **URL**: https://apify.com/realestateapi/aus-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Aus Properties and Details Scraper

This Actor is designed to parse public Australian property listing and search pages that expose JSON-LD or property cards. Its intended output fields cover listing identity, title, address, suburb, state, postcode, asking or sale price, currency, bedrooms, bathrooms, parking, land and floor areas, agent details, features, photos, and listing URL. Live extraction from the configured realestate.com.au page has not been verified; see Access and reliability.

### How to use

Provide one or more official HTTPS realestate.com.au listing or search URLs in `listingUrls`. A search page can yield multiple property cards, while a detail URL normally yields one richer record. `maxItems` is a hard output limit. The Actor makes no source request by default: the configured Chrome page remained blank and inconclusive, so set `sourceAccessConfirmed` only after the page is readable in Chrome and applicable source terms permit the intended collection and storage. This checkbox is an operator attestation, not permission. The Actor does not log in, bypass access controls, solve CAPTCHAs, or collect private information.

The source page is retained as `sourceUrl` so a record can be traced back to the page used for discovery. `listingUrl` is the canonical property URL when the page provides one. Relative links and image paths are resolved to absolute URLs. Prices are numeric when a page exposes them, while the original display string is kept in `priceText`; ranges use `priceMin` and `priceMax`. Dates such as `datePosted` are normalized to ISO 8601.

### Input example

```json
{
  "listingUrls": [
    "https://www.realestate.com.au/buy/in-australia/list-1"
  ],
  "maxItems": 25
}
```

### Output example

The following values are synthetic and illustrate the output shape only; they were not observed on a live listing page.

```json
{
  "recordType": "property-listing",
  "id": "property:145678901",
  "listingId": "145678901",
  "listingType": "buy",
  "propertyType": "House",
  "title": "Contemporary family home in Hawthorn East",
  "address": "14 Garden Street, Hawthorn East, VIC, 3123",
  "priceText": "1650000",
  "priceMin": 1650000,
  "priceMax": 1650000,
  "currency": "AUD",
  "bedrooms": 4,
  "bathrooms": 2,
  "parkingSpaces": 2,
  "listingUrl": "https://www.realestate.com.au/property-house-vic-hawthorn-east-145678901",
  "sourceUrl": "https://www.realestate.com.au/buy/in-australia/list-1"
}
```

### Run status

`OUTPUT_SUMMARY.status` is `SUCCEEDED` or `FAILED`; `runStatus` and `collectionStatus` are `COMPLETED`, `PARTIAL`, `FAILED`, or `SKIPPED_POLICY`. The summary includes bounded generic `failureReasons`, or a `policyReason` for a no-request policy skip. An explicit empty result succeeds with zero records. An unrecognized page or a failure with no saved property rows fails; if real rows were saved first, the run remains `SUCCEEDED/PARTIAL`. The dataset contains property listings only; errors are never emitted as diagnostic or placeholder records. Offline tests use synthetic data and do not verify live source extraction.

Optional values are consistently `null` or empty arrays when the page does not publish them. Export the dataset as JSON, CSV, Excel, or connect it to an integration in the Apify Console. Always respect the source website's terms, robots guidance, rate limits, privacy obligations, and local property-data rules.

### Access and reliability

Live source verification is currently incomplete. On 2026-09-27, connected Chrome opened the configured realestate.com.au URL but showed a blank white viewport with no readable listing structure. This does not establish whether the cause is the source, network, or browser rendering. There are no saved dataset rows to compare with the 28-field schema. No source-based enrichment was made; see `AGENTS.md` and `BROWSER_REVIEW.md`. The Actor does not follow redirects or impersonate Chrome. The checked-in parser tests use synthetic data and verify parsing logic only; they are not evidence of a successful live scrape.

# Actor input Schema

## `sourceAccessConfirmed` (type: `boolean`):

Set true only after a public listing page is readable in Chrome and applicable source terms authorize the intended collection and storage. This attestation is not permission; default execution makes zero requests.

## `listingUrls` (type: `array`):

Public realestate.com.au listing or search pages to read. Search pages may contain multiple property cards.

## `maxItems` (type: `integer`):

Upper bound for property records emitted by the run.

## Actor input object example

```json
{
  "sourceAccessConfirmed": false,
  "listingUrls": [
    "https://www.realestate.com.au/buy/in-australia/list-1"
  ],
  "maxItems": 25
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/aus-properties-and-details-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/aus-properties-and-details-scraper").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 '{}' |
apify call realestateapi/aus-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/aus-properties-and-details-scraper"
        }
    }
}
```

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/x1RmXOIsLkaaZd78Z/builds/rn5kIAb7mYYTu2CqU/openapi.json