# Allhomes Search Spider (`hello.datawizards/allhomes-search-spider`) Actor

Extract structured property sales and listing data from Allhomes by location. This Apify Actor collects prices, property types, beds, baths, agencies, and transaction dates—ideal for real estate market analysis, investment research, and PropTech automation.

- **URL**: https://apify.com/hello.datawizards/allhomes-search-spider.md
- **Developed by:** [datawizards](https://apify.com/hello.datawizards) (community)
- **Categories:** Agents, Automation, Real estate
- **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

***

## 🏡 Allhomes Search Spider · Apify Actor

Extract **property sales and listing intelligence** from **Allhomes search results** using clean, structured JSON — perfect for real estate analytics, market research, and investment insights.

Built and maintained by **[DataWizards](https://linkedin.com/in/data-wizards-aa8080342)**.

***

### 📌 What Is `Allhomes Search Spider`?

The **Allhomes Search Spider** Apify Actor enables you to **crawl and extract property transaction and listing data** from Allhomes based on a specific location slug (e.g. suburb, city, or postcode).

It gathers **key real estate attributes** such as property type, price, bedrooms, bathrooms, agency, and transaction dates — without manual browsing or scraping complexity.

This actor is ideal for **real estate analysts, property investors, data teams, and PropTech platforms**.

***

### 🧠 Key Features

- ✅ Extracts **property sales data by location**
- ✅ Structured **JSON output** ready for analytics
- ✅ Includes price, property type, beds, baths, parking
- ✅ Captures agency, address, postcode, and division
- ✅ Supports **Apify Proxy (RESIDENTIAL IPs)**
- ✅ Fast, scalable, and automation-ready
- ✅ Designed for Australian real estate research

***

### 🛠️ Input Schema

Provide a valid **Allhomes location slug** and enable Apify Proxy.

```json
{
  "Location": "sydney-nsw-2000",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

#### 🔐 Proxy Configuration

- **useApifyProxy**: Must be set to `true`
- **apifyProxyGroups**: `"RESIDENTIAL"` is recommended for accuracy and stability

***

### 📤 Output Example

```json
[
  {
    "date": "2025-12-24T00:00:00",
    "url": "https://www.allhomes.com.au/level-16-unit-1603-1-hosking-place-sydney-nsw-2000-16259836",
    "public_visible_date": "2025-11-04T13:18:06",
    "property_type": "APARTMENT",
    "bedrooms": 1,
    "bathrooms": 1,
    "parking": 0,
    "address": "1603/1 Hosking Place",
    "division": "Sydney",
    "postcode": "2000",
    "agency": "Sydney Cove Property",
    "price": 700000,
    "contractDate": "2025-12-24T00:00:00",
    "transferDate": 700000,
    "transfer_type": 700000,
    "transfer_label": 700000,
    "source": 700000
  }
]
```

***

### 📊 Data Highlights

- Property sale date and visibility date
- Full listing URL
- Property type (Apartment, House, etc.)
- Bedrooms, bathrooms, parking
- Address, postcode, and city division
- Selling agency
- Transaction and price-related metadata

***

### 🚀 Use Cases

- 🏘️ **Property Market Analysis** – Track prices by suburb or postcode
- 📈 **Investment Research** – Identify trends in apartment vs house sales
- 🧠 **PropTech Platforms** – Power dashboards and valuation tools
- 📊 **Data Aggregation** – Feed BI tools and internal analytics
- 🤖 **Automation Pipelines** – Schedule recurring market snapshots

***

### ✅ Best Practices

- Always use **RESIDENTIAL proxies** for consistent results
- Use valid and accurate **location slugs**
- Avoid excessive request frequency for large cities
- Store URLs or dates to prevent duplicate processing
- Combine with visualization tools for deeper insights

***

### 🤝 Support & Customization

Need **additional fields**, **simplified output**, or **new locations supported**?
**DataWizards are always ready for you.**

📩 **Email**: <hello.datawizard@gmail.com>
✉️ **Email Subject**: `Allhomes Search Spider – Support Request`
🔗 **LinkedIn**: <https://linkedin.com/in/data-wizards-aa8080342>

***

### 🧰 Need Something More?

Whether you want:

- Custom property filters
- Normalized or enriched datasets
- Additional Australian portals
- Bug fixes or performance improvements

👉 **DataWizards will build it for you.**

For more custom/simplified outputs or bug reports, please contact:
📧 **<hello.datawizard@gmail.com>**
✉️ **Subject**: `Custom Support – Allhomes Search Spider`

***

### 🐞 Feedback & Bug Reports

Found an issue or want a new feature?

📧 Email: **<hello.datawizard@gmail.com>**
✉️ Subject: `Bug Report – Allhomes Search Spider`
Or report directly via **Apify Issues**.

***

#### 🏁 Start extracting Australian real estate intelligence with **Allhomes Search Spider** —

your reliable solution for structured Allhomes property data.

***

# Actor input Schema

## `Location` (type: `string`):

The location for the spider.

## `itemLimit` (type: `integer`):

Specifies the maximum number of items to process.

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

Specifies proxy servers that will be used by the scraper in order to hide its origin.

## Actor input object example

```json
{
  "Location": "sydney-nsw-2000",
  "itemLimit": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {
    "itemLimit": 50,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("hello.datawizards/allhomes-search-spider").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 = {
    "itemLimit": 50,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("hello.datawizards/allhomes-search-spider").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 '{
  "itemLimit": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call hello.datawizards/allhomes-search-spider --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hello.datawizards/allhomes-search-spider"
        }
    }
}

```

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/qJHKfq4qKhv4d3211/builds/v4EgUhwEVUosc5h99/openapi.json