Realtor.com Scraper: Every Listing, Sold Prices & Agents avatar

Realtor.com Scraper: Every Listing, Sold Prices & Agents

Pricing

from $0.50 / 1,000 listings

Go to Apify Store
Realtor.com Scraper: Every Listing, Sold Prices & Agents

Realtor.com Scraper: Every Listing, Sold Prices & Agents

Scrape every Realtor.com listing of a city, ZIP or county (for sale, for rent, sold), past the 10,000-result wall and the repeating pages, with agent email and phone. Home details, tax history, schools, new-listing and price-change monitoring.

Pricing

from $0.50 / 1,000 listings

Rating

0.0

(0)

Developer

Alexis Morain

Alexis Morain

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

Realtor.com Scraper: every listing of a city, ZIP code or county, sold prices and agents

Realtor.com Scraper exports the listings that Realtor.com shows for a city, a ZIP code, a county or a neighborhood: homes for sale, homes for rent and sold homes. Each row has the price, the sold price and date, the address and coordinates, beds, baths, living area, lot size, year built, the description, photos, the MLS number and the listing agent with name, email, phone and brokerage.

A Realtor.com search stops serving results at 10,000, and its default order changes from page to page, so a plain read of a big city returns well under half of it. This actor cuts each search into price and date ranges small enough to be read in full, sorted by date, removes the listings found twice and returns one row per home. Every run writes a proof in its SUMMARY record: the count Realtor.com announced next to the count you received.

It works as a Realtor.com API alternative: no login, no browser, plain HTTP. Results land in a dataset you can export as JSON, CSV, Excel or XML, or read through the Apify API from Python, JavaScript or cURL.

How to scrape more than 10,000 Realtor.com listings

The table compares what Realtor.com announced with what this actor read and returned, full coverage on, runs of 18 November 2026 on the Apify platform.

SearchRealtor.com announcesPlain readThis actor readsUnique homes returnedRun timeRun
Houston, TX, for sale17,1557,50117,15517,1103 min 28 soXoYFmnrvA2ARz1uW
Austin, TX, for sale6,3664,6046,3666,1212 min 43 svjIU8tWQUHpmrqb7z
Los Angeles, CA, sold in the last 6 months11,284n/a11,28411,2072 min 41 sWbfzukJgu03mbCR4I
Houston, TX, for rent14,076n/a15,46513,8725 min 26 sn03pz94tea7zti6pu

The plain read is 50 pages of 200 in Realtor.com's default order, the most it serves for one search (measured on 17 November). In that order the same homes come back on several pages, and the read stops at 10,000 anyway.

Why fewer unique homes than announced: Realtor.com counts listings, and the same home can be listed by two MLSs, each with its own listing id. Austin had 245 such homes. The actor returns one row per home (propertyId) and charges it once. For rentals, a listing with a rent range shows up in several price ranges, so the actor reads more rows than announced and keeps one per home.

The SUMMARY record of the Houston for sale run:

{
"monitorMode": "off",
"listingsReturned": 17110,
"byEvent": {"listing": 17110},
"searches": [{
"search": "Houston, TX",
"listingType": "forSale",
"announced": 17155,
"listingsRead": 17155,
"retrieved": 17110,
"subSearches": 9,
"walledSubSearches": 0,
"failedPages": 0,
"complete": true
}],
"requests": 113,
"retried": 4
}

When listingsRead equals announced, nothing was left out. subSearches is the number of ranges the search was cut into. walledSubSearches counts the ranges that still held more than 10,000 listings after every possible cut (one price, one day); it is 0 in every test run so far, and the status message names it when it is not.

Why use a Realtor.com scraper

  • Investors and analysts: every home of a metro area with price, size, year built, sold price and coordinates, for a spreadsheet, a notebook or a price model.
  • Agents, lenders, title and home service companies: lists of listing agents with email, phone and brokerage, by ZIP code or county, and a daily feed of new listings.
  • PropTech and data teams: complete, deduplicated rows with a stable property id, plus tax history, value estimates, schools and flood factor when you need them.
  • Rental watchers: rentals by ZIP code with monthly rent, pet policy and new listings each day.

