# Property24 $1💰 Buy, Rent, Sell, Commercial Scraper (`abotapi/property24-scraper`) Actor

From $1/1K. Extract structured property listings from Property24, South Africa’s largest property portal. Search by location or use Property24 URLs. Get 50+ fields including price, beds, baths, sizes, GPS coordinates, photos, property details, and agent/agency information.

- **URL**: https://apify.com/abotapi/property24-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** Real estate, Developer tools, Automation
- **Stats:** 9 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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.
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?

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

## Property24 Scraper (South Africa)

Extract structured property listings from Property24, South Africa's largest property portal. Get price, bedrooms, bathrooms, floor and erf size, GPS coordinates, the full property overview, every photo, agent and agency details, and 50+ fields per listing. Two modes: search by location, or paste Property24 search and listing URLs directly.

### Why this scraper

- **More fields than other Property24 scrapers.** Includes GPS latitude and longitude, numeric floor and erf size, postal code, the complete grouped property overview (rooms, external features, building, security), nearby suburbs, listing date, and full multi-size photo URLs, on top of everything the well-known alternatives return.
- **Lower running cost.** A lean fetching pipeline keeps compute and bandwidth small, so you pay for residential bandwidth only on the pages that need it; turn detail fetching off for a search-only run that is far cheaper.
- **Better reliability.** Country-rotating Residential exits (South Africa first) with a backup pool, health monitoring, and automatic recovery keep runs completing even when individual exits are throttled.
- **Two ways to target data.** Search by any suburb, city or province name (resolved automatically), or paste Property24 URLs (search pages paginate forward, single-listing URLs are fetched directly).
- **Honest filtering.** Price, bedroom, property type, sort and auction filters are applied both in the search URL and on the returned data, so the results actually match what you asked for.
- **Clean, flat output.** One record per listing, ready for spreadsheets, BI tools, ETL pipelines, and CRMs.

### Feature comparison

| Capability | This scraper | Typical alternative |
| --- | --- | --- |
| Search by location name | Yes (auto-resolved) | URL only on some |
| Direct URL mode (search + single listing) | Yes | Partial |
| GPS latitude / longitude | Yes | Often missing |
| Numeric floor size and erf size | Yes | Text only or missing |
| Full grouped property overview | Yes | Partial |
| All photos (multi-size URLs) | Yes | Yes |
| Agent and agency details | Yes | Yes |
| Country-rotating residential + backup failover | Yes | No |
| Automatic proxy failover | Yes | No |
| Price / bedroom / type filters | Yes (verified narrowing) | Varies |

### Data you get

> Sample shape, values are illustrative placeholders, not from a live listing.

| Field | Example |
| --- | --- |
| listingNumber | `100000001` |
| url | `https://www.property24.com/for-sale/sample-suburb/sample-city/western-cape/0000/100000001` |
| listingType | `For Sale` |
| title | `3 Bedroom House for sale in Sample Suburb` |
| price | `2600000` |
| displayPrice | `R 2 600 000` |
| currency | `ZAR` |
| priceOnApplication | `false` |
| bedrooms | `3` |
| bathrooms | `2` |
| garages | `2` |
| parkingSpaces | `4` |
| floorSize | `248` |
| erfSize | `554` |
| propertyType | `House` |
| suburbName | `Sample Suburb` |
| cityName | `Sample City` |
| provinceName | `Western Cape` |
| suburbId / cityId / provinceId | `0000` / `0000` / `9` |
| latitude / longitude | `-33.0000` / `18.0000` |
| descriptionHeader | `Sample headline for the listing.` |
| description | `Full listing description text appears here when fetchDetails is on.` |
| agencyName | `Sample Agency` |
| agencyId | `00000` |
| agencyLogoUrl | `https://images.prop24.com/000000000/Fit450x225` |
| agentName | `Agent Name` |
| agentId | `000000` |
| contacts | `[{ "id": 0, "name": "Agent Name", "photoUrl": "...", "profileUrl": "...", "hasContactNumber": true }]` |
| keyFeatures | `["Bedrooms 3", "Bathrooms 2", "Garden"]` |
| propertyOverview | `{ "Listing Number": "100000001", "Type of Property": "House", "Erf Size": "554 m2" }` |
| details | `[{ "category": "Rooms", "categoryItems": { "Bedrooms": "3" } }]` |
| photos | `[{ "imageIdentifier": "000000000", "thumbnailUrl": "...", "imageUrl": "...", "largeImageUrl": "..." }]` |
| photoCount | `21` |
| nearbySuburbs | `["Sample Suburb A", "Sample Suburb B"]` |
| listingMedia | `{ "youTubeVideoTourId": "xxxxxxxxxxx" }` |
| onShow / auction / repossessed | `false` / `false` / `false` |
| datePosted | `2026-01-01` |
| scrapedAt | `2026-01-01T00:00:00.000Z` |

