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. If you only need ZIP market aggregates, use Realtor.com ZIP Market Stats.

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

Input examples

{
  "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 — Get Realtor.com housing-market aggregates by ZIP code without collecting listing cards.
• Realtor.com Property Details — Enrich Realtor.com property IDs or detail URLs with detailed property records.
• Zillow Search — Collect listing cards by ZIP code, location, search URL, or map bounds.
• Zillow Map Results — Collect lightweight map cards with coordinates and Zillow property IDs.
• Zillow Area Statistic — Get ZIP-level statistics calculated from Zillow sale or rental listings.
• Zillow Property Details — Enrich Zillow property IDs or detail URLs with detailed property records.
• 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.