Real Estate Aggregator - Multi-Platform avatar

Real Estate Aggregator - Multi-Platform

Pricing

from $0.01 / 1,000 results

Go to Apify Store
Real Estate Aggregator - Multi-Platform

Real Estate Aggregator - Multi-Platform

Search Zillow, Redfin and Realtor.com in one run and get one deduplicated list: each home's price on every site, Zestimate, Realtor.com estimates, price and tax history, MLS number and listing agent.

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

The Howlers

The Howlers

Maintained by Community

Actor stats

4

Bookmarked

21

Total users

0

Monthly active users

8 days ago

Last modified

Features

Limited permissions

Share

Real Estate Aggregator - Zillow + Redfin + Realtor

Search Zillow, Redfin and Realtor.com in one run and get one deduplicated list. A home listed on more than one site becomes one row with the price on each platform, the price spread, every source URL, the best photos, and the data only one site has: Zillow's Zestimate, Rent Zestimate and Zestimate history, Realtor.com's home value estimates, neighborhoods, schools and flood score, Redfin's MLS number, days on market and HOA fee, the fullest price history and tax history, and the listing agent with a phone or email when any site has one.


Quick Start

{
"zipCode": "78704",
"maxResultsPerPlatform": 50
}
{
"city": "Austin, TX",
"priceMin": 400000,
"priceMax": 900000,
"bedsMin": 3,
"propertyTypes": ["house"],
"listingStatus": "for_sale"
}
{
"address": "606 Josephine St, Austin, TX 78704",
"searchRadius": 1,
"listingStatus": "recently_sold"
}

How it works

The aggregator runs our scraper for each platform on your Apify account (Zillow Scraper, Redfin Scraper, Realtor.com Scraper), all three by default and all at the same time, then merges the listings.

  • Matching: each listing gets one address key built the same way for every site (house number and street with standard USPS suffixes and directions, the unit, and the 5-digit ZIP code), so "2404 Euclid Ave Unit 1" on Zillow and "2404 Euclid Avenue #1" on Realtor.com are the same home. The key is on each row as matchKey.
  • Merging: price follows deduplicationStrategy (by default Zillow's, then Redfin's). Beds, baths, square feet, year built and description come from the first site that has them; a value no site gave stays null, never 0. pricesByPlatform, priceVariance, allUrls, sources and sourceListings (each site's own short row) show where everything came from.
  • One platform's trouble never hides the others: if a site is slow, fails or blocks, the listings from the other sites are still merged and returned, and that site gets one row with resultType: "status", its fetchStatus and a plain message. platformStatus in the OUTPUT record has every platform's outcome. A source run that is still going when the wait runs out (3 minutes, plus about 2.5 seconds per requested listing, up to 15 minutes) is stopped and the listings it already found are kept.

Each source scraper reads public listing data the way that site's own web pages do, through Apify residential proxies with a real browser fingerprint (and a Camoufox stealth browser fallback for Zillow and Realtor.com). Nothing logs in.

Statuses: for_sale and pending run on all three sites. recently_sold runs on all three (Redfin's sold search). for_rent runs on all three (Redfin's own rental search).

Address searches: each platform places the address on the map and returns only homes within searchRadius miles of it, with distanceMiles on each row (Redfin searches the ZIP code that contains the address). A platform that cannot place the address returns a status row instead of searching somewhere else.


Input Parameters

ParameterTypeDefaultDescription
platformsarray["zillow","redfin","realtor"]Which platforms to search. Empty means all three
citystring-City and state, for example 'Austin, TX'
zipCodestring-5-digit ZIP code
addressstring-Street address to search around
searchRadiusinteger5Miles around the address
priceMin / priceMaxinteger-Price range
bedsMin / bathsMininteger-Minimum bedrooms and bathrooms
propertyTypesarray[]house, condo, townhouse, multi_family, land
listingStatusstring"for_sale"for_sale, pending, recently_sold or for_rent
maxResultsPerPlatforminteger50Maximum listings from each platform before merging
deduplicationStrategystring"keep_all_merged"Which platform's price leads a merged row: keep_all_merged (Zillow, then Redfin), keep_zillow, keep_lowest_price or keep_highest_price
webhookUrlstring-URL to POST 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:

EventWhen it is chargedPrice
Actor startOnce when the run starts, one event per GB of memory (minimum one). At the default 1 GB of memory that is $0.10 per run$0.10 per GB
Listing AggregatedOnce per unique property returned (one row per home after merging)$0.04
Property EnrichedOnce per row merged from two or more platforms (sources lists them; the row combines each site's price, links, photos and extras such as the Zestimate, Realtor.com estimates, MLS number and HOA fee). A row found on one platform only is not charged$0.02
Duplicate DetectedOnce per extra source listing merged into a row: a home found on 3 sites counts 2. The OUTPUT record's duplicatesFound counts every merge; the number actually charged is eventsCharged.duplicate_detected, which is lower when a run stops at your maximum charge$0.001
ResultEach item written to the default dataset$0.00001

The source scraper runs are separate runs on your account and are billed by those actors: their run start, their per-listing event, and their own detail events (Zillow Zestimate and price history, Realtor.com agent and neighborhoods, Redfin market trends) when those rows carry that data. Status rows are never charged. When you set a maximum cost per run, the run stops before any property whose full cost (its events plus the per-item dataset fee) would go over it.


Troubleshooting

Only status rows came back

Every selected platform returned no listings. Read each status row's message: a city without its state, filters that exclude every home, or a site that blocked every attempt. Nothing was charged as a listing.

A home shows up twice

Two sites gave different street numbers or ZIP codes for it, so the address keys differ. Compare the two rows' matchKey.

How do I test for free?

Run the actor with the default input (no location) or set demoMode to true. It returns labeled sample aggregated 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