Detail-only fields (GPS, full description, photos, agent and agency, property overview, nearby suburbs) populate when **Fetch Detail Pages** is on.

### How to use

**Search by location (basic)**

```json
{
  "mode": "search",
  "listingType": "for-sale",
  "locations": ["Cape Town"],
  "maxListings": 50
}
```

**Search with filters**

```json
{
  "mode": "search",
  "listingType": "for-sale",
  "locations": ["Sandton", "Umhlanga"],
  "propertyType": "house",
  "minPrice": 1000000,
  "maxPrice": 3000000,
  "minBedrooms": 3,
  "sortBy": "price-asc",
  "maxListings": 200,
  "fetchDetails": true
}
```

**Rentals**

```json
{
  "mode": "search",
  "listingType": "to-rent",
  "locations": ["Cape Town"],
  "maxListings": 100
}
```

**Direct URLs (search pages and single listings, mixed)**

```json
{
  "mode": "url",
  "urls": [
    "https://www.property24.com/for-sale/cape-town/western-cape/432",
    "https://www.property24.com/for-sale/belhar/cape-town/western-cape/8132/117073882"
  ],
  "maxPages": 3
}
```

### Input parameters

| Parameter | Type | Default | Description |
| --- | --- | --- | --- |
| mode | string | `search` | `search` builds URLs from the fields below; `url` scrapes the URLs you paste. |
| listingType | string | `for-sale` | `for-sale` (Buy), `to-rent` (Rent), `commercial-for-sale`, or `commercial-to-rent` (search mode). The commercial options search Property24's separate commercial-property vertical. |
| locations | array | `["Cape Town"]` | Suburb, city or province names (search mode). Resolved automatically. |
| propertyType | string | `any` | Narrow to house, apartment, townhouse, vacant land, farm, commercial, or industrial. |
| minPrice / maxPrice | integer | none | Price range in Rand (search mode). |
| minBedrooms / maxBedrooms | integer | none | Bedroom range (search mode). |
| minBathrooms | integer | none | Minimum bathrooms (search mode). |
| parkingSpaces | integer | none | Minimum parking spaces or garages (search mode). |
| minErfSize / minFloorSize | integer | none | Minimum erf (land) / floor size in m² (search mode). |
| hasPool | boolean | `false` | Only listings with a swimming pool. |
| hasGarden | boolean | `false` | Only listings with a garden. |
| hasFlatlet | boolean | `false` | Only listings with a flatlet / granny flat. |
| petFriendly | boolean | `false` | Only pet-friendly listings. |
| securityEstate | boolean | `false` | Only listings inside a security estate. |
| repossessed | boolean | `false` | Only bank-repossessed properties. |
| retirement | boolean | `false` | Only retirement listings. |
| sortBy | string | `default` | `newest`, `price-asc`, `price-desc`, or `size`. |
| onShowOnly | boolean | `false` | Only listings with a scheduled show day. |
| auctionsOnly | boolean | `false` | Only properties going to auction. |
| urls | array | example | Property24 URLs to scrape (url mode). |
| fetchDetails | boolean | `true` | Open each listing for GPS, full description, photos, agent, agency, and the property overview. |
| maxPages | integer | none | Optional bound on result pages walked per search (about 45 listings per page). Leave empty to walk every result page; the run size is controlled by maxListings, which this field defers to. |
| maxListings | integer | `20` | THE run cap: max listings across all searches. `0` for unlimited. |
| resumeFromRunId | string | none | ID of a previous run of this actor (or a dataset ID). Listings already in that dataset are skipped, so this run returns only NEW listings (a delta). |
| proxy | object | Apify Residential | Connection settings. Residential is the default and recommended; Datacenter is not recommended (Property24 rejects most Datacenter connections). |

### Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape — the Apify dataset is never changed.

**What gets written to the connector:** a condensed, human-readable **summary** of each record — not the full JSON. Each item becomes one entry with a **title** and its key fields flattened to plain text. The **complete record always stays in the Apify dataset**.

1. Authorize a connector once under **Apify → Settings → Integrations** (Notion, Linear, Airtable, or Apify).
2. Select it in the **"Pipe results into your apps"** input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For **Notion**, also set `notionParentPageUrl` to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

### Output example

> Sample shape, values are illustrative placeholders, not from a live listing.

```json
{
  "listingNumber": "100000001",
  "url": "https://www.property24.com/for-sale/sample-suburb/sample-city/western-cape/0000/100000001",
  "listingType": "For Sale",
  "title": "3 Bedroom House for sale in Sample Suburb",
  "price": 2600000,
  "displayPrice": "R 2 600 000",
  "currency": "ZAR",
  "priceOnApplication": false,
  "bedrooms": 3,
  "bathrooms": 2,
  "garages": 2,
  "floorSize": 248,
  "erfSize": 554,
  "propertyType": "House",
  "suburbName": "Sample Suburb",
  "cityName": "Sample City",
  "provinceName": "Western Cape",
  "provinceId": "9",
  "latitude": -33.0000,
  "longitude": 18.0000,
  "descriptionHeader": "Sample headline for the listing.",
  "description": "Full listing description text appears here when fetchDetails is on.",
  "agencyName": "Sample Agency",
  "agentName": "Agent Name",
  "contacts": [{ "id": 0, "name": "Agent Name", "hasContactNumber": true }],
  "keyFeatures": ["Bedrooms 3", "Bathrooms 2", "Garden"],
  "propertyOverview": { "Type of Property": "House", "Erf Size": "554 m2" },
  "photos": [{ "imageIdentifier": "000000000", "imageUrl": "https://images.prop24.com/000000000/Ensure960x540" }],
  "photoCount": 21,
  "datePosted": "2026-01-01",
  "scrapedAt": "2026-01-01T00:00:00.000Z"
}
```

### Plan and proxy notes

- **Residential proxy (default, recommended)** is required for reliable results. It needs an Apify plan that includes Residential proxy. The actor rotates Residential exits across countries (South Africa first) and uses a backup pool as a last resort, so runs keep completing even under throttling.
- **Datacenter proxy is not recommended.** Property24 rejects most Datacenter connections, especially on listing detail pages, so runs may be slow or return fewer details. The actor will warn you and still attempt to fail over to Residential, but selecting Residential from the start is far more reliable.
- For the lowest cost, keep `fetchDetails` off to collect search-result fields only, then re-run with `fetchDetails` on for the listings you care about.

### Pricing

This actor uses pay-per-event pricing:

| Event | Price (USD) | When it is charged |
| --- | --- | --- |
| Actor start | $0.08 | Once per run, when it starts and initializes. |
| Listing result | $0.003 | Once per listing returned to the dataset (search-result fields). |
| Listing detail enrichment | $0.0008 | Once per listing whose detail page is fetched. Only charged when `fetchDetails` is on. |

A search-result-only run (`fetchDetails` off) costs `$0.08 + $0.003 per listing`. A detail-enriched run adds `$0.0008 per listing`. Example: 50 listings with details ≈ `$0.08 + 50 × $0.0038 = $0.27`.

# Actor input Schema

## `mode` (type: `string`):

How to find listings. 'Search by Location' builds Property24 search URLs from the fields below. 'Direct URLs' scrapes the Property24 search or listing URLs you paste.

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

Which Property24 vertical to search (Search mode only). Buy and Rent are residential; the two Commercial options search Property24's separate commercial-property vertical.

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

Place names to search (Search mode only). Type a suburb, city or province, e.g. 'Cape Town', 'Sandton', 'Western Cape', 'Umhlanga'. Each name is resolved to the matching Property24 area automatically. Multiple locations supported.

## `propertyType` (type: `string`):

Narrow to one property type (Search mode only). Applied to results.

## `minPrice` (type: `integer`):

Minimum price in Rand (Search mode only). Applied both in the search URL and to results.

## `maxPrice` (type: `integer`):

