Pull only the Zillow listings that changed since your last sync

No, it is how the paging works and we would rather over-deliver than silently drop rows. Zillow's result page holds roughly 41 listings and it is fetched whole; max_results caps how many pages get fetched, not how many rows come out of one. A measured request for max_results 3 returned 41; max_results 200 with max_pages 3 returned 123. You are not charged per row, so slice the array to what you need.

Because Zillow does not publish a Zestimate for every home, and we return null rather than an estimate of our own. Measured: only 19 of 123 Austin search rows carried one. Crucially, this is not something property_detail fixes — pulling the full record for zpid 464181906 also returned zestimate_usd null, zestimate_low_pct null and zestimate_history as an empty array. Newer construction and recently-listed homes are the usual gaps. If your product depends on a valuation, plan for the null case rather than retrying.

Because they are two different vocabularies. You filter with lowercase words — house, condo, townhouse, multi_family, land, manufactured, apartment — and the response speaks SCREAMING_SNAKE: SINGLE_FAMILY, CONDO, TOWNHOUSE, MULTI_FAMILY, MANUFACTURED. 'house' and 'SINGLE_FAMILY' are the same thing under two names, so a string comparison between what you sent and what you got will always fail. Map them explicitly.

status is the machine enum and status_text is the label Zillow prints on the card. Across 123 measured rows every single status was FOR_SALE while status_text split four ways: Active (118), House for sale (2), Home for sale (2) and Zillow Preview (1). Those are not different states — they are different phrasings, plus one marketing badge. Branch on status; show status_text.

Square feet, always, including the lot_min and lot_max filters. Divide by 43,560 for acres — a measured lot_sqft of 24,668.03 is 0.57 acres. This trips people up because US listing sites present large lots in acres and small ones in square feet, so a filter written as lot_min: 1 returns essentially everything rather than one-acre-plus properties.

Set fetch_all to true. Zillow's own search caps out around 860 results for any one query no matter how you page, so a busy metro is truncated well before you have the market. fetch_all works around that at the cost of runtime — a plain 3-page search already measured 6.8 seconds. The cheaper alternative for wide areas is to split the query geographically by ZIP and merge, which also keeps each response small enough to process incrementally.

It adds price_per_sqft_usd, year_built, price_change_usd with its date (measured: -10,000 on 2026-08-21), price_history, tax_history, schools, neighborhood, the full description, every photo with a count, and the listing agent block. It drops days_on_market, which came back null there while search reported 60 for the same zpid. Several of the added arrays are frequently empty — tax_history, schools and home_insights were all [] on the measured record, and every listing_agent field was null. Empty means Zillow did not publish it for that home.

When you want inventory that just appeared rather than everything that matches a place. new_listings reads Zillow's published feed and returns only identity and location — zpid, url, address, region, postal_code, changed_at — which you then resolve through property_detail for the numbers. Watch window.is_recent_window on each response: for_sale, sold and for_rent are large enough that you get a genuine recent slice, while the smaller categories (for_sale_by_owner, auction, pending, other) fit inside the window entirely, so what you get is the whole category rather than new arrivals. Poll incrementally by passing the previous call's window.newest as changed_after.

Zillow API is a ReefAPI endpoint group for us homes with prices, history and estimates. It returns live JSON through POST requests under /zillow/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. Zillow calls use the same shared credit balance as every other ReefAPI engine.

No login to Zillow is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live new_listings call, and production requests fetch live data through ReefAPI rather than a static sample.

Zillow actions currently cost 1-3 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call zillow actions with the same key, credit pool and JSON envelope used by normal REST requests.