# Property24 Price-Drop & New Listing Monitor (`hipersoft/property24-monitor`) Actor

Monitor Property24 (South Africa) on a schedule and get ONLY what changed since the last run: new listings, price drops and price increases. Runs inside Apify Schedules, n8n, Make or Zapier — quiet runs return nothing, so it is cheap to watch a search 24/7 for buyers, agents and property alerts.

- **URL**: https://apify.com/hipersoft/property24-monitor.md
- **Developed by:** [hiper soft](https://apify.com/hipersoft) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.0015 / change detected

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?

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

## 🔔 Property24 Price-Drop & New Listing Monitor

**Watch any Property24 search and get alerted the moment something changes.** Point this monitor at a South African property search — for sale or to rent, any city, suburb or filtered search — put it on a schedule, and each run returns **only what changed since the last run**: brand-new listings, price drops, price increases and delistings. Quiet runs return nothing, so you can watch a search every few minutes, all day, and only ever see real movement.

Built for **automation**: drop it into **Apify Schedules**, **n8n**, **Make** or **Zapier** and turn every change into an email, a Slack message, a Google Sheet row or a webhook.

### Why a monitor instead of a scraper?

A scraper gives you *everything* every time — and you then have to figure out what's new. This monitor remembers what it saw last time and hands you a clean feed of **just the changes**:

- 🆕 **New listings** — the moment a property matching your search goes live.
- 📉 **Price drops** — with the old price, new price, amount and percentage dropped.
- 📈 **Price increases** — optional, on by default.
- 🗑️ **Delistings** — listings that were sold, withdrawn or expired.

Perfect for **buyers hunting a specific area**, **agents tracking the competition**, **investors watching price movements**, and anyone building **property alerts**.

### How it works

1. Give it a **search** — a location path like `cape-town/western-cape/432`, or paste one or more Property24 results-page **Start URLs** from your browser.
2. Put it on a **schedule** (e.g. every 15 minutes) in Apify or your automation tool.
3. **First run** quietly records the current listings as a baseline and returns nothing — so a fresh schedule doesn't dump the whole search at you. (Prefer the full list up front? Turn on **Emit all listings on the first run**.)
4. **Every run after that** returns only the changes since the previous run.

Each monitor keeps its own separate memory, so you can run several different searches side by side without them interfering — just give each one a **Monitor name**.

### What you get

One row per detected change:

| Field | Description |
| --- | --- |
| `changeType` | `new`, `price_drop`, `price_increase` or `removed`. |
| `listingNumber` | Property24 listing reference. |
| `title` | Listing title (e.g. "3 Bedroom Apartment for sale in Marina Da Gama"). |
| `price` | Current price as a number, in South African Rand. |
| `priceText` | Price exactly as shown (e.g. "R 3 300 000"). |
| `currency` | Currency code (ZAR). |
| `oldPrice` / `newPrice` | Previous and current price (on price changes). |
| `dropAmount` / `dropPercent` | How much the price fell (on price drops). |
| `increaseAmount` / `increasePercent` | How much the price rose (on price increases). |
| `suburb` | Suburb / area name. |
| `bedrooms`, `bathrooms`, `parking` | Room and parking counts. |
| `floorSize`, `erfSize` | Floor and erf / plot size, when shown. |
| `agency` | Listing agency, when shown. |
| `image` | Main listing image URL. |
| `url` | Link to the property page. |
| `firstSeenAt` | When this monitor first saw the listing. |
| `lastSeenAt` | When the listing was last seen (on delistings). |
| `detectedAt` | When this change was detected. |

### Example change row

```json
{
  "changeType": "price_drop",
  "listingNumber": "117588912",
  "title": "3 Bedroom Apartment for sale in Marina Da Gama",
  "price": 3100000,
  "oldPrice": 3300000,
  "newPrice": 3100000,
  "dropAmount": 200000,
  "dropPercent": 6.06,
  "suburb": "Marina Da Gama",
  "bedrooms": 3,
  "bathrooms": 2,
  "url": "https://www.property24.com/for-sale/marina-da-gama/cape-town/western-cape/10213/117588912",
  "detectedAt": "2026-09-05T12:34:56.000Z"
}
```

### How to use it

1. Add **Property24 Price-Drop & New Listing Monitor** to your Apify account and open its input.
2. Choose the **Listing intent** — For sale or To rent — and enter a **Location path** like `cape-town/western-cape/432` (copy it from a Property24 results URL), **or** paste one or more **Start URLs** from your browser.
3. Optionally set a **Monitor name** so this search keeps its own memory.
4. Save it, then create a **Schedule** (e.g. every 15 or 30 minutes) — or trigger it from n8n, Make or Zapier.
5. Connect the output to email, Slack, a spreadsheet or a webhook and let the alerts come to you.

### Input

```json
{
  "intent": "for-sale",
  "locationUrlPath": "cape-town/western-cape/432",
  "maxItems": 200,
  "monitorName": "cape-town-houses",
  "emitBaselineOnFirstRun": false,
  "detectPriceIncrease": true,
  "detectRemovals": true
}
```

| Field | Description |
| --- | --- |
| `startUrls` | Optional Property24 results-page URLs to watch. Overrides intent + location path. |
| `intent` | `for-sale` or `to-rent`. |
| `locationUrlPath` | Location path `city/province/areaId`, e.g. `cape-town/western-cape/432`. |
| `maxItems` | How many listings from the top of the search to check each run. `0` = no limit. |
| `monitorName` | Optional label so this search keeps its own separate memory. |
| `emitBaselineOnFirstRun` | Output every current listing as `new` on the first run instead of seeding silently. |
| `detectPriceIncrease` | Also report price increases (default on). |
| `detectRemovals` | Also report delisted listings (default on). |

### FAQ

**How often should I run it?**
As often as you like — every 15 or 30 minutes works well. Runs with no changes return nothing, so frequent checks stay cheap.

**Will the first run flood me with results?**
No. By default the first run silently records a baseline and returns nothing; you only start getting rows from the second run onward. Turn on **Emit all listings on the first run** if you'd rather get the full list up front.

**Can I watch several searches at once?**
Yes. Give each one a different **Monitor name** and each keeps its own independent memory of what it has seen.

**Does it work for rentals too?**
Yes — set **Listing intent** to *To rent*, or paste a to-rent results URL.

**What export and integration options are there?**
JSON, CSV, Excel and XML, plus the Apify API, webhooks and native integrations with n8n, Make, Zapier and more.

# Actor input Schema

## `startUrls` (type: `array`):

Optional. One or more Property24 search/result page URLs to monitor (e.g. a for-sale or to-rent results page for a city, suburb or filtered search). Paste the URL straight from your browser. When set, this overrides the Intent and Location path fields. Each run checks these searches and reports only what changed since the previous run.

## `intent` (type: `string`):

Watch properties for sale or to rent. Used together with the Location path when no Start URLs are provided.

## `locationUrlPath` (type: `string`):

The Property24 location path to watch, in the form 'city/province/areaId' — for example 'cape-town/western-cape/432' or 'johannesburg/gauteng/95'. Copy it straight out of a Property24 results URL (the part after /for-sale/ or /to-rent/). Ignored when Start URLs are set.

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

How many listings from the top of the search to check each run (0 = no limit). The newest listings appear first, so 200 comfortably covers new arrivals and recent price changes for most searches. Delisted-listing detection is only reported when this cap is not reached.

## `monitorName` (type: `string`):

Optional label for this monitor. Each named monitor keeps its own separate memory of what it has already seen, so you can run several different searches side by side without them interfering. Leave blank to derive it automatically from the search.

## `emitBaselineOnFirstRun` (type: `boolean`):

By default the very first run silently records the current listings as a baseline and returns nothing, so a fresh schedule does not dump the whole search at you. Turn this on to instead output every current listing as 'new' on that first run.

## `detectPriceIncrease` (type: `boolean`):

Report listings whose asking price went up since the last run, not just price drops.

## `detectRemovals` (type: `boolean`):

Report listings that were present before but have now disappeared from the search (sold, withdrawn or expired). Only reported when the whole search fits within 'Max listings to check per run'.

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

Optional. This monitor runs fine without a proxy and none is used by default.

## Actor input object example

```json
{
  "intent": "for-sale",
  "locationUrlPath": "cape-town/western-cape/432",
  "maxItems": 200,
  "emitBaselineOnFirstRun": false,
  "detectPriceIncrease": true,
  "detectRemovals": true
}
```

# Actor output Schema

## `results` (type: `string`):

The detected changes as dataset items.

# 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 = {
    "locationUrlPath": "cape-town/western-cape/432"
};

// Run the Actor and wait for it to finish
const run = await client.actor("hipersoft/property24-monitor").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 = { "locationUrlPath": "cape-town/western-cape/432" }

# Run the Actor and wait for it to finish
run = client.actor("hipersoft/property24-monitor").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 '{
  "locationUrlPath": "cape-town/western-cape/432"
}' |
apify call hipersoft/property24-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hipersoft/property24-monitor"
        }
    }
}
```

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/IU0OKVKHy1QiMCp6X/builds/xTh1J3uKNIf6xp1Gn/openapi.json