Realtor.com Scraper - Property Data
Pricing
from $0.01 / 1,000 results
Realtor.com Scraper - Property Data
Scrape Realtor.com listings by city, ZIP code, address or landmark: price, beds, baths, the listing agent's name, phone and email, price and tax history, value estimates, neighborhoods and schools.
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
The Howlers
Maintained by CommunityActor stats
0
Bookmarked
39
Total users
0
Monthly active users
19 days ago
Last modified
Categories
Features
Share
Realtor.com Scraper
Scrape Realtor.com listings by city, ZIP code, street address or landmark. Every listing comes back with price, beds, baths, square feet, lot size, home type, year built, status, listing date, description, photos, coordinates and the listing agent's name, phone and email with the brokerage. With listing details on (the default) you also get price history, tax history, home value estimates from Quantarium, Collateral Analytics and Cotality, neighborhoods, nearby schools with ratings, flood and noise scores, the HOA fee and the full feature sheet. Built for agents, investors, lenders and lead generation.
Quick Start
{"zipCode": "78704","listingStatus": "for_sale","maxResults": 50}
{"city": "Austin, TX","priceMin": 400000,"priceMax": 900000,"bedsMin": 3,"propertyTypes": ["single_family"],"listedWithin": 7}
{"address": "606 Josephine St, Austin, TX 78704","searchRadius": 1,"listingStatus": "sold"}
What you get per listing
| Field | What it is |
|---|---|
price, priceType, priceFormatted | The price that applies to the listing: list price (priceType: "list"), sale price ("sold") or rent ("rent"). Unknown stays null, never 0 |
listPrice, soldPrice, priceMin, priceMax, priceReducedAmount | Each price on its own. Apartment communities and new-construction plans give a priceMin to priceMax range. Sold homes in states that do not publish sale prices (Texas, for example) have soldPrice: null and show the last list price |
beds, baths, bathsFull, bathsHalf | Room counts (bedsMin/bedsMax and bathsMin/bathsMax for ranges) |
sqft, lotSqft, propertyType, propertySubType, yearBuilt, garage, stories, hoaFee | Home facts |
status, flags, listingDate, daysOnMarket, lastSoldDate, lastSoldPrice | Listing state (for sale, pending, contingent, sold, for rent) and dates |
agent | Listing agent name, phone, email, office company and companyPhone, and broker |
estimatedValue, estimates | Realtor.com's best home value, and each provider's estimate with its low/high range and date |
priceHistory | {date, price, event, source, pricePerSqft} for every listing and sale event |
taxHistory | {year, tax, assessment, assessedLand, assessedBuilding, marketValue} per year |
neighborhoods, schools, floodFactorScore, femaFloodZone, noiseScore | Neighborhood data |
features, description, photos, coordinates, county | Listing details |
distanceMiles | Address and landmark searches: miles from that point (every row is inside searchRadius) |
addressNormalized | USPS-style address for matching the same home across Realtor.com, Zillow and Redfin |
detailStatus | ok, skipped (details off) or failed |
A run that finds nothing returns one row with resultType: "status", a fetchStatus and a plain message. The OUTPUT record in the key-value store has a run summary.
How it works
The actor reads Realtor.com's public listing data from the same data endpoint Realtor.com's own website calls. One request returns up to 200 homes with the location, radius, status, price, bed, bath, home type and listed-within filters applied by Realtor.com, and one small request per home adds the history, estimates and neighborhood data.
An address or landmark is placed on the map with the US Census geocoder (addresses) or OpenStreetMap (landmarks), and Realtor.com is asked for homes within searchRadius miles of that point. Each row gets distanceMiles, and nothing outside the radius is returned. If the place cannot be found, the run returns a status row and no listing is charged; it never searches a different area instead.
Realtor.com puts its Kasada bot check in front of cloud traffic, so requests go out through Apify residential proxies in the US with a real Chrome browser fingerprint, sticky sessions and short pauses between requests. A session that draws the check is replaced by a fresh residential IP. If the check keeps coming, the run switches to a Camoufox stealth browser that opens Realtor.com and sends the same requests from inside the page. Only public listing data is read; nothing logs in.
Input Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
city | string | - | City and state, for example 'Austin, TX' |
zipCode | string | - | 5-digit ZIP code |
address | string | - | Street address to search around (use with searchRadius) |
landmark | string | - | Landmark, school, university or neighborhood to search around |
searchRadius | integer | 5 | Miles around the address or landmark |
priceMin / priceMax | integer | - | Price range (sale price for sold searches) |
bedsMin / bathsMin | integer | - | Minimum bedrooms and bathrooms |
propertyTypes | array | [] | single_family, condo, townhouse, land, multi_family, mobile, farm |
listingStatus | string | "for_sale" | for_sale, pending, sold or for_rent |
listedWithin | integer | - | Listed (or sold) in the last N days |
maxResults | integer | 50 | Maximum listings (up to 500) |
includeDetails | boolean | true | Price and tax history, estimates, neighborhoods, schools, flood risk, features |
proxyConfiguration | object | Residential, US | Proxy settings (leave as is unless you bring your own proxies) |
webhookUrl | string | - | URL to POST the results to when the run finishes |
Pricing
This actor uses pay-per-event billing. Each event is charged after the row is saved to the dataset, at most once per listing:
| Event | When it is charged | Price |
|---|---|---|
| Actor start | Once when the run starts, one event per GB of memory (minimum one). At the default 2 GB of memory a run starts at $0.20 | $0.10 per GB |
| Listing Scraped | Once per Realtor.com listing returned. Price and tax history, value estimates, schools and flood risk on that listing come with it | $0.02 |
| Agent Extracted | Once per listing whose row names the listing agent together with the agent's own phone or email (agent). A row with no agent, or one that only names a rental feed such as "Zillow" with no agent contact, is not charged | $0.01 |
| Neighborhood Data | Once per listing whose row carries at least one neighborhood (neighborhoods), however many it lists. A row with no neighborhoods is not charged | $0.01 |
| Result | Each item written to the default dataset | $0.00001 |
Status rows and sample rows never trigger a task event. When you set a maximum cost per run, the run stops before any listing whose full cost (its events plus the per-item dataset fee) would go over it, so the cap is never exceeded.
Troubleshooting
A rental has no single price
Apartment communities list a rent range. Those rows have price: null with priceMin and priceMax filled in.
Realtor.com test listings
Realtor.com keeps a few internal test listings, marked with state ZZ or ZIP 00000 (their titles read like "Copy of Ext schema plan"). They are not real homes, so they are dropped and never charged. A real home whose street or plan name contains a word like "Test" or "Copy of" is kept. A search that finds only those returns a status row.
A sold home shows the list price
Some states (Texas, for example) do not publish sale prices. The row keeps the last list price with priceType: "list" and soldPrice: null.
I got a status row
Read its message. Common causes: a city without its state, or filters that exclude every listing.
How do I test for free?
Run with demoMode on. It returns labeled sample listings in the live output format. Every sample item carries demo: true and a _notice field, and sample runs charge no task events.
Built by John Rippy | Actor Arsenal