Zillow Property Listings Scraper

Export public Zillow search-card listings from locations or known search URLs for sale, rental or recently sold inventory research. Retain deduplicated property identity, available card fields and search provenance. The Actor applies explicit numeric filters to extracted cards and keeps partial, filtered-empty and blocked-source outcomes distinct. AUTO and PAGINATION read HTML; explicit SEARCH_STATE submits a copied Zillow search state to the structured search endpoint without HTML fallback.

Quick start

Use one known location, a low saved-listing cap and one source page. The existing San Francisco example is:

{
  "locations": ["San Francisco, CA"],
  "listingType": "for_sale",
  "extractionMethod": "AUTO",
  "minBeds": 2,
  "maxItems": 25,
  "maxPages": 1,
  "proxy": { "useApifyProxy": true }
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

One saved search-card property row with ZPID, source URL and page, collection time and available address, price, home-status, attribution, media and location fields. Missing values remain null or empty arrays. Search-card output does not include a complete property-detail record, and Zillow estimates or listing labels are not independent valuations.

Who is it for?

• Real-estate investors tracking prices, inventory, and comparable homes.
• Agents and brokerages monitoring public listings in target markets.
• Proptech and data teams building internal dashboards from public property search results.
• Relocation teams creating shortlists across multiple cities.
• Market researchers comparing public sale and rental inventory over time.

How you can use the data

• Prepare a San Francisco listing sample. Use the existing for-sale location and minimum-bedroom filter with low page and row caps. Keep ZPID, sourceUrl and sourcePage for manual review rather than treating a limited sample as total city inventory.
• Review an Austin rental subset. Use the existing Austin rental recipe or its known rental URL, retaining listingType beside price and address. Search-card prices can be source-formatted and estimates are separate fields, so do not interpret them as completed transaction values.
• Use a copied search URL deliberately. AUTO sends your authorized URL, including its query parameters, to Zillow's HTML page. It does not guarantee native map/filter interpretation. For structured requests, choose SEARCH_STATE and supply valid searchQueryState JSON in each source URL, without location sources. Returned bounds and common numeric filters are checked before rows are saved.
• Compare your own bounded snapshots. Store ZPID, source context and scrapedAt in your destination before comparing later exports. A missing listing can reflect a page cap, filters or failed access rather than a confirmed sale, removal or market-wide change.

Input settings

Setting	API key	Type	Description
Zillow search URLs	startUrls	array	Up to 100 HTTP(S) Zillow search URLs. Explicit SEARCH_STATE submits their searchQueryState; AUTO/PAGINATION retain HTML behavior.
Locations	locations	array	City, ZIP code, neighborhood, or area names converted to Zillow search URLs.
Resume URLs	resumeSearchUrls	array	URLs copied from RUN_CHECKPOINT after a bounded deadline stop. They replace fresh URLs and locations.
Listing type	listingType	string	for_sale, for_rent, or sold for generated location searches.
Extraction method	extractionMethod	string	AUTO and PAGINATION read HTML. Explicit SEARCH_STATE sends validated copied state with no bootstrap or HTML fallback.
Maximum listings	maxItems	integer	Global maximum unique rows, from 1 to 10,000.
Pages per search	maxPages	integer	Maximum pages per source, from 1 to 20.
Minimum price	minPrice	number	Keep rows at or above this numeric price.
Maximum price	maxPrice	number	Keep rows at or below this numeric price.
Minimum bedrooms	minBeds	number	Keep rows with at least this many bedrooms.
Minimum bathrooms	minBaths	number	Keep rows with at least this many bathrooms.
Proxy configuration	proxy	object	Existing runs default to a US residential Apify Proxy session. Omit groups for that default, use an explicit empty group list for standard Apify datacenter routing, supply other authorized groups, or disable the proxy.

AUTO and PAGINATION both read data embedded in HTML search pages. URLs containing searchQueryState retain those parameters, but this is not structured-search extraction or a guarantee that Zillow applies every native filter. Explicit SEARCH_STATE requires a valid searchQueryState object in every selected URL. Clear locations (unless using resume URLs). The copied state retains filters, sort, regions, bounds and page. Requests use Zillow's structured endpoint only, without bootstrap or HTML fallback. Missing/malformed state is rejected before charges or network. Applied-state or page identities are checked when Zillow returns them; absent echoes are not claimed as equality proof. Returned coordinates, price, bed/bath ranges and price ordering are checked where requested. Other native filters are passed through rather than independently guaranteed. Unknown or contradictory results fail instead of saving unrelated rows.

Input options

Direct rental URL example

{
  "startUrls": [
    { "url": "https://www.zillow.com/homes/for_rent/Austin,-TX_rb/" }
  ],
  "maxItems": 50,
  "maxPages": 2
}

Austin rentals

{"locations":["Austin, TX"],"listingType":"for_rent","maxItems":20,"maxPages":1}

Denver homes between $500,000 and $1,500,000 with at least two bedrooms

{"locations":["Denver, CO"],"minPrice":500000,"maxPrice":1500000,"minBeds":2,"maxItems":25,"maxPages":2}

Copied Zillow search URL

Paste an authorized search URL into startUrls with "extractionMethod":"AUTO" for HTML extraction, or choose "extractionMethod":"SEARCH_STATE" when the URL contains valid searchQueryState JSON and clear locations. Structured pagination begins at the copied state's current page and preserves its fields. Use minPrice, maxPrice, minBeds and minBaths for additional explicit post-extraction filtering in either mode. Verify output provenance and coverage; a bounded sample does not establish every native filter's semantics.

Output data

This synthetic row illustrates the output shape rather than a current property or market observation:

{
  "zpid": "12345678",
  "url": "https://www.zillow.com/homedetails/12345678_zpid/",
  "address": "123 Market St, San Francisco, CA 94103",
  "addressCity": "San Francisco",
  "addressState": "CA",
  "addressZipcode": "94103",
  "price": "$1,250,000",
  "unformattedPrice": 1250000,
  "currency": "USD",
  "beds": 3,
  "baths": 2,
  "area": 1450,
  "propertyType": "SINGLE_FAMILY",
  "homeStatus": "FOR_SALE",
  "statusText": "For sale",
  "zestimate": 1210000,
  "rentZestimate": 5200,
  "latitude": 37.7749,
  "longitude": -122.4194,
  "brokerName": "Example Realty",
  "imageUrl": "https://photos.zillowstatic.com/...jpg",
  "imageUrls": ["https://photos.zillowstatic.com/...jpg"],
  "daysOnZillow": 12,
  "isFeatured": false,
  "listingType": "for_sale",
  "sourceUrl": "https://www.zillow.com/homes/for_sale/San-Francisco,-CA_rb/",
  "sourcePage": 1,
  "sourceRoute": "HTML",
  "scrapedAt": "2026-07-08T08:00:00.000Z"
}

Group	Fields
Identity	zpid, url, providerListingId
Address	address, addressStreet, addressCity, addressState, addressZipcode
Price and estimates	price, unformattedPrice, currency, zestimate, rentZestimate
Property	beds, baths, area, lotAreaValue, lotAreaUnit, propertyType
Listing status	homeStatus, statusText, daysOnZillow, isFeatured, isShowcaseListing
Location and attribution	latitude, longitude, brokerName
Media/open house	imageUrl, imageUrls, hasImage, has3DModel, hasVideo, hasOpenHouse, openHouseStartDate, openHouseEndDate
Provenance	listingType, sourceUrl, sourcePage, sourceRoute, scrapedAt

Fields are null or an empty array when Zillow does not include them in the search card. This Actor does not fabricate property-detail data.

The default key-value store also contains:

• RUN_SUMMARY: final status, separate confirmed saved and actual charged counts, retries, per-source results, warnings, and any fatal error. Rows are saved before billing in batches of at most 10, limited by available capacity. A charge-limit race can leave saved but uncharged rows; counts are not assumed equal. A failed storage request may have committed partial rows not included in the confirmed saved count; inspect the accessible dataset after a failure.
• RUN_CHECKPOINT: the latest bounded progress marker and resumeSearchUrls when work remains.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses Apify pay-per-event pricing. The one-time start event is requested after input validation, before extraction, so a run may incur it without returning listings. The primary item event bills saved Zillow property listings, subject to the run's available event budget.

Current rates depend on your Apify plan or custom agreement. Check the live Apify Pricing tab before running production jobs.

Apify may also charge platform usage for compute, storage, proxies, or data transfer outside this Actor pricing. Check the Actor run and the live Pricing tab for the exact cost shown to your account.

Tips for best results

• Begin with a small saved-row cap. Start with a small maxItems value for your first run.
• Check filter coverage. A copied URL is used for HTML requests; exact native map/filter interpretation is not guaranteed. Explicit numeric filters are checked against extracted card values.
• Limit pages deliberately. Keep maxPages conservative. Ordinary Zillow result pagination is commonly capped near 20 pages for one region/filter slice.
• Inspect partial outcomes. If one source fails after other sources save rows, inspect RUN_SUMMARY instead of assuming the entire dataset is complete.
• Copy explicit resume URLs. Copy RUN_CHECKPOINT.resumeSearchUrls into the resumeSearchUrls input after a deadline-bounded partial run.
• Keep filtered-empty outcomes distinct. Explicit numeric filters are applied before saving and charging. A run can legitimately finish EMPTY_FILTERED when Zillow returned candidates but all were excluded.

Limits and caveats

• Zillow can change its page payload. Detected HTTP 200 challenges are treated as blocks, not empty searches. Explicit SEARCH_STATE uses only the structured search endpoint; it does not bypass or solve challenges.
• Requests are sequential: at most three attempts per page, 20 pages per source, 100 sources and 10,000 saved rows. An independent 240-second budget reserves five seconds for final persistence. Known 404/410 targets are marked unavailable, not inferred private or deleted.
• Only public listing/search data is extracted. The actor does not access private accounts, messages, saved homes, or owner-only data.
• It detects but does not solve CAPTCHA/challenge pages.
• Search-card output is not the same as full property-detail output. Tax history, complete price history, schools, descriptions, agent contacts, and full photo galleries are outside this Actor's contract.

The unique-listing and per-source page caps bound coverage, and search-card fields are not full detail-page facts. Zero rows can succeed with an explicit reason: EMPTY_FILTERED when numeric filters excluded candidates, an explicit zero-total search response, or an unavailable target. Unexplained empty discovery or challenges remain failures, even when other sources saved useful rows. Billing and essential storage errors remain fatal. Budget/deadline stops are reported as partial, not complete extraction.

Copy RUN_CHECKPOINT.resumeSearchUrls into the explicit resumeSearchUrls input for a separate continuation. These URLs replace fresh URLs and locations; a partly processed page may be revisited, so deduplicate ZPIDs across runs in your destination. Each new run has normal start and saved-listing charges. Automatic resurrection of a checkpointed run is rejected to prevent repeated paid work.

Privacy and data handling

Results, RUN_SUMMARY, and RUN_CHECKPOINT are written to the run's Apify storage. Error diagnostics include reproduction input with credentials and proxy endpoints redacted. Use authorized public search inputs and avoid unnecessary personal or sensitive data.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl "https://api.apify.com/v2/acts/fetch_cat~zillow-property-listings-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"locations":["San Francisco, CA"],"listingType":"for_sale","maxItems":20}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/zillow-property-listings-scraper').call({
  locations: ['San Francisco, CA'],
  listingType: 'for_sale',
  maxItems: 20,
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/zillow-property-listings-scraper').call(run_input={
    'locations': ['San Francisco, CA'],
    'listingType': 'for_sale',
    'maxItems': 20,
})
print(run['defaultDatasetId'])

