# Realtor.com Scraper — US Sold Comps, ZIP & Monitor (`crawloop/realtor-com-scraper`) Actor

Scrape Realtor.com sold comps, for-sale, and rental listings by ZIP or city. Get sold price, sold date, beds, sqft, GPS, photos, and agent phone. Monitor new sales. Realtor API alternative for Python, Node.js, and MCP.

- **URL**: https://apify.com/crawloop/realtor-com-scraper.md
- **Developed by:** [Andrej Kiva](https://apify.com/crawloop) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.99 / 1,000 listings

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

## Realtor.com Scraper — US Sold Comps, ZIP & Monitor

> **Disclaimer:** This is an unofficial integration developed independently. It is not affiliated with, sponsored by, or endorsed by Realtor.com, Move, Inc., or News Corp.

> **Realtor.com** and related names are trademarks of their respective owners. Data is read from publicly accessible US listing search. No Realtor.com account login is required.

> This Actor is provided **for informational, research, CMA, lead-generation, and market monitoring purposes**. You are solely responsible for complying with applicable laws (including US state privacy rules), Realtor.com's terms of use, and your organization's policies when processing listing and agent data.

**Realtor.com scraper** for US **sold comps**, **for-sale**, and **for-rent** listings — export sold price, sold date, beds, baths, sqft, $/sqft, ZIP, GPS, photos, and listing-agent phone into JSON/CSV. Use it as a **Realtor.com API alternative** from **Python**, **Node.js**, **cURL**, or **Apify MCP** / AI assistants: paste ZIP codes, a city, or any search / `/realestateandhomes-detail/` URL.

**Best for:** ZIP-farm sold comps (the housing equivalent of completed-sales search), CMA worksheets, new-sale monitors, and US coverage next to the EU/UK/IL portal Actors.

| Actor | Role |
| :--- | :--- |
| Realtor.com Scraper ◄── you are here | US sold comps, ZIP, for-sale & rent |
| [Rightmove Scraper](https://apify.com/crawloop/rightmove-scraper) | UK Rightmove listings (sale & rent) |
| [Idealista Scraper](https://apify.com/crawloop/idealista-scraper) | Spain Idealista listings + agency leads |
| [ImmobilienScout24 Scraper](https://apify.com/crawloop/immobilienscout24-scraper) | Germany IS24 rent & buy |
| [Yad2 Scraper](https://apify.com/crawloop/yad2-scraper) | Israel Yad2 listings |
| [Airbnb Occupancy Scraper](https://apify.com/crawloop/airbnb-occupancy-monitor) | US STR calendars vs long-term comps |

### When to use this Actor

- **Sold comps by ZIP** — Drop `78704`, `90210`, or a farm list. Default status is **sold**, sorted by sold date, last 30 days.
- **CMA windows past six months** — Set **Sold within (days)** to 90, 180, or 365. Public search commonly returns 12+ months of closed sales.
- **For-sale or rental pull** — Switch listing status, or paste a search URL with type / beds / price already in the path.
- **Scheduled monitoring** — Re-run the same ZIPs and emit only **new** or **status/price-changed** rows (new sold this week).
- **One listing** — Paste a `/realestateandhomes-detail/` URL to fetch that property.

### When not to use this Actor

- **Nationwide agent directories, building permits, or email enrichment** — This version is listing comps, not an agent CRM dump.
- **Zillow / Redfin** — Separate portals; this Actor reads Realtor.com only.
- **Authenticated MLS feeds** — No login, saved searches, or contact-unlock walls.

### Key features

- **HTTP GraphQL** — Same search backend the site uses. No headless browser, 128–512 MB RAM.
- **ZIP-first builder** — `zipCodes[]` is the primary input; cities and Start URLs are optional.
- **Sold recency you control** — 1–730 days via `sold_date`, default 30, sort `sold_date` desc.
- **Search + detail URLs** — Path filters (`show-recently-sold`, `type-single-family-home`, `beds-3`, `price-min-max`) are kept.
- **Price-band split** — Automatic when a query hits the ~10,000-result GraphQL window.
- **Monitor mode** — Key-value store remembers property IDs plus status/price across runs.
- **Residential US proxy** — Recommended on Apify Cloud so datacenter IPs are not blocked.

### Input

| Field | What it does |
| :--- | :--- |
| **ZIP codes** | Primary builder. One search per ZIP with the filters below. |
| **Cities / neighborhoods** | `Austin, TX` style fallback when you do not have ZIPs. |
| **Start URLs** | Search (`/realestateandhomes-search/`, `/apartments/`) or listing (`/realestateandhomes-detail/`) links. |
| **Listing status** | `sold` (default), `for_sale`, or `for_rent`. Builder only. |
| **Sold within (days)** | Recency window for sold searches (1–730). Default 30. |
| **Property types / price / beds / sqft** | Optional filters. Price is list price, or close price when status is sold. |
| **Max listings** | Cap per run across all ZIPs and URLs. |
| **Scrape full details** | Off by default. Adds description, tax parcel, extra photos, and price history. |
| **Monitor mode** | Save only new or changed properties on scheduled re-runs. |

```json
{
  "zipCodes": ["78704"],
  "listingStatus": "sold",
  "soldWithinDays": 30,
  "maxItems": 50,
  "includeDetails": false,
  "monitorMode": false
}
```

### Output

One dataset row per property.

| Field | Meaning |
| :--- | :--- |
| `id` / `propertyId` / `listingId` | Realtor.com identifiers |
| `url` | Canonical listing URL |
| `status` | `sold`, `for_sale`, or `for_rent` |
| `soldPrice` / `soldDate` | Close price and date when sold |
| `listPrice` / `listDate` / `originalListPrice` | List side; original from history when details are on |
| `daysOnMarket` / `pricePerSqft` | Calendar DOM and $/sqft |
| `beds` / `baths` / `sqft` / `lotSqft` / `yearBuilt` | Size and vintage |
| `address` / `zip` / `city` / `state` / `latitude` / `longitude` | Location |
| `mls` / `mlsId` | MLS board and listing id |
| `agentName` / `agentPhone` / `officeName` | Listing agent as shown publicly |
| `photos` | Image URLs |
| `description` / `propertyHistory` | Present when details are enabled |
| `scrapedAt` | UTC timestamp |

```json
{
  "id": "8208702628",
  "url": "https://www.realtor.com/realestateandhomes-detail/1900-Barton-Springs-Rd-Unit-5015_Austin_TX_78704_M82087-02628",
  "status": "sold",
  "soldPrice": 325000,
  "soldDate": "2026-08-21",
  "listPrice": 325000,
  "listDate": "2026-05-01",
  "daysOnMarket": 112,
  "pricePerSqft": 467,
  "propertyType": "condos",
  "beds": 0,
  "baths": 1,
  "sqft": 696,
  "zip": "78704",
  "city": "Austin",
  "state": "TX",
  "agentName": "Gabriel Recio",
  "agentPhone": "(210) 563-1557",
  "officeName": "Redfin Corporation"
}
```

### Use cases

- **ZIP CMA** — Pull 30- or 90-day solds for a farm, then chart $/sqft by beds.
- **New-sale alerts** — Schedule daily with monitor mode; only newly closed rows land in the dataset.
- **Investor screens** — For-sale list in the same ZIP next to recent solds for spread vs comps.
- **US vs EU pipeline** — Same field style as Rightmove / Idealista / ImmobilienScout24 for a multi-country warehouse.

### Integration examples

Replace `YOUR_TOKEN` with your Apify API token. Actor name: `crawloop/realtor-com-scraper`.

#### Node.js

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('crawloop/realtor-com-scraper').call({
  zipCodes: ['78704'],
  listingStatus: 'sold',
  soldWithinDays: 30,
  maxItems: 25,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.slice(0, 5));
```

#### Python

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("crawloop/realtor-com-scraper").call(
    run_input={
        "zipCodes": ["78704"],
        "listingStatus": "sold",
        "soldWithinDays": 30,
        "maxItems": 25,
    }
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items[:5])
```

#### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/crawloop~realtor-com-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "zipCodes": ["78704"],
    "listingStatus": "sold",
    "soldWithinDays": 30,
    "maxItems": 25
  }'
```

### MCP and AI assistants

Use this Actor from AI tools via [Apify MCP](https://docs.apify.com/platform/integrations/mcp).
Connect your Apify account, then call this Actor by its Store ID / name (`crawloop/realtor-com-scraper`).

Example prompts:

- "Run Realtor.com Scraper for ZIP 78704 sold last 30 days, max 20, and return address, soldPrice, soldDate, sqft as JSON"
- "Scrape Realtor.com 90210 for-sale listings and summarize median list price vs beds"
- "Pull Austin sold comps with Realtor.com Scraper, then compare the field set with Rightmove Scraper for a US vs UK pipeline"

### Suite next step

After US sold comps, add short-term rental occupancy with [Airbnb Occupancy Scraper](https://apify.com/crawloop/airbnb-occupancy-monitor), or UK sale/rent coverage with [Rightmove Scraper](https://apify.com/crawloop/rightmove-scraper).

### FAQ

**Is this an official Realtor.com API?**\
No. It is an unofficial **Realtor.com scraper** / API alternative that reads the public listing search GraphQL. It is not affiliated with Move, Inc. You can call it from **Python**, **Node.js**, **cURL**, or **MCP**.

**How do I scrape Realtor.com sold listings by ZIP with Python or Node.js?**\
Pass `zipCodes` plus `listingStatus: "sold"` (the default). Use the snippets above. Add `soldWithinDays` for the CMA window and `monitorMode` on a schedule for new closed sales.

**How far back do sold comps go?**\
Public search accepted a 365- and 730-day `sold_date` window in testing. Coverage still depends on what the portal exposes for that ZIP — it is not a full MLS history.

**Why is last\_sold\_price empty on some rows?**\
Many sold cards only populate `listPrice`. This Actor sets `soldPrice` from `last_sold_price` when present, otherwise from the displayed list/close price on sold status.

**Do I need a proxy?**\
On Apify Cloud, **US RESIDENTIAL** is the supported setup. HTML search pages often return 429 from datacenter IPs; GraphQL with residential US is the path this Actor uses.

### Related Actors

| Actor | Role |
| :--- | :--- |
| [Rightmove Scraper](https://apify.com/crawloop/rightmove-scraper) | UK sale and rent listings |
| [Idealista Scraper](https://apify.com/crawloop/idealista-scraper) | Spain sale/rent listings + agency phones |
| [ImmobilienScout24 Scraper](https://apify.com/crawloop/immobilienscout24-scraper) | Germany rent and buy |
| [Yad2 Scraper](https://apify.com/crawloop/yad2-scraper) | Israel classifieds |
| [Airbnb Occupancy Scraper](https://apify.com/crawloop/airbnb-occupancy-monitor) | US STR occupancy calendars |

# Actor input Schema

## `zipCodes` (type: `array`):

US ZIP codes to scrape (primary builder). Each ZIP is a separate sold/sale/rent search with the filters below. Example: 78704, 90210.

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

Fallback when you do not have ZIPs. Examples: Austin, TX or Zilker, Austin, TX.

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

Paste Realtor.com search URLs or /realestateandhomes-detail/ links. Path filters (solds, type, beds, price) are applied automatically.

## `listingStatus` (type: `string`):

Builder only (ignored when the Start URL already encodes sold/sale/rent). Default is sold comps.

## `soldWithinDays` (type: `integer`):

Keep sold listings with last\_sold\_date in the last N days (1–730). Applies to sold searches. Default 30. Public search commonly returns 12+ months — unlike 6-month-only scrapers.

## `propertyTypes` (type: `array`):

Optional. Leave empty for all types.

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

Minimum list price, or sold/close price when status is sold.

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

Maximum list price, or sold/close price when status is sold.

## `minBeds` (type: `integer`):

Minimum bedroom count. Studios are 0.

## `maxBeds` (type: `integer`):

Maximum bedroom count.

## `minSqft` (type: `integer`):

Minimum interior square footage.

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

Maximum number of listings to save per run (across all ZIPs/URLs).

## `includeDetails` (type: `boolean`):

Fetch each home's description, tax parcel, extra photos, and price history. Off by default — search cards already include sold price, date, beds, sqft, GPS, and agent phone.

## `monitorMode` (type: `boolean`):

On scheduled re-runs, save only properties that are new or whose status/price changed since the last run on this Actor. Use for 'new sold this week' comps.

## `maxConcurrency` (type: `integer`):

How many property-detail requests to run in parallel when details are on. Default 8.

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

Apify Proxy. US RESIDENTIAL is recommended for stable access to Realtor.com on Apify Cloud.

## Actor input object example

```json
{
  "zipCodes": [
    "78704"
  ],
  "listingStatus": "sold",
  "soldWithinDays": 30,
  "maxItems": 10,
  "includeDetails": false,
  "monitorMode": false,
  "maxConcurrency": 8,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

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

Default dataset items — one Realtor.com listing per row.

# 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 = {
    "zipCodes": [
        "78704"
    ],
    "soldWithinDays": 30,
    "maxItems": 10,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "US"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawloop/realtor-com-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 = {
    "zipCodes": ["78704"],
    "soldWithinDays": 30,
    "maxItems": 10,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "US",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("crawloop/realtor-com-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 '{
  "zipCodes": [
    "78704"
  ],
  "soldWithinDays": 30,
  "maxItems": 10,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}' |
apify call crawloop/realtor-com-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawloop/realtor-com-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/63qof3Fob5HR4ddXh/builds/xgsWODxDHVbDeOLIN/openapi.json