# Real Estate Listing Monitor – Price and Status Changes (`signal_lab/real-estate-listing-monitor`) Actor

Monitor public property listing URLs for price, availability, and status changes using JSON-LD or optional CSS selectors with persistent state.

- **URL**: https://apify.com/signal\_lab/real-estate-listing-monitor.md
- **Developed by:** [Signal Lab](https://apify.com/signal_lab) (community)
- **Categories:** Real estate, Automation, Marketing
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 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

## Real Estate Listing Monitor – Price and Status Changes

Monitor public property pages for price drops, availability changes, and listing-status updates. Repeated runs keep a compact baseline so each result can show what changed and preserve the source URL.

### Run a verified example

[Monitor a property listing price](https://apify.com/signal_lab/real-estate-listing-monitor/examples/monitor-a-property-listing-price) opens a ready-to-run public task. Start with the verified fixture, then replace it with a compatible public listing URL.

### What you can do

- Track a focused acquisition watchlist.
- Detect price and sale-status changes on a schedule.
- Export normalized listing events to CSV, Excel, JSON, or a webhook.
- Keep current and previous values together for evidence-backed alerts.

### Start quickly

Run the built-in public fixture first, then replace it with a small list of compatible property-detail pages.

```json
{
  "listingUrls": [
    "https://signal-lab-tools.vitaxastar.chatgpt.site/fixtures/real-estate-listing"
  ],
  "emitOnlyChanges": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxItems": 5
}
```

1. Add public detail URLs to `listingUrls`.
2. Keep `emitOnlyChanges` off for the first baseline run.
3. Add CSS selectors only when the page does not expose usable structured metadata.
4. Keep `useApifyProxy` off for accessible pages; enable it when a public source blocks cloud requests.
5. Save the input as a task, enable change-only output, and add a schedule.

### Output

Each successful row can include title, address, current and previous price, currency, price change, current and previous status, change flags, description, image, source URL, and scrape time. Fully blocked or unusable inputs fail honestly instead of producing misleading rows.

### Troubleshooting

- **No listing found:** use a public property-detail page rather than a search page.
- **Price or status missing:** provide the optional CSS selectors shown in the input.
- **No change rows:** turn off `emitOnlyChanges` to inspect the current baseline.
- **Blocked page:** retry with Apify Proxy enabled; residential access may be required and proxy usage is billed separately. Choose an accessible source and follow its terms—the Actor does not bypass access controls.

### Free workflow guide

See the [real-estate price alert workflow, sample input, output fields, and FAQ](https://signal-lab-tools.vitaxastar.chatgpt.site/workflows/real-estate-price-alerts).

### Pricing and responsible use

Launch pricing is **$3.00 per 1,000 successful listing rows** plus the small start event shown in the Pricing tab. You pay for rows actually produced. Collect only public data you are authorized to use.

# Actor input Schema

## `listingUrls` (type: `array`):

Public property listing detail URLs.

## `emitOnlyChanges` (type: `boolean`):

Skip unchanged listings after the first run.

## `titleSelector` (type: `string`):

Optional selector when no structured title is available.

## `priceSelector` (type: `string`):

Optional selector when no structured price is available.

## `statusSelector` (type: `string`):

Optional selector for availability or sale status.

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

Optional Apify Proxy configuration. Residential access may be required for protected public pages.

## `stateStoreName` (type: `string`):

Named key-value store used to compare this run with previous runs.

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

Hard cap for emitted dataset rows and pay-per-event charges.

## Actor input object example

```json
{
  "listingUrls": [
    "https://signal-lab-tools.vitaxastar.chatgpt.site/fixtures/real-estate-listing"
  ],
  "emitOnlyChanges": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxItems": 5
}
```

# Actor output Schema

## `results` (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 = {
    "listingUrls": [
        "https://signal-lab-tools.vitaxastar.chatgpt.site/fixtures/real-estate-listing"
    ],
    "emitOnlyChanges": false,
    "proxyConfiguration": {
        "useApifyProxy": false
    },
    "maxItems": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("signal_lab/real-estate-listing-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 = {
    "listingUrls": ["https://signal-lab-tools.vitaxastar.chatgpt.site/fixtures/real-estate-listing"],
    "emitOnlyChanges": False,
    "proxyConfiguration": { "useApifyProxy": False },
    "maxItems": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("signal_lab/real-estate-listing-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 '{
  "listingUrls": [
    "https://signal-lab-tools.vitaxastar.chatgpt.site/fixtures/real-estate-listing"
  ],
  "emitOnlyChanges": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxItems": 5
}' |
apify call signal_lab/real-estate-listing-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,signal_lab/real-estate-listing-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/63JOpRNWf23GaadvU/builds/BUgKbueVexjqGASVe/openapi.json