What you get on top of a plain search export:

  • Full coverage past the 10,000 wall and past the repeating pages, with the announced count against the returned count in every run.
  • Sold prices and dates, in the states that publish them.
  • The listing agent on the search row: name, email, phone numbers and brokerage, no second request.
  • Optional home page data per listing: price and sale history, tax history, value estimates, nearby schools, flood factor, open houses, pet policy, HOA fee.
  • A watch mode that returns only new listings, or new listings plus price changes with the previous price, and a webhook at the end of the run.
  • Proxies included in the price, and Apify scheduling, API access and integrations (Make, Zapier, n8n, Google Sheets).

How to scrape Realtor.com listings, step by step

  1. Open the actor in Apify Console and go to the Input tab.
  2. In Places, type what you would type in Realtor.com's search box: Austin, TX, 78701, Travis County, TX or Hyde Park, Austin, TX. Each place is read separately.
  3. Pick For sale, For rent or Sold, and add filters if you want a subset.
  4. Set Max listings. Use 100 for a first test. 0 means the whole area, tens of thousands of listings for a large city.
  5. Turn on Include home page details if you need the history, tax, estimate and school fields. Leave Full coverage on to get more than 10,000 rows.
  6. Click Start. The status message ends with the announced count against the returned count.
  7. Download the dataset from the Output tab as JSON, CSV or Excel, or read it through the API.

Scrape Realtor.com by city, ZIP code, county or search URL

Places (locations)

City and state, ZIP code, county or neighborhood. Realtor.com resolves the place itself: Travis County, TX announced 9,775 listings for sale, ZIP code 78701 244, the Hyde Park neighborhood of Austin 24 (17 November 2026). A place Realtor.com does not know ends as not found, and the status message names it. A single place that fails does not stop the others.

Realtor.com search URLs (startUrls)

A search page copied from realtor.com, such as https://www.realtor.com/realestateandhomes-search/Austin_TX/beds-3/price-300000-600000 or https://www.realtor.com/apartments/Denver_CO. The actor reads the place, the listing type (for sale, rent or sold) and the filters written in the URL path: price, beds, baths, home type, living area, lot size, year built, new construction and hide pending. A path filter it does not know is named in the log and ignored. Filters you set in the input fields apply on top, for the listing type of the URL.

Filters

FieldWhat it does
minPrice, maxPricePrice for sale and sold, monthly rent for rentals, in USD
minBeds, maxBedsBedrooms
minBathsBathrooms
minSqft, maxSqftLiving area, square feet
minLotSqft, maxLotSqftLot size, square feet
minYearBuilt, maxYearBuiltYear built
homeTypeshouse, condo, townhouse, multiFamily, lot, manufactured, farm
daysOnRealtor1, 7, 14, 30, 90, 6m, 12m, 24m or 36m. For sold homes it is the sale window
newConstructionOnlyNew construction only
hidePendingLeave out homes under contract

Full coverage and home page details

Full coverage is on by default. A search that announces more than 4,000 listings is cut in two by price, then each half again, until every range holds 4,000 or fewer. Ranges are read sorted by date, newest first, so a range read in full gives each listing once. Sold searches are cut by sale date first, then by price. With a small Max listings and no watch, the actor reads the newest listings without cutting.

Include home page details (includeDetails) reads the Realtor.com home page of each listing and adds its fields to the row. The row is charged as a detailed listing instead of a plain one, not on top of it. If a home page cannot be read, the row keeps the search fields, hasDetails is false, and it is charged as a plain listing.

What data does the Realtor.com scraper extract?

Fields that Realtor.com does not show for a given home come back as null, so every row has the same keys.

