# Australian Real Estate Agency Directory Scraper (`realestateapi/australian-real-estate-pro-properties-and-details-scraper`) Actor

Collects public OpenStreetMap real-estate agency records across Sydney, Melbourne, Brisbane, Perth, and Adelaide. This is an agency directory, not a property-listing scraper.

- **URL**: https://apify.com/realestateapi/australian-real-estate-pro-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

## Australian Real Estate Agency Directory Scraper

This Actor collects real-estate agency directory records from public OpenStreetMap data for Sydney, Melbourne, Brisbane, Perth, and Adelaide. It returns agencies and their mapped locations; it does not scrape property listings. The primary query uses Overpass nwr selectors for nodes, ways, and relations. If Overpass fails or returns no agencies, the Actor uses a rate-limited Nominatim fallback.

### Input

- cities: supported Australian search areas.
- maxItems: maximum unique OSM agencies to save.
- preferOverpass: query Overpass first; set false to use Nominatim only.
- overpassEndpoint: fixed public Overpass endpoint (`https://overpass-api.de/api/interpreter`); other hosts and paths are rejected.
- timeoutMs: timeout for each OSM request.

### Output

Records retain flat fields for compatibility and add nested agency, osm, location, contact, and provenance objects. `osm.tags` contains the tags returned by the selected source; Nominatim may return only `extratags`, so its `category`/`type` classification is normalized separately to `agency.officeType` without being presented as a raw tag. `address` is populated only when OSM address tags include both a house number and street. A nearby Nominatim label is stored separately as `geocoderDisplayName`; it must not be read as a confirmed agency address. `city` is populated only when the geocoder returns a city value, while `sourceCity` identifies the requested search area.

The browserVerification object appears only on saved rows that were manually checked in Chrome; it is review metadata, not a claim that every Actor-run record received a browser review.

Overpass access restrictions and rate limits stop collection without a Nominatim retry. Network/service failures and valid empty Overpass results may use the documented, rate-limited Nominatim fallback. `OUTPUT.recordCount` and `OUTPUT.successfulItems` are run-local counts; the default dataset can also contain records from earlier runs.

### Synthetic output example

The values below are synthetic and show structure only. They are not a current OSM record.

```json
{
  "recordType": "agency-directory",
  "osmType": "node",
  "osmId": 1001,
  "name": "Example Realty",
  "city": "Sydney",
  "state": "New South Wales",
  "country": "Australia",
  "postcode": "2000",
  "address": "Unit 4 12 Example Road",
  "geocoderDisplayName": "12 Example Road, Sydney, 2000",
  "latitude": -33.86,
  "longitude": 151.21,
  "website": "https://example.invalid",
  "email": "hello@example.invalid",
  "phone": "+61 2 0000 0000",
  "openingHours": "Mo-Fr 09:00-17:00",
  "sourceCity": "Sydney",
  "sourceMode": "overpass-nwr",
  "sourceUrl": "https://overpass-api.de/api/interpreter",
  "scrapedAt": "2026-09-27T00:00:00.000Z",
  "agency": {
    "name": "Example Realty",
    "officeType": "estate_agent",
    "operator": "Example Realty Group",
    "checkDate": "2026-09-01",
    "localizedNames": { "zh": "示例地产" }
  },
  "osm": {
    "type": "node",
    "id": 1001,
    "url": "https://www.openstreetmap.org/node/1001",
    "tags": {
      "name": "Example Realty",
      "office": "estate_agent",
      "addr:unit": "4",
      "addr:housenumber": "12",
      "addr:street": "Example Road",
      "addr:postcode": "2000"
    }
  },
  "location": {
    "latitude": -33.86,
    "longitude": 151.21,
    "address": {
      "unit": "4",
      "houseNumber": "12",
      "street": "Example Road",
      "postcode": "2000",
      "formatted": "Unit 4 12 Example Road"
    },
    "city": "Sydney",
    "locality": null,
    "state": "New South Wales",
    "country": "Australia",
    "postcode": "2000",
    "postcodeSource": "osm-tag",
    "geocoderDisplayName": "12 Example Road, Sydney, 2000"
  },
  "contact": {
    "website": "https://example.invalid",
    "email": "hello@example.invalid",
    "phone": "+61 2 0000 0000",
    "openingHours": "Mo-Fr 09:00-17:00"
  },
  "provenance": {
    "provider": "OpenStreetMap",
    "attribution": "© OpenStreetMap contributors",
    "sourceMode": "overpass-nwr",
    "sourceCity": "Sydney",
    "sourceUrl": "https://overpass-api.de/api/interpreter",
    "objectUrl": "https://www.openstreetmap.org/node/1001",
    "retrievedAt": "2026-09-27T00:00:00.000Z"
  }
}
```

### Verification and attribution

The five saved Sydney rows were compared with their exact OSM object pages in connected Chrome on 2026-09-27. Their historical scrapedAt values remain unchanged. See BROWSER_REVIEW.md. OSM content is attributed to © OpenStreetMap contributors; the public OSM object URL is retained in each record.

### Run status

`OUTPUT.status` and `runStatus` are `SUCCEEDED` or `FAILED`. Valid empty responses complete successfully. If Overpass fails and fallback records are saved, the run remains `SUCCEEDED` with `collectionStatus: PARTIAL`; source or dataset failures with zero saved agency rows report `FAILED`. `recordCount` and `successfulItems` count records saved by this run, while the local dataset can also contain rows from earlier runs. Failures are logged, never emitted as diagnostic or placeholder dataset rows.

# Actor input Schema

## `cities` (type: `array`):

Australian cities to query. Supported defaults are Sydney, Melbourne, Brisbane, Perth, and Adelaide.

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

Maximum number of unique agency records to save.

## `preferOverpass` (type: `boolean`):

Query all OpenStreetMap nodes, ways, and relations first; use the public geocoder only as a conservative fallback when Overpass is unavailable.

## `overpassEndpoint` (type: `string`):

The configured public Overpass endpoint. Alternate hosts and paths are rejected.

## `timeoutMs` (type: `integer`):

Timeout in milliseconds for each OpenStreetMap request.

## Actor input object example

```json
{
  "cities": [
    "Sydney",
    "Melbourne",
    "Brisbane",
    "Perth",
    "Adelaide"
  ],
  "maxItems": 5,
  "preferOverpass": true,
  "overpassEndpoint": "https://overpass-api.de/api/interpreter",
  "timeoutMs": 30000
}
```

# 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/australian-real-estate-pro-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/australian-real-estate-pro-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/australian-real-estate-pro-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/australian-real-estate-pro-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/jCXH07jofMLJ8mqOd/builds/qbbNvum3laIA5G9l9/openapi.json