# Realtor.com Listings by ZIP (`alol/realtor-search`) Actor

Collect Realtor.com listings across up to 100 ZIPs with automatic pagination, deduplication, and separate ZIP market statistics. Choose your own listing limit and see explicit truncation reasons.

- **URL**: https://apify.com/alol/realtor-search.md
- **Developed by:** [Al Ol](https://apify.com/alol) (community)
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.85 / 1,000 search listings — usd 1.70 to usd 0.85 per 1,000s

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?

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 Listings Scraper by ZIP Code

**Scrape Realtor.com real estate listings by ZIP code, including homes for sale, rentals, and sold properties.** Collect normalized listing cards and separate ZIP market statistics in the same run. Search up to 100 ZIP codes, with automatic pagination and property deduplication across ZIPs.

Successfully fetched listing pages and ZIP metrics are returned even if a later listing page fails. The run still reports the upstream failure, and returned listing quality records the shortened collection.

- **Control the listing volume:** choose a global `maxResults` limit of at least 20, with no fixed upper bound in the input schema. The default is 20; upstream availability, run time, and budgets still limit collection.
- **Keep market context distinct:** each input ZIP gets a separate statistics row, with source market counts clearly separated from search-result totals.
- **Prepare data for downstream use:** normalized listings include available sale dates and lot size, caller-supplied correlation IDs, and explicit truncation reasons.

Search current Realtor.com listing cards by one or more five-digit US ZIP codes. The Actor returns normalized listing rows and one separate ZIP market-statistics row per input ZIP. Market metrics are never copied into listing rows, and `searchTotal` remains distinct from the market-wide `listing_count` metric.

For detailed property records, pass the returned property IDs or detail URLs to [Realtor.com Property Details](https://apify.com/alol/realtor-property-details). If you only need ZIP market aggregates, use [Realtor.com ZIP Market Stats](https://apify.com/alol/realtor-zip-statistics).

This is a strict ZIP-only product. Unsupported and unknown fields are rejected instead of being ignored.

### Input examples

```json
{
  "zipCodes": ["08109", "00501"],
  "listingTypes": ["forSale"],
  "maxResults": 100,
  "externalId": "market-scan-42"
}
```

### Pricing

The effective result price depends on the customer's Apify account tier. Platform usage is included.

There is no fixed start charge. Each published listing and each complete six-metric ZIP-statistics row is billed separately. Unavailable and not-found statistics rows are free.

Paid output is reserved before the Dataset write and charged only after successful publication. Max Cost in the platform run options and `maxTotalChargeUsd` both limit collection; the lower limit applies. Page sizes are bounded by the number of affordable listings. A later ZIP is skipped when neither a listing nor its statistics can be funded. Saved rows and their charges are retained.

#### `search-result`

| Apify tier | Per result | Per 1,000 results |
| --- | ---: | ---: |
| FREE | `$0.00170` | `$1.70` |
| BRONZE | `$0.00145` | `$1.45` |
| SILVER | `$0.00115` | `$1.15` |
| GOLD | `$0.00085` | `$0.85` |

#### `zip-statistics`

| Apify tier | Per result | Per 1,000 results |
| --- | ---: | ---: |
| FREE | `$0.00095` | `$0.95` |
| BRONZE | `$0.00095` | `$0.95` |
| SILVER | `$0.00090` | `$0.90` |
| GOLD | `$0.00085` | `$0.85` |

### FAQ and troubleshooting

#### How do I scrape Realtor.com listings by ZIP code?

Enter one to 100 five-digit strings in `zipCodes`, choose `forSale`, `forRent`, or `sold` in `listingTypes`, and set the global `maxResults` limit. Listing rows and ZIP market-statistics rows remain separate. City names, county names, and search URLs are not accepted by this Actor.

**Why is `searchTotal` different from `listing_count`?** `searchTotal` is the total for the selected listing categories. `listing_count` is a separate ZIP market aggregate supplied by Realtor.com.

**Why is a ZIP statistics row unavailable or not found?** Realtor.com may return a recognized ZIP without a housing-market aggregate, or no geographic container at all. The Actor preserves that distinction and does not estimate missing metrics.

**Why are fewer listings emitted than expected?** Check `quality.truncated` and `quality.reasons`, plus `maxResults`, charge budget, upstream total, and cross-ZIP deduplication.

**Does this Actor use a proxy or browser fallback?** Yes. Requests use a fixed operator-managed chain: primary residential proxy, premium residential proxy, then Bright Data Scraping Browser. Each proxy tier exhausts bounded fresh-session retries before fallback. The Actor fails closed if the chain is not configured and never uses Apify Residential or a direct connection. The endpoint is an internal GraphQL contract and can change without notice; deterministic contract errors fail immediately rather than wasting fallback requests.

### Related Actors

Explore our other real-estate Actors for property discovery, enrichment, market analysis, and monitoring:

- [Realtor.com ZIP Market Stats](https://apify.com/alol/realtor-zip-statistics) — Get Realtor.com housing-market aggregates by ZIP code without collecting listing cards.
- [Realtor.com Property Details](https://apify.com/alol/realtor-property-details) — Enrich Realtor.com property IDs or detail URLs with detailed property records.
- [Zillow Search](https://apify.com/alol/zillow-search) — Collect listing cards by ZIP code, location, search URL, or map bounds.
- [Zillow Map Results](https://apify.com/alol/zillow-map-results) — Collect lightweight map cards with coordinates and Zillow property IDs.
- [Zillow Area Statistic](https://apify.com/alol/zillow-area-statistic) — Get ZIP-level statistics calculated from Zillow sale or rental listings.
- [Zillow Property Details](https://apify.com/alol/zillow-property-details) — Enrich Zillow property IDs or detail URLs with detailed property records.
- [Zillow Listing Monitor](https://apify.com/alol/zillow-listing-monitor) — Track new listings, price changes, status changes, and confirmed delistings across repeated scans.

### Responsible use and data availability

This independent Actor is not affiliated with or endorsed by Realtor.com. It does not grant rights to Realtor.com, broker, MLS, photographic, personal, or other third-party data.

Source availability and field coverage vary by ZIP, listing type, time, and upstream response. Customers are responsible for lawful use, compliance with applicable terms, copyright, database, privacy, fair-housing, marketing, and other rules, and for obtaining any required permissions. Do not use missing or delayed data as proof that a property or listing does not exist.

# Actor input Schema

## `externalId` (type: `string`):

Optional caller-owned run ID copied to every Realtor.com output row.

## `correlationId` (type: `string`):

Optional trace or workflow ID copied to every Realtor.com output row.

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

One to 100 five-digit US ZIP codes. Leading zeroes are preserved.

## `listingTypes` (type: `array`):

Realtor.com listing categories to include in the ZIP search.

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

Global cap on paid listing rows across all ZIP codes. Paid runs require at least 20 requested results; ZIP statistics are separate.

## `maxTotalChargeUsd` (type: `number`):

Hard limit for Realtor.com pay-per-event charges in this run. Paid rows are not written after the limit is reached.

## `maxUpstreamAttempts` (type: `integer`):

Optional run-level ceiling for Realtor.com GraphQL request attempts. The deployment limit can only reduce this value.

## `maxUpstreamCostUsd` (type: `number`):

Optional best-effort ceiling for measured Realtor.com GraphQL request cost. The final request may cause a small overshoot.

## Actor input object example

```json
{
  "zipCodes": [
    "10314"
  ],
  "listingTypes": [
    "forSale"
  ],
  "maxResults": 20
}
```

# Actor output Schema

## `results` (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 = {
    "zipCodes": [
        "10314"
    ],
    "listingTypes": [
        "forSale"
    ],
    "maxResults": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("alol/realtor-search").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": ["10314"],
    "listingTypes": ["forSale"],
    "maxResults": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("alol/realtor-search").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": [
    "10314"
  ],
  "listingTypes": [
    "forSale"
  ],
  "maxResults": 20
}' |
apify call alol/realtor-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alol/realtor-search"
        }
    }
}
```

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/zaaZ5UKgpfv41CqXq/builds/FYVQlgeZtZaEzNjnG/openapi.json