Realtor Property Details Cheap (Pay Per Result)
Pricing
from $1.00 / 1,000 results
Realtor Property Details Cheap (Pay Per Result)
Realtor.com property details scraper that extracts price, beds, baths, sqft, tax history, and school ratings from any US address or property ID, so investors and agents can pull structured listing data at scale.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
Kawsar
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Realtor Property Details Scraper

Pull full property details from Realtor.com for any US address or numeric property ID. The actor resolves plain-text addresses automatically, calls the Realtor.com API, and returns structured data: listing price, beds, baths, square footage, year built, status, tax history, school ratings, estimated value, photos, and more. No API key, no browser, no manual lookups.
Each result is stored as a flat, table-ready record with 17 individual columns plus the full raw JSON object. Works for active listings, off-market homes, and recently sold properties.
The most affordable Realtor.com property data scraper on Apify. Pay only for what you use — no subscriptions, no minimums, no wasted credits.
What data does this actor extract?
Every property comes back as a flat row with key fields broken out as separate columns, so the results open cleanly in Google Sheets, Excel, or any BI tool without any preprocessing.
Output columns (table view)
| Field | Type | Description |
|---|---|---|
searchQuery | string | The original address or property ID you submitted |
propertyId | string | Resolved Realtor.com property ID |
status | string | Listing status: for_sale, sold, off_market, pending, etc. |
listPrice | number | Current listing price in USD |
lastSoldPrice | number | Price the property last sold for |
lastSoldDate | string | Date of the last sale |
lastUpdateDate | string | Date the listing was last updated on Realtor.com |
beds | number | Number of bedrooms |
baths | number | Number of bathrooms |
sqft | number | Interior square footage |
yearBuilt | number | Year the property was built |
propertyType | string | Property type: single_family, condo, townhouse, etc. |
address | string | Street address line |
city | string | City |
state | string | Two-letter state code |
postalCode | string | ZIP code |
href | string | Direct Realtor.com listing URL |
propertyData | object | Full raw API response with tax history, schools, photos, estimates, mortgage info, and more |
Example output record
{"searchQuery": "742 Evergreen Terrace, Springfield, IL 62704","propertyId": "9535495300","status": "for_sale","listPrice": 485000,"lastSoldPrice": 410000,"lastSoldDate": "2021-06-15","lastUpdateDate": "2026-02-14","beds": 4,"baths": 3,"sqft": 2200,"yearBuilt": 1998,"propertyType": "single_family","address": "742 Evergreen Terrace","city": "Springfield","state": "IL","postalCode": "62704","href": "https://www.realtor.com/realestateandhomes-detail/742-Evergreen-Terrace_Springfield_IL_62704","propertyData": {"description": { "lot_sqft": 9200, "garage": 2, "pool": false, "heating": "Forced Air", "cooling": "Central" },"tax_history": [{ "year": 2023, "tax": 6800 }, { "year": 2022, "tax": 6500 }],"schools": { "schools": [{ "name": "Springfield Elementary", "rating": 8, "distance_in_miles": 0.4 }] },"estimates": { "current_values": [{ "estimate": 492000 }] },"photos": [{ "href": "https://ap.rdcpix.com/..." }],"mortgage": { "estimate": { "monthly_payment": 2640 } },"property_history": [{ "date": "2021-06-15", "event_name": "Sold", "price": 410000 }],"local": { "flood": { "flood_factor_score": 1 }, "noise": { "score": 42 } }}}
Input
| Parameter | Type | Default | Description |
|---|---|---|---|
searchQueries | array | required | List of US addresses or Realtor.com property IDs. Mix both in the same run. One per line. |
maxItems | integer | 0 (unlimited) | Maximum number of properties to process. Set to 0 for no limit. |
timeoutSecs | integer | 300 | Total actor run time limit in seconds. |
requestTimeoutSecs | integer | 30 | Per-request HTTP timeout in seconds before moving on. |
proxyConfiguration | object | Datacenter (United States) | Proxy type and location. Supports Datacenter, Residential, Special, and custom proxies. Optional. |
Example input
{"searchQueries": ["3291777140","3808 Warm Meadows St, Las Vegas","13018 Lumberjack Rd NW Unit 1"],"maxItems": 0,"requestTimeoutSecs": 30,"proxyConfiguration": { "useApifyProxy": true, "apifyProxyCountry": "US" }}
Use cases
- Real estate investment research: pull list price, last sold price, and estimated value for a watchlist of addresses to spot underpriced properties fast
- Competitive market analysis: compare beds, baths, sqft, and price per sqft across a neighborhood to understand pricing trends without visiting Realtor.com manually
- Lead enrichment: append property specs to a CRM export — beds, baths, sqft, year built, and listing status added to every address in your contact list
- Off-market property monitoring: track addresses that are currently off-market and detect when a new listing goes live
- Portfolio valuation: batch-process a list of owned properties to pull current estimates, recent price changes, and tax records in one run
- Property data pipelines: feed structured real estate data into Google Sheets, Airtable, or a database on a schedule using Apify integrations
How it works
- For each item in
searchQueries, the actor checks whether the input is a numeric string (treated as a Realtor.com property ID) or a plain-text address. - Plain-text addresses are sent to Realtor.com's geocoder, which returns a numeric property ID.
- The actor calls the Realtor.com GraphQL API with the property ID and retrieves the full listing record.
- Key fields are extracted and stored as flat columns. The complete raw API response is saved in
propertyDatafor anything deeper. - If a property is not found or a request fails, the record is saved with null fields and the run continues — one bad address never stops the whole batch.
FAQ
Can I mix addresses and property IDs in the same list? Yes. Numeric strings are used as property IDs directly. Everything else goes through the address resolver. You can mix both freely in a single run.
Does this work for off-market and sold properties? Yes. The actor pulls data for any property in the Realtor.com database, not just active listings. Off-market homes, recently sold properties, and pending sales all return data.
Do I need a Realtor.com account or API key? No. The actor uses the same API endpoint the Realtor.com mobile app uses. No credentials required.
What is inside the propertyData field?
The full raw API response, including tax history by year, nearby school ratings and distances, flood risk score, noise score, photo URLs with AI-generated tags, mortgage payment estimates, FHA eligibility, price history, HOA fees, open house dates, virtual tours, and neighborhood median stats.
When should I switch to residential proxies? Datacenter proxies (US) work for most runs. If you start seeing a high rate of null results on large batches, switch to Residential in the proxy settings. Residential proxies are harder to detect and better suited for high-volume scraping.
How many properties can I process per run?
There is no hard limit. Set maxItems to 0 to process your entire input list. Each property uses roughly two API requests: one for address resolution and one for the data fetch.
Can I schedule this actor to run automatically? Yes. Use the Apify scheduler to run the actor on a daily or weekly schedule. Combine it with Google Sheets integration to keep a spreadsheet updated automatically.
Integrations
Connect this Realtor.com property scraper with other tools using Apify integrations. Push results directly to Google Sheets or Google Drive, trigger workflows in Zapier or Make, sync data to Airtable or Airbyte, or post a Slack notification when a batch finishes. You can also use webhooks to pipe results into your own backend the moment each run completes.