Skip to content

Zillow Listings and Sale Prices via Scraper

A Zillow scraper API lets a market-comps or valuation-tracking workflow pull public Zillow listing data without you running your own headless browsers or proxy fleet.

OUTPUT FORMATSHTMLJSONMarkdown

You send a Zillow URL, the service renders the page and returns structured output you can parse. This page covers what fields come back, how the request options change the credit cost, and how to choose between selector-based and AI-based extraction.

What a Zillow scrape returns

Each listing response is designed to carry the fields a comp analysis usually needs: address, list price, beds, baths, square footage, Zestimate, days on market, agent info, neighborhood and the image gallery. The same call can also surface sale prices, rental rates and neighborhood signals when those appear on the public page. Output is JSON when you pass extraction rules; otherwise you receive the rendered page for your own parsing.

A useful rule of thumb: if a field is visible on the public listing page after JavaScript runs, it is a candidate for extraction. If it only appears after login or behind an account wall, it is out of scope for this workflow.

How the request flow works

The flow has four steps. First, create an account to get an API key and the free starting credits. Second, install an SDK if you want one — Python, Node.js, Go, PHP, Ruby and Java are published, and plain cURL works too. Third, send one HTTP call with your API key and a Zillow URL; proxy rotation, fingerprint handling and JavaScript rendering happen on the service side. Fourth, add advanced parameters only when the page needs them.

The advanced parameters worth knowing are render_js for JavaScript-heavy pages, stealth_proxy when CAPTCHA handling is needed, country_code for geo-targeting, and ai_extract_rules for natural-language extraction. These are the same parameter names used across the wider API, so a Zillow workflow can share configuration with other scrapers.

Selector rules versus AI extraction

There are two ways to get structured JSON back. The first is extract_rules: you map CSS selectors (or XPath) to field names, and the response is parsed JSON keyed by those names. This is deterministic and cheap to reason about, but it breaks when Zillow changes its markup. The second is ai_extract_rules: you describe the fields you want in natural language and the service returns structured JSON without selectors. This tolerates markup changes better but gives you less control over exactly which element is read.

A practical split: use extract_rules for stable, high-volume fields like list price and beds; use ai_extract_rules for fields that are hard to pin to a single selector, or when you are prototyping a new field set.

Field and control map

Use this map to decide which request options a given Zillow workflow needs before you write code.

  • Listing fields (address, list price, beds, baths, square footage, Zestimate, days on market, agent info, neighborhood, image gallery): available from the rendered page; pair with extract_rules or ai_extract_rules.
  • JavaScript-dependent pages: set render_js. This is the option that most Zillow listing pages will need.
  • CAPTCHA or aggressive bot checks: set stealth_proxy.
  • Geo-targeted results: set country_code.
  • Natural-language field spec: set ai_extract_rules instead of extract_rules.
  • Visual verification: request a full-page screenshot alongside the extraction.
  • LLM-ready output: request Markdown when you want to feed listings into a language model rather than a database.

A small comp-set example

Suppose you are tracking five comparable homes in one ZIP code. You collect the five public listing URLs, then send one request per URL with render_js enabled and an extract_rules map that names the fields you care about: address, list_price, beds, baths, sqft, zestimate, days_on_market, agent_name. The response for each URL is a JSON object with those keys. You store the five objects with a timestamp, and on the next run you diff the zestimate and days_on_market values to see movement.

This example uses only the field names the service documents; it does not assume any particular price or Zestimate value. The point is the shape of the workflow: one URL in, one structured record out, repeated across a comp set.

Blocked request versus empty extraction

Two failures look similar but need different fixes. A blocked request means the service could not get a usable page back — often a CAPTCHA or an IP-level block. The fix is usually to enable stealth_proxy or adjust the proxy tier. An empty extraction means the page loaded but your rules matched nothing — often because the markup changed or your selector targeted an element that only appears after a scroll. The fix is to inspect the rendered HTML, update the selector, or switch that field to ai_extract_rules.

