# Zillow/Realtor Listing Change Monitor (`isotonic/zillow-realtor-listing-change-monitor`) Actor

Monitors public Zillow and Realtor listing pages for visible changes without login, private APIs, or bypass techniques.

- **URL**: https://apify.com/isotonic/zillow-realtor-listing-change-monitor.md
- **Developed by:** [Brian Keefe](https://apify.com/isotonic) (community)
- **Categories:** Real estate, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

## Zillow/Realtor Listing Change Monitor

Production-ready Apify Actor for monitoring visible changes on low-volume, public Zillow and Realtor pages.

### What It Does

- Accepts public listing URLs and public agent/profile URLs.
- Auto-detects Zillow vs. Realtor, or respects a forced `sourceType`.
- Extracts visible listing details such as address/title, price, status, beds, baths, and square footage.
- Optionally includes public agent/profile/contact links already visible on the page.
- Compares current results against `previousSnapshot` and emits change fields plus previous/current values.
- Returns warning rows for blocked, login-required, or captcha pages.
- Supports `fixture://` URLs for deterministic local testing.

### Public-Data-Only Limitations

- Public URLs only.
- No login.
- No MLS or private APIs.
- No anti-bot bypass.
- No broad search scraping.
- No stealth, captcha solving, proxy escalation, or hidden endpoint access.

If Zillow or Realtor returns a blocked or login wall page, the actor records a warning row and stops there for that URL.

### Input

```json
{
  "urls": [
    "https://www.zillow.com/homedetails/...",
    "https://www.realtor.com/realestateagents/...",
    "fixture://zillow-listing"
  ],
  "sourceType": "auto",
  "previousSnapshot": [],
  "maxPages": 10,
  "includeAgentInfo": true
}
```

### Output

Each dataset item is either a `listing` row or a `warning` row.

Example listing fields:

```json
{
  "rowType": "listing",
  "source": "zillow",
  "url": "fixture://zillow-listing",
  "visibleAddress": "123 Main St, Austin, TX, 78701",
  "visibleTitle": "Single family residence",
  "price": 765000,
  "status": "For sale",
  "beds": 3,
  "baths": 2,
  "sqft": 1840,
  "agentName": "Jamie Stone",
  "agentProfileUrl": "fixture://zillow-agent",
  "contactLinks": [
    "tel:+15125550199",
    "mailto:jamie@example.com"
  ],
  "evidence": {
    "priceText": "$765,000",
    "statusText": "For sale"
  },
  "snapshotTimestamp": "2026-07-05T00:00:00.000Z",
  "changed": true,
  "changeFields": ["price"],
  "previousPrice": 749000,
  "currentPrice": 765000,
  "previousStatus": "For sale",
  "currentStatus": "For sale"
}
```

### Fixture URLs

Local deterministic fixtures included for smoke tests:

- `fixture://zillow-listing`
- `fixture://realtor-listing`
- `fixture://realtor-agent`
- `fixture://blocked-page`

### Development

Install and test:

```bash
npm install
npm test
```

Run locally:

```bash
npm start
```

### Notes On Parsing

- Uses JSON-LD first when available.
- Falls back to common visible page selectors and text heuristics.
- Normalizes price, beds, baths, and sqft to numbers when possible.
- Matches previous rows by `url`, `visibleAddress`, and `visibleTitle`.

### Files

- Actor metadata: `.actor/actor.json`
- Input schema: `.actor/input_schema.json`
- Main entrypoint: `src/main.js`
- Fixtures: `fixtures/*.html`
- Smoke tests: `tests/smoke.test.js`

# Actor input Schema

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

Public Zillow/Realtor listing URLs or agent/profile URLs. Fixture URLs like fixture://zillow-listing are supported for tests.

## `sourceType` (type: `string`):

Auto-detect, or force Zillow/Realtor parsing heuristics.

## `previousSnapshot` (type: `array`):

Optional prior output rows used to compute deltas.

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

Maximum number of input or discovered listing pages to process.

## `includeAgentInfo` (type: `boolean`):

Include visible agent names and public contact/profile links when available.

## Actor input object example

```json
{
  "urls": [
    "fixture://zillow-listing",
    "fixture://realtor-listing"
  ],
  "sourceType": "auto",
  "previousSnapshot": [],
  "maxPages": 10,
  "includeAgentInfo": true
}
```

# 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 = {
    "urls": [
        "fixture://zillow-listing",
        "fixture://realtor-listing"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("isotonic/zillow-realtor-listing-change-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 = { "urls": [
        "fixture://zillow-listing",
        "fixture://realtor-listing",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("isotonic/zillow-realtor-listing-change-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 '{
  "urls": [
    "fixture://zillow-listing",
    "fixture://realtor-listing"
  ]
}' |
apify call isotonic/zillow-realtor-listing-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,isotonic/zillow-realtor-listing-change-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/YwVHf7jVSxHOPByBa/builds/8nCCndy2vvbnacx6l/openapi.json