FieldTypeDescription
propertyIdstringRealtor.com property id (the M number of the listing URL). Use it to deduplicate
listingIdstringId of the current listing of this property
urlstringListing page on Realtor.com
statusstringforSale, forRent, sold or readyToBuild
listPricenumberAsking price in USD, monthly rent for rentals
priceReducedAmountnumberAmount of the last price cut
soldPricenumberSale price for sold homes. Empty in non-disclosure states such as Texas
soldDatestringSale date for sold homes, YYYY-MM-DD
lastSoldDatestringDate of the last recorded sale of the property
lastSoldPricenumberPrice of the last recorded sale. Empty in non-disclosure states
listDatestringDate and time the listing appeared on Realtor.com, UTC
lastUpdateDatestringLast update of the listing, UTC
address, street, city, state, postalCodestringAddress
county, countyFipsstringCounty and its FIPS code
latitude, longitudenumberCoordinates
propertyType, propertySubTypestringsingle_family, condos, townhomes, multi_family, land, mobile, farm, apartment...
beds, baths, bathsFull, bathsHalfnumberBedrooms and bathrooms
sqft, lotSqftnumberLiving area and lot size, square feet
yearBuilt, garage, storiesnumberYear built, garage spaces, stories
descriptionstringListing description written by the agent
isNewListing, isNewConstruction, isPriceReduced, isPending, isComingSoonbooleanRealtor.com flags
primaryPhoto, photosstring, arrayMain photo and all photo URLs
tagsarrayFeature tags (central_air, garage_2_or_more, fenced_yard...)
mlsId, mlsListingIdstringMLS code and the listing number in that MLS
agentName, agentEmail, agentPhones, agentOfficestring, arrayListing agent and brokerage, as the listing shows them
searchLocationstringThe place of the search that returned this row
hasDetailsbooleanTrue when the home page was read (charged as a detailed listing)
previousPrice, priceChangenumber, stringWatch mode: price at the previous run, and new, up or down
scrapedAtstringWhen the run read the search, UTC
propertyHistoryarrayDetails: listing, price change and sale events (date, event, price, source)
taxHistoryarrayDetails: property tax and assessed values per year
estimates, bestEstimatearray, numberDetails: automated value estimates by source, and the one Realtor.com shows first
schoolsarrayDetails: nearby schools with distance, rating, levels, grades and funding
floodFactorScore, floodFactorSeveritynumber, stringDetails: First Street flood factor, 1 to 10, and in words
openHousesarrayDetails: upcoming open houses
petPolicyobjectDetails: cats and dogs allowed (rentals)
hoaFeenumberDetails: monthly HOA fee

How full the agent fields are, measured on 18 November 2026: on Houston for sale, the agent name is on 98 % of the rows, the email on 82 % and a phone on 94 %. On Los Angeles sold homes, 80 % have an email. New construction listings are often published by a builder community without an agent, which is why a city with many new homes (Austin) has fewer emails. On a sample of home pages, tax history and value estimates were on 77 to 78 % of the rows, schools on all of them and the flood factor on 98 %.

Example row

A real row from Austin, for sale, 18 November 2026, with the photo and tag lists shortened:

{
"propertyId": "7764405867",
"listingId": "3003712067",
"url": "https://www.realtor.com/realestateandhomes-detail/9012-Tall-Sky-Trce_Austin_TX_78724_M77644-05867",
"status": "forSale",
"listPrice": 275000,
"lastSoldDate": "2023-04-14",
"listDate": "2026-11-17T23:43:56Z",
"address": "9012 Tall Sky Trce, Austin, TX 78724",
"city": "Austin",
"state": "TX",
"postalCode": "78724",
"county": "Travis",
"latitude": 30.273832,
"longitude": -97.633552,
"propertyType": "single_family",
"beds": 4,
"baths": 3,
"sqft": 2125,
"lotSqft": 11273,
"yearBuilt": 2009,
"garage": 4,
"stories": 2,
"isNewListing": true,
"photos": ["https://ap.rdcpix.com/34d7ede0760b5c22f2fdc6982729a5b4l-m2441438747s.jpg"],
"tags": ["central_air", "garage_2_or_more"],
"mlsId": "ZIPR",
"searchLocation": "Austin, TX",
"hasDetails": true,
"propertyHistory": [
{"date": "2026-11-17", "event": "Listed", "price": 275000, "source": "Zillow"},
{"date": "2023-03-09", "event": "Price Changed", "price": 455000, "source": "UnlockMLS"}
]
}