Checking the HTTP status and the presence of expected keys separately will tell you which case you are in before you spend credits on retries.

How credits are consumed

Every request consumes at least one credit. Turning on JavaScript rendering raises the cost to five credits for a successful request. Premium proxies add ten credits when JS rendering is off, or twenty-five when it is on. The stealth_proxy option is the most expensive at seventy-five credits. Credits expire after one month and do not carry over, so size a large comp-set run against the monthly allowance instead of assuming unused credits will accumulate. These per-request credit figures are commercial terms that should be verified against the current pricing page before you commit to a budget; treat the numbers here as a planning framework rather than a locked quote. Because Zillow listing pages rely heavily on JavaScript, most Zillow requests will sit at the five-credit tier at minimum. Reserve premium or stealth proxies for pages that genuinely need them, and test a small sample first to see which tier your target pages actually require.

Choosing a plan for a Zillow workflow

The published plan tiers differ mainly in monthly credits and concurrent requests. A small comp-tracking job that runs a few hundred requests a month fits comfortably in the lower tiers; a portfolio-wide daily refresh across many ZIP codes will need the higher concurrency tiers so requests do not queue. The Business tier and above add priority email support, a dedicated account manager and team management, which matter when several analysts share one account.

All published prices are exclusive of VAT. Plan names, credit allowances and concurrency limits are listed in the pricing table below; confirm current terms before committing to a tier.

Published plan tiers and limits
PlanPriceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. Credits are valid for one month and do not roll over. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every tier. Confirm current pricing before purchase.

Credit cost per request by option (owner-confirmed terms pending)
OptionCredits per successful request
Base request1
JavaScript rendering (render_js)5
Premium proxy, no JS rendering10
Premium proxy with JS rendering25
stealth_proxy75

Credit costs apply per successful request. Confirm these per-request credit costs against the current pricing page before publication, and treat the table as a planning framework until verified.

Frequently asked questions

Do I need a Zillow account to scrape Zillow?

No external Zillow account is needed. You sign up for an API key, send the URL, and the service handles the request. The starting allowance is commonly offered as 1,000 free credits with no card required, but confirm the current free allowance on the provider's pricing page before you rely on it.

Is scraping Zillow legal?

Public-facing pages can usually be scraped, but you should review Zillow's terms of service before deploying and avoid post-login content. Legality depends on your jurisdiction and use case; this page is not legal advice.

What data can I extract from Zillow?

Anything that renders on the public page. In practice that includes address, list price, beds, baths, square footage, Zestimate, days on market, agent info, neighborhood and the image gallery. Use extract_rules with CSS selectors or ai_extract_rules for AI-driven extraction to get structured JSON back.

How do I get structured JSON from Zillow?

You have two routes to a parsed JSON response. With extract_rules, you supply a selector-to-field-name mapping and the service reads each element into the matching key. With ai_extract_rules, you describe the fields you want in plain language and the service resolves them without selectors. Either way, the body you receive is already parsed JSON rather than raw HTML.

Which programming languages can I use to scrape Zillow?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Zillow?

A typical starting offer is 1,000 free credits on signup with no card required, and paid plans commonly begin around $19/month for higher volume and concurrency. Credit cost per request depends on the options you enable: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Credits are usually valid for one month and do not roll over. These credit costs and the free allowance are commercial terms that should be checked against the current pricing page before you budget a run; treat the figures here as a planning framework rather than a locked quote.

What is the difference between a blocked request and an empty extraction?

A blocked request means the service could not get a usable page back, often due to a CAPTCHA or IP-level block; the fix is usually to enable stealth_proxy or adjust the proxy tier. An empty extraction means the page loaded but your rules matched nothing, often because the markup changed; the fix is to inspect the rendered HTML and update the selector or switch that field to ai_extract_rules.