Maximum price in Rand (Search mode only). Applied both in the search URL and to results.

## `minBedrooms` (type: `integer`):

Minimum number of bedrooms (Search mode only). Applied both in the search URL and to results.

## `maxBedrooms` (type: `integer`):

Maximum number of bedrooms (Search mode only). Applied to results.

## `sortBy` (type: `string`):

Result ordering (Search mode only).

## `onShowOnly` (type: `boolean`):

Only listings with a scheduled show day (Search mode only).

## `auctionsOnly` (type: `boolean`):

Only properties going to auction (Search mode only).

## `minBathrooms` (type: `integer`):

Minimum number of bathrooms (Search mode only). Applied in the search URL and to results.

## `parkingSpaces` (type: `integer`):

Minimum parking spaces or garages (Search mode only).

## `minErfSize` (type: `integer`):

Minimum erf (land) size in square metres (Search mode only).

## `minFloorSize` (type: `integer`):

Minimum floor size in square metres (Search mode only).

## `hasPool` (type: `boolean`):

Only listings with a swimming pool (Search mode only).

## `hasGarden` (type: `boolean`):

Only listings with a garden (Search mode only).

## `hasFlatlet` (type: `boolean`):

Only listings with a flatlet / granny flat (Search mode only).

## `petFriendly` (type: `boolean`):

Only pet-friendly listings (Search mode only).

## `securityEstate` (type: `boolean`):

Only listings inside a security estate (Search mode only).

## `repossessed` (type: `boolean`):

Only bank-repossessed properties (Search mode only).

## `retirement` (type: `boolean`):

Only retirement listings (Search mode only).

## `urls` (type: `array`):

Property24 search-result or single-listing URLs to scrape (URL mode only). Multi-URL supported. Filter fields are ignored in this mode. For search URLs, pagination starts at the page in the URL and walks forward.

## `fetchDetails` (type: `boolean`):

Open each listing to add GPS coordinates, full description, all photos, agent and agency details, the full property overview (erf and floor size, rooms, features, security), and points of interest. Turn off for a faster, cheaper run with search-result fields only.

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

Optional bound on result pages walked per search (about 45 listings per page). Leave empty to walk every result page; the run size is controlled by Max Listings, which this field defers to.

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

THE run cap: maximum listings to return across all searches. Default 20. Set 0 for unlimited. For large pulls, add many locations or price bands; a single Property24 search exposes a finite number of pages.

## `resumeFromRunId` (type: `string`):

Optional. ID of a previous run of this actor (or a dataset ID). Listings already in that dataset are skipped, so this run returns only NEW listings (a delta). Combine both runs' datasets for the full set. Max Listings then counts only the new listings.

## `proxy` (type: `object`):

Residential proxy is required for reliable results. Property24 rejects most Datacenter connections (especially on listing detail pages), so Datacenter is not recommended. The actor rotates Residential exits across countries (South Africa first) and uses a backup pool when needed. Residential proxy needs a paid Apify plan.

## `mcpConnectors` (type: `array`):

Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON — the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "listingType": "for-sale",
  "locations": [
    "Cape Town"
  ],
  "propertyType": "any",
  "sortBy": "default",
  "onShowOnly": false,
  "auctionsOnly": false,
  "hasPool": false,
  "hasGarden": false,
  "hasFlatlet": false,
  "petFriendly": false,
  "securityEstate": false,
  "repossessed": false,
  "retirement": false,
  "urls": [
    "https://www.property24.com/for-sale/cape-town/western-cape/432"
  ],
  "fetchDetails": true,
  "maxListings": 20,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (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 = {
    "mode": "search",
    "locations": [
        "Cape Town"
    ],
    "urls": [
        "https://www.property24.com/for-sale/cape-town/western-cape/432"
    ],
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/property24-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 = {
    "mode": "search",
    "locations": ["Cape Town"],
    "urls": ["https://www.property24.com/for-sale/cape-town/western-cape/432"],
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/property24-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 '{
  "mode": "search",
  "locations": [
    "Cape Town"
  ],
  "urls": [
    "https://www.property24.com/for-sale/cape-town/western-cape/432"
  ],
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call abotapi/property24-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/property24-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/rwfuZfOLbo4xd4imD/builds/ShMI7lVkbE8u3uECr/openapi.json