Market research
Pull every home in a map area with price, beds, baths and living area, then compute price per square foot by ZIP code or home type.
- 1search
- Market table
Homes from any Zillow search and full property records by URL or address: price, beds, baths, living area, home type and status, as typed JSON in the same response envelope. Public data only.
Pick the data you need. The live endpoints take a Zillow search URL, a property URL or an address and give you clean JSON back for 1 credit per successful call. Cards without a GET path are on our final API list and show the input they take.
GET/api/v2/zillow-search/Homes from a Zillow search URL, a page at a time: address, price, beds, baths, living area and status.
GET/api/v2/zillow-detail/One property by Zillow URL or street address: price, home type and status, beds, baths and zpid.
INlocationReal estate agents for a location, with name, screen name, Zillow profile URL, photo and business.
GET/api/v2/social-media-platform-email/Public email addresses found on Zillow pages for a keyword: email, page title, description, URL and scrape time.
INkeywordsPublic phone numbers on Zillow pages that match a keyword, with the country and dial code.
Pick an endpoint, fill in the input and press Run. Without a key you see the catalog sample and nothing is billed. With your API key it runs a real call from your browser.
Every successful call costs 1 credit, whether the page holds one profile or a page of comments. Failed calls cost nothing. A free tier lets you try it first.
On Pro, 1,000 calls at 1 credit cost $1.58. Scale brings that to $1.20, so 250,000 Zillow calls a month is $299.
See all plans →| Plan | Price / mo | Credits / mo | Per 1,000 calls |
|---|---|---|---|
| Free | $0 | Free tier | — |
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Built to be easy to start with, even if you've never scraped a website. Here's how to get Zillow data in a few minutes:
searchQueryState with mapBounds and filterState.url, or one property URL or street address in urls, per call.next_cursor; pass it back as cursor for the next page. Property details are one record per call.X-API-Key header, or ask your AI agent over MCP.Two ways in. Use whichever matches what you already have.
You already have the links to the pages you want.
zillow.com/homes/for_sale/?searchQueryState=%7B%22isMapVisi…zillow.com/homedetails/17-Zelma-Dr-Greenville-SC-29617/1102…You don't know the items yet: find them with a keyword.
// GET /api/v2/zillow-search/ { "url": "https://www.zillow.com/homes/for_sale/?searchQueryState=%7B%22isMapVisible%22%3Atrue%2C%22mapBounds%22%3A%7B%22west%22%3A-124.61%2C%22east%22%3A-120.37%2C%22south%22%3A36.71%2C%22north%22%3A38.74%7D%2C%22filterState%22%3A%7B%22sort%22%3A%7B%22value%22%3A%22days%22%7D%7D%2C%22isListVisible%22%3Atrue%7D", "method": "zoom", "delay": "1" }
// GET /api/v2/zillow-detail/ { "urls": "https://www.zillow.com/homedetails/17-Zelma-Dr-Greenville-SC-29617/11026031_zpid/" }
| Send this | Parameter | And you can get |
|---|---|---|
| Zillow search URL | url · method | Homes with address, price, beds, baths, living area and status |
| Property URL or street address | urls | One property: zpid, price, home type and status, beds and baths |
Optional on list endpoints: cursor (pass back next_cursor for the next page). Auth is one header: X-API-Key. Send parameters in the query string (GET) or as a JSON body (POST).
The one thing to know: each data type has its own shape. Field names stay the same on every call, so code and agents read them directly. Samples below come from the live catalog.
// GET /api/v2/zillow-search/?url=https://www.zillow.com/homes/for_sale/?searchQueryState=%7B% // one item of data.listings · catalog sample { "zpid": "12345678", "detailUrl": "https://www.zillow.com/homedetails/.../12345678_zpid/", "address": "123 Main St", "city": "San Francisco", "state": "CA", "zipcode": "94110", "price": 1250000, "bedrooms": 3, "bathrooms": 2, "livingArea": 1450, "homeStatus": "FOR_SALE", "foundFromSearchUrl": "https://www.zillow.com/homes/for_sale/?searchQueryState=..." }
// GET /api/v2/zillow-detail/?urls=https://www.zillow.com/homedetails/17-Zelma-Dr-Greenville-SC // one item of data.property · catalog sample { "zpid": 11026031, "is_valid": true, "street_address": "17 Zelma Dr", "city": "Greenville", "state": "SC", "home_status": "RECENTLY_SOLD", "home_type": "SINGLE_FAMILY", "price": 415000, "bedrooms": 4, "bathrooms": 3, "address_or_url_from_input": "https://www.zillow.com/homedetails/17-Zelma-Dr-Greenville-SC-29617/11026031_zpid/", "scraped_at": "2026-06-24T12:00:00.000Z" }
Every response is {"success": true, "data": {…}}: your input echoed back, the result under its own key (profile, posts, comments…) and next_cursor for the next page.
Public Zillow data powers real estate market research, investment screening, price tracking and property data enrichment. Here are five common jobs, and the Zillow scraper endpoints each one chains together.
Pull every home in a map area with price, beds, baths and living area, then compute price per square foot by ZIP code or home type.
Search the areas you invest in, filter the results to your price and size range, then pull each property record to confirm type and status before an offer.
Run the same Zillow search on a schedule and compare prices and status between runs. Spot price cuts and homes that go pending.
Turn a list of street addresses into Zillow records with zpid, price, home type, status, beds and baths, ready to join with your own data.
Search recently sold homes near a property, then open the closest matches for type, size and price to build a quick comparison.
Zillow Scraper fetches clean, structured Zillow data at low cost: built for market research, investment screening, price tracking and AI agents.
Each request reads Zillow at call time; property records say when in scraped_at.
Same field names on every call: price, beds, baths and living area as numbers.
Search returns next_cursor; run up to 3 requests in parallel per key.
Draw the area and set filters on Zillow; the search URL carries them to the API.
The Scrapier MCP server reaches every endpoint from Claude Code, Cursor, Windsurf and VS Code with one command.
Plain REST: Python, Node.js, cURL, n8n, Make, Zapier or Google Sheets.
Property details accept a Zillow URL or a plain street address.
When Zillow changes its pages, Scrapier updates the scraper; your field names stay the same.
1 credit per call, however many homes the page holds. Failed calls are never billed.
Zillow's data APIs, served through Bridge Interactive, are for approved partners and limit how the data can be used. Scrapier reads public Zillow search results and property pages with one API key, at a price you know before the call runs.
Any non-2xx response is free, so retries cost nothing.
At 1 credit a call. Flat per-call pricing, no compute units or bandwidth to estimate.
No application, data agreement or MLS membership to request.
The same key and JSON envelope cover Realtor.com, Idealista, Airbnb, Google Maps and more.
| Feature | Scrapier Zillow Scraper | Zillow/Bridge APIs (partner access) | DIY scraper |
|---|---|---|---|
| Whose data | Any public listing | Datasets your partner agreement covers | Any public listing |
| Setup | One API key | Application and approval | Proxies, browsers, parsers |
| Maintenance | Handled by Scrapier | Terms and dataset changes | Breaks on layout changes |
| Cost | From $1.20 per 1,000 calls | Set by your agreement | Servers, proxies and engineering time |
| AI agents | MCP server included | Build your own | Build your own |
No. Each endpoint returns one data type. To get a search and the full record of each home, call zillow-search then zillow-detail with each detailUrl, or let an AI agent chain the calls over MCP.
A Zillow search URL with a searchQueryState parameter that holds at least mapBounds and filterState. Draw your area and set filters on zillow.com, then copy the address bar. Send one URL per call in url.
Yes. zillow-detail takes a Zillow property URL or a street address in urls and returns one record with zpid, price, home type, status, beds and baths. next_cursor is always null for this endpoint.
As many as Zillow shows publicly for your search. zillow-search returns a page at a time with next_cursor; pass it back as cursor for the next page. Each page is one call at 1 credit.
Yes, if the search on Zillow shows them. Set the listing type and filters on zillow.com before copying the URL; the filters travel in filterState. Property details also work for recently sold homes, as the catalog sample shows.
When Zillow doesn't show a value, the field is null, so you can tell "not shown" from zero. Check for null before you compute averages such as price per square foot.
It depends on what you collect, where you are and how you use it, so this is not legal advice. Scrapier returns publicly visible data only. Check Zillow's terms and local rules before you republish listing data or photos.
Yes. Any tool that can make an HTTP request works: n8n, Make, Zapier, Google Sheets, Airbyte or your own code. Send your key in the X-API-Key header and read the JSON response.
Yes. Run claude mcp add -t http scrapier https://mcp.scrapier.io/mcp with your key in an X-API-Key header. The agent finds the right Zillow endpoint with search_endpoints and calls it with run_scrape, in Claude Code, Cursor or Windsurf.
Check the status code first: 401 means the X-API-Key header is missing, 403 an invalid key, 402 no credits left, 429 too many requests (wait Retry-After seconds). For search, check the URL has mapBounds and filterState. Then report the request and response.
Both live Zillow endpoints cost 1 credit per successful call, however many homes the page holds. Failed calls are free. Plans: Hobby $29 for 15,000 credits, Pro $79 for 50,000, Scale $299 for 250,000, Enterprise custom. A free tier lets you try it first.
Run up to 3 requests in parallel per API key. If you go faster, the API answers 429 with a Retry-After header: wait that many seconds and retry. 429 and 5xx responses are never billed. Property details can run long, so set a client timeout of 210 seconds or more.
Use the requests library: requests.get("https://proxy.scrapier.io/api/v2/zillow-detail/", headers={"X-API-Key": key}, params={"urls": "17 Zelma Dr, Greenville, SC 29617"}, timeout=210). The response is JSON, so read r.json()["data"]["property"] directly; there is no HTML to parse.
Free API key. No sales call, no proxy setup, and failed calls are free.