Question 1

What do I give it and what do I get back?

Accepted Answer

You give it a US street address. It returns one JSON record with up to 50 fields — the Redfin Estimate, price and price history, tax assessment and tax history, beds, baths, sqft, year built, lot size, property type, the county's public-record figures, county/FIPS/APN, lat/long, MLS number, listing description, listing agent and office phone, buyer's agent, FEMA flood zone, assigned schools, climate-risk scores, amenities, and the photo gallery — or { "found": false } if no source has a match.

Question 2

Does it return the Redfin Estimate / a valuation?

Accepted Answer

Yes — data.estimatedValue is the Redfin Estimate, Redfin's own automated valuation, in whole dollars. It came back on every address we tested, including sold and off-market homes. It is Redfin's number, not ours and not a Zestimate. When Zillow answers instead, the row carries data.zestimate (Zillow's Zestimate) and data.rentZestimate (its monthly rent estimate). They are different models — on 32 Philadelphia homes we checked, the Zestimate never equalled the Redfin Estimate and the two were a median 10.7% apart — so each keeps its own field.

Question 3

Which sources are supported?

Accepted Answer

Redfin and Zillow by default, with Realtor.com as an option. Redfin is the primary path and is where the full record comes from. Set source to 'all' to also look the address up on Realtor.com and merge its own value estimate and range, agent email, HOA fee and list date into the same row, or 'realtor' for Realtor.com alone (see the Realtor.com cost question below). Zillow returns the core physical facts (address, beds, baths, sqft, year built, lot size, property type) plus the Zestimate, rent Zestimate, latitude/longitude, county, county tax-assessed value, and a price when the home is listed or sold. The default source 'auto' tries Redfin first and falls back to Zillow when Redfin has no exact match, with no setting needed. Zillow sits behind PerimeterX, so a Zillow lookup can occasionally be refused; it is then reported as not found with the reason, and is free.

Question 4

How am I charged?

Accepted Answer

Pay-per-event: one charge per successful lookup (a match with address, city, and ZIP). Not-found or blocked lookups are free, so you never pay for a miss.

Question 5

Why did my batch stop before the end?

Accepted Answer

For one of two reasons, and the last row of the dataset says which and lists every address it skipped, free of charge. Either your run's maximum charge was reached (raise it and re-run the skipped addresses), or the batch was clearly not going to work: fewer than 3 of the first 50 addresses found (usually a list missing city, state or ZIP — fix it and re-run), 200 misses in a row, or 10 lookups in a row refused by the sites or timed out (re-run those later). A batch with ordinary misses mixed in runs to the end.

Question 6

Why not just fetch the pages?

Accepted Answer

Redfin and Zillow block plain HTTP requests on TLS/browser fingerprint (not just IP), so curl and a bare fetch get 403/429. Redfin is read from inside a real browser session; Zillow walls headless browsers outright, so it is read with a client that presents Chrome's fingerprint over residential IPs. Either way the actor reads each site's own structured data.

Question 7

Do I need a proxy?

Accepted Answer

No. Redfin works direct, and the Zillow fallback routes its requests through residential IPs on its own. The useProxy option additionally sends the Redfin browser through a residential proxy, which can help at high volume.

Question 8

Does it return listing photos?

Accepted Answer

Yes — the data.images array gives the listing's photo gallery as full-size image URLs in order (the first is the hero), each with width and height. The URLs are public CDN links you can load directly in an <img> tag. A home with no gallery (many off-market/sold listings) returns an empty array. Photos come from Redfin and, with source 'realtor' or 'all', Realtor.com; the Zillow-only mode returns none.

Question 9

Does it return floor plans?

Accepted Answer

Yes, when the listing publishes one: data.floorPlans holds them separately from the photos. Each entry has a url (the image, or the SVG preview of an interactive CubiCasa scan), a kind ('image' or 'interactive'), a viewerUrl for interactive scans, and the source. Most homes have no public floor plan, so the array is often empty: 10 of 28 for-sale homes sampled on 2026-10-28 had one, and off-market homes rarely do. Redfin is checked on every lookup; source 'all' also adds plans only Realtor.com tags. The Zillow-only mode returns none. The price per property is unchanged.

Question 10

Is this personal data?

Accepted Answer

It returns public property facts, plus the listing agent's, buyer's agent's and brokerage's names and the phone numbers (and, from Realtor.com, the email) they publish on the public listing page — that is business contact information, not private data. It does no owner lookup and adds no PII enrichment: there is no owner name, phone, email, or occupant data in the output.

Question 11

Does it work for rural and small-town addresses?

Accepted Answer

Yes. On 2026-10-27 we looked up 20 addresses in 10 small towns in 10 states — Ely NV, Marfa TX, Hettinger ND, Lewistown MT, Hazard KY, Valentine NE, Monticello UT, Greenville ME, Clayton GA and Hillsboro WV — and 17 came back as full records (the other 3 had no exact match on Redfin, and were free). What varies is how much the county and MLS publish: rural records are thinner — tax history came back on 8 of those 17, the county's beds/sqft on fewer — and a non-disclosure state like Texas publishes no sale prices at all. Fields a county does not publish are simply left out of the row.

Question 12

What does Realtor.com cost me?

Accepted Answer

This actor's price is the same in every mode — one charge per matched address. But Realtor.com only opens through Apify's Web Fetch service (it blocks ordinary scrapers), and the run calls Web Fetch with your own Apify account, so Apify bills you for it separately: about $0.0015 per Realtor.com page on the Free plan, less on paid plans. It is only called when Realtor.com has an exact match for your address, and Realtor.com is switched off for the rest of the run after 5 refused pages in a row. Realtor.com pages take ~15 s each, several in parallel. The default 'auto' never uses it.

Question 13

Why are some fields missing from my result?

Accepted Answer

Unknown fields are omitted rather than returned as null or 0, so what is present is real. Valuation, status, geo and county come back on effectively any resolvable address. Tax assessment needs a public county record, and MLS number, listing description and agent need an MLS record — a never-listed or off-market home simply won't have those keys.

Question 14

How current is the data?

Accepted Answer

It reflects each site's live data at run time, so the facts are as current as Redfin's/Zillow's own published records. Values are passed through as published — including the assessment roll year in data.taxYear, which is whatever the county last filed rather than the current year.

Field	Type
`query`	string\|null
`found`	boolean\|null
`source`	string\|null
`address`	string\|null
`city`	string\|null
`state`	string\|null
`zip`	string\|null
`beds`	integer\|null
`baths`	number\|null
`sqft`	integer\|null
`yearBuilt`	integer\|null
`lotSizeSqft`	integer\|null
`propertyType`	string\|null
`sourceUrl`	string\|null
`estimatedValue`	integer\|null
`zestimate`	integer\|null
`rentZestimate`	integer\|null
`price`	integer\|null
`priceLabel`	string\|null
`pricePerSqft`	number\|null
`lastSoldDate`	string\|null
`status`	string\|null
`latitude`	number\|null
`longitude`	number\|null
`county`	string\|null
`fips`	string\|null
`apn`	string\|null
`mlsId`	string\|null
`stories`	number\|null
`yearRenovated`	integer\|null
`fullBaths`	integer\|null
`halfBaths`	integer\|null
`taxAssessedValue`	integer\|null
`taxAssessedLand`	integer\|null
`taxAssessedImprovement`	integer\|null
`taxesDue`	number\|null
`taxYear`	integer\|null
`description`	string\|null
`listingAgent`	string\|null
`listingBroker`	string\|null
`priceHistory`	array\|null
`amenities`	object\|null
`schools`	array\|null
`riskFactors`	object\|null
`images`	array\|null
`floorPlans`	array\|null
`sources`	array\|null
`filledFrom`	object\|null
`realtorEstimate`	integer\|null
`realtorEstimateLow`	integer\|null
`realtorEstimateHigh`	integer\|null
`listDate`	string\|null
`hoaFee`	number\|null
`listingAgentPhone`	string\|null
`listingAgentEmail`	string\|null
`listingOfficePhone`	string\|null
`buyerAgent`	string\|null
`buyerBroker`	string\|null
`realtorFlags`	array\|null
`realtorUrl`	string\|null
`realtorPropertyId`	string\|null
`realtorError`	string\|null

Field	Type	Req	Default	Description
`address`	string	no	`"745 Garland Dr, Palo Alto, CA 94303"`	Full US property address, e.g. '745 Garland Dr, Palo Alto, CA 94303'. To look up several properties, use 'Property addresses' below — one run handles the whole list on a single browser, which is faster and cheaper than a run per address.
`addresses`	array	no	`["745 Garland Dr, Palo Alto, CA 94303","1600 Amphitheatre Pkwy, Mountain View, CA 94043"]`	Look up many properties in ONE run. Each address is scraped on the same warm browser and pushed as its own row, so a batch is substantially faster than starting a run per address. Combined with 'Property address' if you fill both, and duplicates are removed. Billing is unchanged: you are charged per matched property, not per address submitted. A batch stops early, with a free notice row listing the addresses it skipped, when your run's maximum charge is reached, or when the batch clearly isn't working: fewer than 3 of the first 50 addresses found (usually a list missing city, state or ZIP), 200 misses in a row, or 10 lookups in a row refused by the sites or timed out. Ordinary misses mixed into a list don't stop it.
`source`	string	no	`"auto"`	Which site to look the property up on. 'Auto' tries Redfin first (the full 40-field record) and falls back to Zillow (core physical facts) when Redfin has no exact match — no proxy setting needed. Pick a single source to pin the lookup to it. 'Realtor.com only' and 'All sources' (opt-in): 'All sources' runs Auto and also looks the address up on Realtor.com, returning ONE merged row per address — the Redfin/Zillow record plus Realtor's own value estimate (with its low–high range), listing agent phone/email, listing office, buyer's agent on sold homes, HOA fee and list date, with any gap filled from Realtor and named in 'filledFrom'. This actor's price is the same in every mode (one charge per matched address). IMPORTANT: Realtor.com pages can only be opened through Apify's Web Fetch service, which this run calls with YOUR Apify account, so Apify bills you for it separately (about $0.0015 per Realtor page on the Free plan, less on paid plans). It is only called for addresses Realtor.com has an exact match for, and Realtor is switched off for the rest of the run after 5 refused pages in a row. Realtor lookups take ~15 s each (several run at once).
`useProxy`	boolean	no	`false`	Route the Redfin browser through Apify residential proxy. Default off (direct). Turn on only for IP rate-limiting at high volume. Zillow lookups always use residential IPs on their own, whatever this is set to.