Realtor.com new listing and price drop tracker

Set Monitor mode to get a feed instead of a full export.

  • New listings only (newOnly) returns the listings that no earlier run with the same input returned.
  • New listings and price changes (newAndPriceChanges) also returns listings whose price moved, with previousPrice and priceChange (up or down). Listings new to the watch get priceChange new.

The first run returns everything. After that, unchanged listings are not pushed and not charged. A watch reads the whole search and compares it with its memory, so nothing is missed when Realtor.com reorders its results.

The memory lives in a named key-value store in your account called realtor-scraper-monitor, one record per search and per watch. Runs that share the same input and the same Monitor name share one memory; change the name to start a second, separate watch on the same search. A listing joins the memory only after it was delivered, so one cut by Max listings or by the maximum charge comes back in the next run. Entries older than 180 days are forgotten.

To schedule it, open Schedules in Apify Console, pick the actor, paste the input and set a cron expression. A daily run at 7:00 with a watch on gives you what changed since yesterday.

Webhook. Set Webhook URL to get a POST at the end of every run. The JSON body carries actor, runId, datasetId, monitorMode, status, searches, failedSearches, listings, listingsWithDetails, priceChanges, skippedAlreadySeen and chargeLimitReached, plus the status message in text (Slack) and content (Discord). A webhook that fails is logged and does not fail the run.

How much does it cost to scrape Realtor.com?

The actor uses Apify's pay-per-event pricing. You pay for events; proxies are included.

EventCharged whenFreeBronzeSilverGold, Platinum, Diamond
ListingA unique listing is returned from a search$1.00 per 1,000$0.87$0.73$0.50
Detailed listingA listing is returned with its home page data. Charged instead of Listing$2.00 per 1,000$1.70$1.50$1.00
Actor startThe run starts, per GB of memory (512 MB by default)$0.002$0.002$0.002$0.002

The plan tier is the one of your Apify subscription. A listing found twice in a run is charged once. A listing skipped by the watch because it was already returned is not charged. A home page that could not be read is charged as a plain listing.

Example: a search that returns 10,000 listings, 1,000 of them with their home page (9,000 Listing events and 1,000 Detailed listing events). That costs $11.00 on Free (9,000 x $0.00100 + 1,000 x $0.00200), $9.53 on Bronze, $8.07 on Silver and $5.50 on Gold, start event not included.

Other examples at the Free rate: Houston, all 17,110 for sale homes, about $17.11; a daily watch on a ZIP code that sees 15 new listings a day, about $0.017 a run. To keep a test cheap, set Max listings or the maximum charge per run in the run options: at the maximum charge the actor stops and keeps the rows it already read.

Scrape Realtor.com with Python, JavaScript or cURL

