Domain.com.au Real Estate Scraper

Domain.com.au Real Estate Scraper extracts Australian property listings from Domain.com.au for sale, rent, and sold inventory. Use it when you need suburb-level comps, rental supply monitoring, investor research, agency/agent lead lists, or a repeatable dataset for dashboards and market analysis.

Use this actor for Domain.com.au property search pages, suburb slugs, and individual listing URLs. Do not use it for Realestate.com.au, commercial portals, or standalone Domain agent-profile search.

What Data Can You Extract?

Field group	Examples
Listing identity	listingId, listingUrl, listingType, status, sourceSearchUrl
Price and property	priceText, priceAmount, propertyType, bedrooms, bathrooms, parkingSpaces, landAreaSqm
Location	address, streetAddress, suburb, state, postcode, latitude, longitude
Detail enrichment	description, features, inspectionTimes, auctionDate, listedAt, soldDate
Media and contacts	imageUrls, floorplanUrls, videoUrl, agentNames, agentPhones, agencyName, agencyUrl
Provenance	scrapedAt, warnings

When To Use It

• Build comparable sales and active-listing datasets across Australian suburbs.
• Monitor rentals by suburb, bedroom count, and price band.
• Export agent and agency attribution for real estate lead workflows.
• Run scheduled market supply snapshots from consistent Domain search URLs.
• Scrape a small set of detail URLs for richer property descriptions and media.

Pricing

This actor uses Pay per event + platform usage.

Event	Price
Actor start	$0.00005
Listing returned	$0.004 per validated dataset row

Example: 100 listings cost about $0.40 in listing events, plus the tiny actor-start event and Apify platform usage for compute/proxy traffic. The actor logs the maximum event charge at run start and stops at maxResults.

Input Example

{
  "listingType": "sale",
  "locations": ["sydney-nsw-2000"],
  "maxResults": 20,
  "maxPagesPerSearch": 1,
  "enrichDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "AU"
  }
}

You can also paste a filtered Domain.com.au search URL:

{
  "startUrls": [{ "url": "https://www.domain.com.au/rent/melbourne-vic-3000/" }],
  "maxResults": 50,
  "enrichDetails": true
}

Output Example

{
  "listingId": "2020755515",
  "listingUrl": "https://www.domain.com.au/9-cox-avenue-bondi-beach-nsw-2026-2020755515",
  "sourceSearchUrl": "https://www.domain.com.au/sale/bondi-beach-nsw-2026/",
  "listingType": "sale",
  "priceText": "$1,250,000",
  "priceAmount": 1250000,
  "priceCurrency": "AUD",
  "address": "9 Cox Avenue, Bondi Beach NSW 2026",
  "bedrooms": 3,
  "bathrooms": 2,
  "parkingSpaces": 1,
  "agencyName": "Example Real Estate",
  "agentNames": ["Jane Smith"],
  "imageUrls": ["https://rimh2.domainstatic.com.au/example.jpg"],
  "scrapedAt": "2026-07-15T17:30:00.000Z",
  "warnings": []
}

Reliability Notes

Reliability comes from a layered route strategy. The actor begins with an AU residential browser session, then uses a bounded Domain data provider when the native page does not expose a complete listing, with current search discovery retained as a final recovery path.

While building this actor, I found that preserving one stable output contract mattered more than exposing the route used behind the scenes. Every recovered listing is therefore normalized into the same property schema, validated before storage, and billed only after the dataset write succeeds.

The actor keeps dataset rows homogeneous and stores operational details in key-value records. COMPLETE and PARTIAL both contain useful listing rows, while VALID_EMPTY means the requested filters were processed without a matching property. OUTPUT and RUN_SUMMARY identify the selected route for agents that need provenance.

API Usage

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/domain-com-au-real-estate-scraper').call({
  listingType: 'rent',
  locations: ['melbourne-vic-3000'],
  maxResults: 25,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Related Workflow Steps

For broader real estate owner enrichment, combine exported addresses with a skip-trace or property-owner workflow after reviewing local compliance requirements. Keep Domain listing scraping separate from agent-profile scraping so the data contract remains one record per property listing.

Legal And Compliance

This actor extracts publicly available web data from Domain.com.au. You are responsible for using the output lawfully, respecting applicable privacy, spam, contract, and real estate data rules, and honoring any obligations that apply to your use case.

Feedback

Open an Apify issue with the run ID, input, and the field that looked wrong. Run IDs make it possible to inspect RUN_SUMMARY, blocked routes, and dataset validation details without guessing.