# Realtor.com Scraper (US) — Listings + Agent Emails (`yugenox/realtor-com-scraper`) Actor

Scrape US real-estate listings from Realtor.com by city, state, or ZIP — price, beds/baths, size, address, status, photos, MLS info, AND the listing agent's name, email, phone, and brokerage. US only (Realtor.com); for Canada use our Realtor.ca scrapers.

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

## Pricing

from $1.00 / 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.

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 — US Listings, Agent Emails & Sold Prices

Pull **for-sale, for-rent and recently-sold listings from [Realtor.com](https://www.realtor.com)**
for any US city, state or ZIP. Price, beds, baths, square footage, lot size, coordinates, photos,
MLS® name, price-reduction history, open houses — **and the listing agent with their email address**.

> 🇺🇸 **United States.** For Canada see the **Realtor.ca Property Scraper** and
> **Realtor.ca Agent Scraper**.

***

### Why this scraper

- **Agent emails.** Most listing scrapers give you a property and a brokerage phone. This returns the
  advertiser records behind the listing — agent name, **email**, website, office and brokerage phone.
- **Sold listings, with prices.** `status: "sold"` gives you recent comparables, plus `lastSoldPrice`
  and `lastSoldDate` on active listings. That's the data most portals hide.
- **Price-drop signal.** `priceReducedAmount` tells you which listings are moving, without diffing
  snapshots yourself.
- **No API key and no MLS® licence.**

***

### Input

| Field | Type | Required | Default | Description |
|---|---|:--:|---|---|
| `locations` | array of strings | ✅ | | `"City, ST"`, a city name, or a ZIP code. |
| `limitPerLocation` | integer | | | Max listings per location. |
| `status` | string | | `sale` | `sale`, `rent` or `sold`. |

```json
{
  "locations": ["Austin, TX", "78701", "Nashville, TN"],
  "limitPerLocation": 200,
  "status": "sale"
}
```

***

### Output

One row per listing.

#### Property

| Field | Type | Description |
|---|---|---|
| `listPrice` | number | Asking price. |
| `beds` | number | Bedrooms. |
| `baths` | string | Bathrooms, e.g. `"2.5"`. |
| `sqft` | number | Interior square footage. |
| `lotSqft` | number | Lot size in square feet. |
| `propertyType` | string | e.g. `single_family`, `condo`, `townhouse`. |
| `address` / `city` / `stateCode` / `postalCode` | string | Location fields. |
| `latitude` / `longitude` | number | Coordinates. |
| `status` | string | e.g. `for_sale`, `for_rent`, `sold`. |
| `listDate` | string | ISO listing date. |
| `priceReducedAmount` | number | Size of the most recent price cut. |
| `lastSoldPrice` / `lastSoldDate` | number / string | Previous sale, when published. |
| `photoCount` / `primaryPhoto` | number / string | Photo count and lead image. |
| `mlsName` | string | Originating MLS®, e.g. `ACTRIS`. |
| `flags` | object | Status flags such as `isPending`, `isNewListing`, `isForeclosure`. |
| `url` | string | Realtor.com listing page. |
| `openHouses` | array | Scheduled open houses, when listed. |

#### Agent

| Field | Type | Description |
|---|---|---|
| `agentName` | string | Listing agent. |
| `agentEmail` | string | Agent email, where published. |
| `agentWebsite` | string | Agent's own site. |
| `brokerage` | string | Brokerage name. |
| `brokeragePhone` | string | Office phone. |
| `advertisers` | array | Every agent on the listing, each with email and office. |
| `mlsAgents` | array | MLS® agent identifiers. |

```json
{
  "listPrice": 450000,
  "beds": 4,
  "baths": "2.5",
  "sqft": 2150,
  "lotSqft": 6500,
  "propertyType": "single_family",
  "address": "123 Main St",
  "city": "Austin",
  "stateCode": "TX",
  "postalCode": "78701",
  "latitude": 30.29,
  "longitude": -97.75,
  "status": "for_sale",
  "listDate": "2026-06-15T00:00:00Z",
  "priceReducedAmount": 10000,
  "lastSoldPrice": 380000,
  "lastSoldDate": "2022-04-01",
  "mlsName": "ACTRIS",
  "photoCount": 42,
  "primaryPhoto": "https://ap.rdcpix.com/....jpg",
  "agentName": "Jane Doe",
  "agentEmail": "jane@kw.com",
  "agentWebsite": "http://janedoe.com",
  "brokerage": "Keller Williams Realty",
  "brokeragePhone": "(512) 555-0100",
  "flags": { "isPending": false, "isNewListing": true },
  "url": "https://www.realtor.com/realestateandhomes-detail/..."
}
```

*Values above are illustrative.*

***

### What people use it for

**Comparables and valuation.** Run `status: "sold"` across a ZIP to build a comp set with price,
square footage and sale date — the inputs an AVM or a listing presentation needs.

**Investor deal flow.** Sort on `priceReducedAmount` and `listDate` to surface motivated sellers, and
use `flags.isForeclosure` and `isPending` to filter out what's already gone.

**Agent lead lists.** `advertisers` carries agent email and office per listing, so a run over a metro
gives you the active agents in that market — with contact details — ranked by how much they list.

**Portals and market dashboards.** Coordinates, photos and MLS® name on every row, refreshed on a
schedule, behind a map or an internal inventory tracker.

***

### Scale and cost

- Listings paginate efficiently; a few hundred per location is routine.
- Pass several ZIPs or cities rather than one very large metro for the best coverage.
- Cost is Apify compute only — no per-request fee.

Start with `limitPerLocation: 10` to inspect the shape of the data, then scale.

***

### FAQ

**Are agent emails really included?**
Where Realtor.com publishes them on the listing's advertiser record, yes — that's the main reason to
use this over a plain listing scraper. They aren't present on every listing.

**Can I get sold prices?**
Yes. Set `status` to `sold`, and active listings also carry `lastSoldPrice` / `lastSoldDate` when
published.

**Can I search by ZIP?**
Yes — `locations` accepts `"City, ST"`, a bare city, or a ZIP code, and you can mix them in one run.

**Do I need an MLS® feed or licence?**
No. This reads only publicly visible Realtor.com pages.

**Is rental data supported?**
Yes, via `status: "rent"`.

**How fresh is it?**
Read live at run time. Schedule the actor to keep a feed current.

**Do you cover Canada?**
Not here — Realtor.com is US only. Use the **Realtor.ca Property Scraper** for Canadian listings and
the **Realtor.ca Agent Scraper** for Canadian agents.

***

**Is it legal to scrape Realtor.com?**
This Actor only collects publicly available data: for-sale, for-rent and sold listings that anyone can view on Realtor.com without an account. Collecting publicly available data is generally legal, but you're responsible for how you use it. Results can include listing agents' names and business contact details, and that counts as personal data. You must follow privacy laws such as GDPR, PIPEDA and CCPA, as well as Realtor.com's terms. If you're unsure, check with a lawyer. More on this: [Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/)

**Does it access any private data?**
No. Everything comes from pages Realtor.com shows to any visitor without logging in. It never uses a login, never touches private or restricted accounts, and never reaches password-protected areas.

### Notes

- MLS®, Multiple Listing Service® and REALTOR® are trademarks of the National Association of
  REALTORS®. This actor is not affiliated with or endorsed by NAR or Realtor.com.
- Only publicly visible listing information is collected.

# Actor input Schema

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

US locations to search. Use "City, ST" (e.g. "Austin, TX"), a city name, or a ZIP code (e.g. "90210").

## `limitPerLocation` (type: `integer`):

Cap listings collected per location.

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

Which listings to pull.

## Actor input object example

```json
{
  "locations": [
    "Austin, TX",
    "Miami, FL",
    "90210"
  ],
  "limitPerLocation": 200,
  "status": "sale"
}
```

# 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"
    ],
    "limitPerLocation": 200
};

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

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

```

## MCP server setup

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