These examples use the actor alexmorain/realtor-scraper. Replace the token with your own and keep it in an environment variable.

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("alexmorain/realtor-scraper").call(run_input={
"locations": ["Austin, TX", "78701"],
"listingType": "forSale",
"minPrice": 300000,
"maxPrice": 900000,
"minBeds": 3,
"homeTypes": ["house", "townhouse"],
"daysOnRealtor": "30",
"maxItems": 2000,
})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
print(row["address"], row["listPrice"], row["agentEmail"])
summary = client.key_value_store(run["defaultKeyValueStoreId"]).get_record("SUMMARY")["value"]
for entry in summary["searches"]:
print(entry["search"], entry["announced"], entry["retrieved"])

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('alexmorain/realtor-scraper').call({
locations: ['Los Angeles, CA'],
listingType: 'sold',
daysOnRealtor: '90',
maxItems: 0,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, 'sold homes, median price',
items.map((r) => r.soldPrice).filter(Boolean).sort((a, b) => a - b)[Math.floor(items.length / 2)]);

cURL

Start a run and wait for the rows in one call:

curl -X POST \
"https://api.apify.com/v2/acts/alexmorain~realtor-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"locations": ["78701"], "listingType": "forRent", "maxItems": 200}'

A synchronous call times out after five minutes: use it for short runs. For a whole city, start the run with POST /v2/acts/alexmorain~realtor-scraper/runs and read the dataset when it ends.

Limits of this Realtor.com scraper, written plainly

  • United States only. A place outside the US ends as not found.
  • No sold prices in non-disclosure states. Texas, Utah and a dozen other states do not publish sale prices, so soldPrice and lastSoldPrice stay empty there. The sale date is still there.
  • Unique homes are fewer than the announced count. Realtor.com counts a home listed by two MLSs twice; the actor returns it once. Compare listingsRead with announced to check that nothing was left out.
  • Rentals cannot be checked to the unit. A rental with a rent range appears in several price ranges, so listingsRead is above announced and does not prove completeness on its own. Houston returned 13,872 unique rentals for 14,076 announced.
  • Agent contacts are the listing's. Email and phone are what the listing shows. New construction published by a builder community has no agent, and the fields are empty.
  • Not extracted: agent directory pages and agent reviews. They are not part of the listing data this actor reads.
  • Realtor.com can refuse requests. The actor changes IP and retries, and moves to US residential IPs if datacenter IPs are refused from the start. If Realtor.com refuses everywhere, the run ends FAILED with a message instead of returning a half empty dataset.

Realtor.com scraper FAQ

How to scrape more than 10,000 listings from Realtor.com?

A Realtor.com search serves 10,000 results at most, and its default order repeats listings from page to page. To get a whole area, the search has to be cut into smaller ranges, each read in full in a stable order, and the results merged without duplicates. That is what full coverage does. Houston announced 17,155 listings for sale; the actor read all 17,155 and returned 17,110 unique homes (run oXoYFmnrvA2ARz1uW).

Can I scrape Realtor.com by ZIP code?

Yes. Type the ZIP code in Places, for example 78701. You can pass many ZIP codes in the same run, and each one gets its own line in the SUMMARY record.

Can I get sold prices from Realtor.com?

Yes, with Listing type set to Sold, in the states that publish sale prices. daysOnRealtor sets the sale window, from the last day to the last 36 months.

Can I get the listing agent's email and phone?

Yes, on the search row, with no extra charge: agentName, agentEmail, agentPhones and agentOffice.

This is not legal advice. The data this actor reads is what Realtor.com shows to any visitor of its public pages: no login, no private account data. Whether collecting it is allowed depends on what you do with it, where you are and Realtor.com's terms of use, which limit automated access and the reuse of its content. Read them before building a product on the data. The listing data contains personal data: the name, email and phone number of listing agents. In the European Union the GDPR applies to it, and in the US state privacy laws, CAN-SPAM and the rules on unsolicited calls and texts (TCPA) may apply. Do not use agent contacts for mass cold calling or messaging, keep only what you need, and ask a lawyer if the use is commercial and at scale.

Disclaimers and support

Our actors do not extract private user data. They only extract what Realtor.com shows publicly. Your results can still contain personal data, such as the name, email and phone number of a listing agent. Personal data is protected by the GDPR in the European Union and by other regulations around the world. Do not scrape personal data unless you have a legitimate reason, and if you are unsure whether yours is legitimate, consult a lawyer. This actor is not affiliated with or endorsed by Realtor.com or Move, Inc.

Something wrong or missing? Use the Issues tab of this actor. Send the run id and the input. The API tab has the endpoints and ready-made code to start the actor from your own tools.

Guide and use cases

Use cases for outbound and automation, the output fields, pricing and common questions are on the Realtor.com Scraper page of my site. The Classifieds and real estate family page puts it side by side with the other scrapers of the same family.