MCP and AI agents

You can ask your AI assistant to collect data with Zillow Property Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Zillow Property Listings Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/zillow-property-listings-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Zillow Property Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/zillow-property-listings-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Zillow Property Listings Scraper to collect up to 5 for-sale listings in San Francisco, CA with at least 2 bedrooms and one page. Keep ZPIDs and source context without interpreting the sample as total inventory or an appraisal.”
• “Retrieve up to 5 rental listings in Austin, TX with one page. Keep source prices, address fields and missing values without collecting full property histories or certifying availability.”
• “Collect up to 5 Denver, CO for-sale listings priced from 500,000 to 1,500,000 with at least 2 bedrooms and one page. Keep explicit filtered-empty outcomes separate from failed discovery, without calculating a market-wide median.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does this actor need a Zillow account?

No. It is designed for public search result pages only.

Can it scrape rentals and sold properties?

Yes. Use listingType for location inputs or paste matching Zillow search URLs in startUrls.

Why did my run stop with a block message?

Zillow may block automated traffic. Lower maxPages, keep concurrency low, and use Apify residential proxy settings.

Can I use exact Zillow filter URLs?

You can submit a copied URL for HTML extraction with AUTO, retaining query parameters, but exact native filter interpretation is not guaranteed. Explicit numeric filters are supported. Explicit SEARCH_STATE submits valid copied state without switching to HTML. It checks returned state/page identifiers when present and verifiable bounds/common numeric ranges; other native filters remain pass-through.

Does it use Zillow GraphQL?

No. GraphQL evidence currently applies mainly to full property-detail queries. This Actor uses Zillow search-card state and search-page data so it does not multiply detail requests or silently expand the paid output contract.

Why did a zero-result run fail?

Unexplained empty discovery or a challenge remains an actionable failure. Explicit zero-total search responses, unavailable targets and numeric-filter exhaustion can succeed with truthful reasons in RUN_SUMMARY. A useful partial dataset does not make a failed source complete.

Does it scrape property detail pages?

The first version focuses on search-result listing data. Detail-page enrichment can be added later if demand and reliability justify it.

Related Actors

• Google Maps Places Scraper — Collect public Google Maps business listings and place details for area context, rather than Zillow property records.
• Zillow Property Details Scraper — Collect available facts, photos and published history from known Zillow property detail pages.
• Rightmove Property Listings Scraper — Collect UK Rightmove search listings, rather than full individual property pages.
• Idealista Scraper — Collect public Idealista listings from search or property URLs in Spain, Portugal and Italy.
• Bing Search Results Scraper — Collect Bing web-search result titles, snippets and links, using a different search engine from Google.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