# Realtor.com Scraper: For Sale, Rent & Sold Listings (`scrapebench/realtor-property-scraper`) Actor

Realtor.com listings by city, ZIP, county or state: for sale, for rent or recently sold, with price, beds, baths, sq ft, agent and office phone and email, MLS number and photos. Paste a search URL or set filters.

- **URL**: https://apify.com/scrapebench/realtor-property-scraper.md
- **Developed by:** [ScrapeBench](https://apify.com/scrapebench) (community)
- **Categories:** Real estate, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.0012 / listing

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Realtor.com Scraper: For Sale, Rent & Sold Listings

### Pain points

- Realtor.com's pages sit behind a bot check (Kasada): on 2026-11-08 a plain request for a search page answered 429 instead of listings.
- A search shows 42 cards a page, so copying a city's listings into a sheet means hundreds of pages and the agent's contact sits one click deeper on each listing.
- Sold prices, rent ranges and agent phones each sit in a different spot on the page, so a hand-built list is never complete.

### What we solve

- Many places in one run, each with the same filters, or paste the realtor.com search URLs you already use.
- For sale, for rent and recently sold, with Realtor.com's own price, beds, baths, square feet and property-type filters.
- Agent and office name, phone and email on the row, not a click away.
- A place Realtor.com does not know, a search with nothing in it, or a search bigger than Realtor.com serves comes back as a free row saying so.

### Summary

Name the places (a city, ZIP, county, neighborhood or state) or paste realtor.com search URLs, pick for sale, for rent or sold, and set the usual filters: price, beds, baths, square feet, property type, listed or sold in the last N days. You get one row per listing as Realtor.com's own search shows it: list price (or the rent range of a building with several units), the sale price and date on sold homes, Realtor.com's estimated value, full address with county, FIPS and coordinates, beds, baths, square feet, lot, year built, garage, HOA fee, the listing remarks and feature tags, flags such as price reduced, pending, foreclosure or new construction, the listing agent and office with phone and email, the MLS and MLS number, open houses, virtual tour and every photo URL.

### Who it's for

- Real estate investors screening new listings, price cuts and foreclosures by ZIP
- Agents and brokers watching competing listings and recent sales in their farm area
- Mortgage, title, insurance and moving companies building lists of active listings and their agents
- Property managers and rental analysts tracking asking rents by building and bedroom count
- Analysts and developers feeding a pricing model or a market dashboard

### How to use

Set the input, run the actor, and collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API). Example input:

```json
{
  "locations": [
    "Austin, TX"
  ],
  "status": "for_sale",
  "minBeds": 3,
  "propertyTypes": [
    "single_family"
  ],
  "maxResults": 100
}
```

See **Inputs** below for every available field.

### What you get

One row per record:

| Field | Description |
|---|---|
| `status` | for_sale, for_rent or sold |
| `list_price` | Asking price or monthly rent (list_price_min / list_price_max: a building's rent range) |
| `last_sold_price` | Sale price on a sold row (last_sold_date beside it); empty in non-disclosure states such as Texas |
| `estimated_value` | Realtor.com's own home value estimate |
| `address` | Street line (unit, city, state, zip_code, county, county_fips, latitude, longitude beside it) |
| `property_type` | single_family, condos, townhomes, multi_family, land, apartment, ... |
| `beds` | Bedrooms (baths, sqft, lot_sqft, year_built, garage, stories beside it) |
| `hoa_fee` | Monthly HOA fee |
| `flags` | new_listing, price_reduced, pending, contingent, foreclosure, new_construction, coming_soon, short_sale |
| `features` | Realtor.com feature tags (central_air, garage_2_or_more, community_swimming_pool, ...) |
| `agent_name` | Listing agent with agent_phone and agent_email |
| `office_name` | Listing brokerage or management company with office_phone and office_email |
| `mls_id` | MLS listing number (mls: the MLS code) |
| `list_date` | Date listed, YYYY-MM-DD |
| `photos` | Every photo URL (primary_photo, photo_count beside it) |
| `search` | The place and status the row was found under |
| `source_url` | The listing's page on realtor.com |

Sample:

```json
{
  "search": "Austin, TX (for_sale)",
  "property_id": "7292599957",
  "listing_id": "3003436130",
  "status": "for_sale",
  "list_price": 255000,
  "last_sold_price": null,
  "last_sold_date": "2014-12-15",
  "list_date": "2026-11-09",
  "address": "910 Duncan Ln Apt 43",
  "unit": "Apt 43",
  "city": "Austin",
  "state": "TX",
  "zip_code": "78705",
  "county": "Travis County",
  "county_fips": "48453",
  "latitude": 30.292571,
  "longitude": -97.724511,
  "property_type": "condos",
  "beds": 2.0,
  "baths": 2.0,
  "sqft": 1007,
  "lot_sqft": 1350,
  "year_built": 1970,
  "garage": 3,
  "flags": [
    "new_listing"
  ],
  "agent_name": "Max Smirnoff",
  "agent_email": "abor@maxsmirnoff.com",
  "office_name": "Uptown Realty Llc",
  "mls": "AUTX",
  "mls_id": "9511241",
  "primary_photo": "http://ap.rdcpix.com/03b6ad87bd1c9502a41a3777c7d06a22l-m3510415523s.jpg",
  "source_url": "https://www.realtor.com/realestateandhomes-detail/910-Duncan-Ln-Apt-43_Austin_TX_78705_M72925-99957"
}
```

### Inputs

| Field | Required | Type | Default | Description |
|---|---|---|---|---|
| `locations` | no | array | `["Austin, TX"]` | Places to search, one per line: a city ('Austin, TX'), a ZIP ('78704'), a county ('Travis County, TX'), a neighborhood ('Hyde Park, Austin, TX') or a 2-letter state ('VT'). Each place is its own search; the filters below apply to every one. |
| `location` | no | string | — | One place; kept alongside 'Locations' for saved tasks. |
| `startUrls` | no | array | — | Optional. Paste search pages from realtor.com, e.g. https://www.realtor.com/realestateandhomes-search/Austin_TX/beds-3/price-300000-500000 or https://www.realtor.com/apartments/Denver_CO. The place, status (sale, rent, recently sold), price, beds, baths, square feet and property type are read from each URL; each URL is its own search and uses its own filters, not the ones below. Anything else in the URL is ignored and named in a free row. |
| `status` | no | string | `"for_sale"` | for_sale: homes on the market (pending and contingent included, marked in flags). for_rent: rentals. sold: recently sold homes (sale prices are empty in non-disclosure states such as Texas). |
| `minPrice` | no | integer | — | List price, monthly rent, or (for sold) the sale price. |
| `maxPrice` | no | integer | — | List price, monthly rent, or (for sold) the sale price. |
| `minBeds` | no | integer | — | Fewest bedrooms. |
| `maxBeds` | no | integer | — | Most bedrooms. |
| `minBaths` | no | integer | — | Fewest bathrooms. |
| `minSqft` | no | integer | — | Smallest living area. |
| `maxSqft` | no | integer | — | Largest living area. |
| `propertyTypes` | no | array | — | Any of: single_family, condos, townhomes, multi_family, duplex_triplex, coop, mobile, land, farm, apartment. Empty = every type. Unknown values are ignored and named in a free row. |
| `listedWithinDays` | no | integer | — | For sale or for rent: only listings added in the last N days. |
| `soldWithinDays` | no | integer | — | Sold: only homes sold in the last N days. |
| `sort` | no | string | `"newest"` | Order of results (decides which ones you get when a search has more than Max results). newest = most recently listed, or most recently sold for sold. |
| `maxResults` | no | integer | `200` | Listings per location or URL. Realtor.com serves at most the first 10,000 of one search; split a bigger area by ZIP or price. |
| `proxyConfiguration` | no | object | `{"useApifyProxy": false}` | Off by default: Realtor.com's search answered Apify's own IPs without one (2026-11-08). |

### Pricing (Pay Per Event)

You pay per result (`listing`) — **no charge for empty runs**. Example: **1000 listings** at *$0.0012/result* ≈ **$1.20**.

$1.20 per 1,000 listings, no start fee. A ZIP's homes for sale are often 100 to 400 listings ($0.12 to $0.48). No charge for empty runs.

### Use cases

- New listings every morning: locations \['78704', '78745'], status for_sale, listedWithinDays 1, scheduled daily.
- Recent sales for comps: location 'Columbus, OH', status sold, soldWithinDays 90, propertyTypes \['single_family'].
- Rent survey: location 'Denver, CO', status for_rent, minBeds 2, then compare list_price_min and list_price_max by building.
- Agent outreach list: a county, status for_sale, and the agent_name, agent_phone and agent_email columns.
- Paste your saved realtor.com search: startUrls with https://www.realtor.com/realestateandhomes-search/Austin_TX/beds-3/price-300000-500000.

### Why this actor

- Reads the same search data Realtor.com's own pages load, with no browser and no proxy, so a 1,000-listing run takes seconds.
- Agent and office phone and email, MLS number, estimated value and every photo on the row.
- Free rows for anything missing, never a silent empty run.

### Limitations & updates

Returns what Realtor.com's search results carry; it does not open each listing's page, so price and tax history, schools, and room-by-room details are not included. A search returns at most the first 10,000 listings Realtor.com serves; split a bigger area by ZIP or price. Sale prices are empty in non-disclosure states. Rentals in a building with several units come back as one row per building with a rent, bed and square-foot range. Listings are as Realtor.com shows them at the moment of the run.

### FAQ

**Which places can I search?**

Anything Realtor.com's own search box takes: a city ('Austin, TX'), a ZIP ('78704'), a county ('Travis County, TX'), a neighborhood ('Hyde Park, Austin, TX'), or a 2-letter state ('VT'). A place it does not recognise comes back as a free row.

**How many listings can one search return?**

Up to 10,000. Realtor.com serves at most the first 10,000 results of a search, so a bigger area (all of Texas for sale, or a large city's sold homes) comes back with a free row saying so; split it into ZIP codes or price ranges, which you can list in one run.

**Why is the sold price empty?**

Some states do not make sale prices public (non-disclosure states such as Texas: 0 of 20 sold homes in a 2026-11-08 Austin 78704 sample had one), so Realtor.com has no sale price for those homes; the sold date and the rest of the row are still there. In disclosure states such as Ohio the sale price is filled (20 of 20 sold homes in a 2026-11-08 Columbus sample).

**Does every listing have the agent's phone and email?**

No, only what Realtor.com shows. In a 2026-11-08 sample of 20 Austin homes for sale, 15 had the agent's phone and 13 the agent's email; rentals managed by a company often list only the office.

**Can I paste a realtor.com search URL?**

Yes. Put it in startUrls: the place, status (sale, rent, recently sold), price, beds, baths, square feet and property type are read from the URL. Anything else in it (sort order, other filters) is ignored and named in a free row.

**How am I charged?**

$0.0012 per listing row, no start fee. Rows that explain something are free. Max results per search caps each location; the run's maximum charge caps the whole run.

### Which actor to choose

Works with:

- **Zillow & Redfin Property Data Scraper** — You have street addresses and want each home's full record: price and tax history, schools, flood zone.

### Guides & use cases

Written up on **[scrapebench.dev](https://scrapebench.dev)** — the bench that runs and verifies this actor against the live source every night:

- **How-to:** [How to run Realtor.com Scraper: For Sale, Rent & Sold Listings](https://scrapebench.dev/guides/how-to-realtor-property-scraper/)
- **Use case:** [A morning feed of new listings for a loan officer's ZIP codes](https://scrapebench.dev/use-cases/new-listings-daily-by-zip/)

More actors, coverage and nightly verification results: **[scrapebench.dev](https://scrapebench.dev)**

### Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the [MCP tab](https://apify.com/scrapebench/realtor-property-scraper/api/mcp) on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

> "Find single-family homes for sale in Austin, TX with at least 3 bedrooms, newest first, with the listing agent's phone and email."

Uses locations \['Austin, TX'], status for_sale, minBeds 3, propertyTypes \['single_family']: 3,772 matches on 2026-11-08, so keep maxResults small for a first call. Runs started this way bill exactly like any other run.

### Data & lawful use

This actor collects publicly available information that Move, Inc., which operates Realtor.com publishes for public
lookup — licence records, business listings and the contact details professionals list there.
Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any
names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the
controller of that data and we act only as your processor (Apify Standard Actor Contract).
You need a lawful basis for your use, must honour opt-out and deletion requests, and must
follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar).
Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or
for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and
don't sell or share them.

### Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by
Move, Inc., which operates Realtor.com. Names and marks are used only to describe the data source. Records are
provided as published by the source and may be out of date or incomplete. For anything
consequential (hiring, a permit, a legal decision), confirm the record with the issuing
agency. You are responsible for making sure your use complies with applicable law and the
source's terms.

### Need help?

Open an issue on this actor's **Issues** tab and we'll respond there. Bug reports, missing
fields and feature requests are all welcome. Guides and examples: [scrapebench.dev](https://scrapebench.dev).

If you are a person named in this data and want your record removed from our copy, email
apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: [Apify Console → Settings → Security → Share run data with developers](https://console.apify.com/settings/security). It lets us see exactly what went wrong and keep improving the actor.

If this actor saved you time, a short review on its Store page helps other buyers find it.

# Actor input Schema

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

Places to search, one per line: a city ('Austin, TX'), a ZIP ('78704'), a county ('Travis County, TX'), a neighborhood ('Hyde Park, Austin, TX') or a 2-letter state ('VT'). Each place is its own search; the filters below apply to every one.

## `location` (type: `string`):

One place; kept alongside 'Locations' for saved tasks.

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

Optional. Paste search pages from realtor.com, e.g. https://www.realtor.com/realestateandhomes-search/Austin_TX/beds-3/price-300000-500000 or https://www.realtor.com/apartments/Denver_CO. The place, status (sale, rent, recently sold), price, beds, baths, square feet and property type are read from each URL; each URL is its own search and uses its own filters, not the ones below. Anything else in the URL is ignored and named in a free row.

## `status` (type: `string`):

for_sale: homes on the market (pending and contingent included, marked in flags). for_rent: rentals. sold: recently sold homes (sale prices are empty in non-disclosure states such as Texas).

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

List price, monthly rent, or (for sold) the sale price.

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

List price, monthly rent, or (for sold) the sale price.

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

Fewest bedrooms.

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

Most bedrooms.

## `minBaths` (type: `integer`):

Fewest bathrooms.

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

Smallest living area.

## `maxSqft` (type: `integer`):

Largest living area.

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

Any of: single_family, condos, townhomes, multi_family, duplex_triplex, coop, mobile, land, farm, apartment. Empty = every type. Unknown values are ignored and named in a free row.

## `listedWithinDays` (type: `integer`):

For sale or for rent: only listings added in the last N days.

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

Sold: only homes sold in the last N days.

## `sort` (type: `string`):

Order of results (decides which ones you get when a search has more than Max results). newest = most recently listed, or most recently sold for sold.

## `maxResults` (type: `integer`):

Listings per location or URL. Realtor.com serves at most the first 10,000 of one search; split a bigger area by ZIP or price.

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

Off by default: Realtor.com's search answered Apify's own IPs without one (2026-11-08).

## Actor input object example

```json
{
  "locations": [
    "Austin, TX"
  ],
  "status": "for_sale",
  "sort": "newest",
  "maxResults": 200,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per Realtor.com listing: price, address, beds, baths, square feet, agent and office contacts, photos. Free notice rows explain anything not returned.

# 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 = {
    "locations": [
        "Austin, TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapebench/realtor-property-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 = { "locations": ["Austin, TX"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapebench/realtor-property-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 '{
  "locations": [
    "Austin, TX"
  ]
}' |
apify call scrapebench/realtor-property-scraper --silent --output-dataset

```

## MCP server setup

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