Zillow and Redfin data from one API
Most US property questions need both portals, because a listing that is stale on one is often live on the other and the sold history rarely matches. Both are covered here under one account, with the same request shape, so the join happens in your code rather than across two vendor contracts.
Neither portal publishes a public listings API for this. Zillow's developer programme is partner-gated and Redfin has no open equivalent, so the practical alternative is two scrapers you maintain yourself. This is read-only public listing data, no account on either portal, one key.
What the two engines give you
- Zillow search
- search, search_by_coordinates, search_by_url, new_listings
- Zillow detail
- property_detail, comps, sold
- Redfin search
- search, autocomplete
- Redfin detail
- listing_detail, similar, market_stats
- Shared shape
- one key, one base URL, the same JSON envelope on both
Cross-check one address on both portals
Three calls tell you whether the two portals agree about a property.
- 1
POST /zillow/v1/searchfind the property and take its id from the row
- 2
POST /zillow/v1/property_detailprice, tax history, Zestimate, status
- 3
POST /redfin/v1/searchsame address on the other portal; compare status and price
Two records for one address. Where they disagree, that disagreement is the signal: it is usually a stale status on one side rather than a price change.
Where the two sources genuinely differ
| zillow | redfin | |
|---|---|---|
| Sold history | Zillow exposes a dedicated sold endpoint and comps | Redfin exposes market_stats rather than a sold endpoint |
| Estimates | Zestimate travels on the property detail | no equivalent estimate field is published |
| Depth | 14 actions including coordinate and url search | 5 actions; search plus detail, similar and stats |
| Sold price coverage | in twelve non-disclosure states the sold price is absent at source, not withheld by us | the same legal limit applies |