Zillow data API: the official API or an Apify Actor?
Zillow limits its official API to approved partners. 8 Apify Actors in this catalogue return Zillow data over HTTP too: send the input to Apify's run-sync endpoint with your token and get the records back as JSON, from $0.40 a run plus $0.99 per 1,000 results at Store prices (plus platform usage).
Side by side
| Zillow data access (partner / Bridge) | Zillow connector for Claude | Apify Actors (8) | |
|---|---|---|---|
| Access | Approved partners only | No sign-in | Apify API token (any account) |
| What you get | Zillow does not publish an open self-serve listing API. Data access for industry partners runs through Zillow Group and MLS-related programs. | Home and rental search, property details by address, Zestimates and their history, neighbourhood market insights and mortgage payment estimates. | Rows defined by each Actor's published schema; up to 76 fields per record |
| Price | Partner terms; no public self-serve price. | No price listed | From $0.40 a run plus $0.99 per 1,000 results (Store price, Free plan), plus platform usage |
| Limits | Approval and licensing apply. Public-page scraping is a third-party alternative. | As set by the provider | Synchronous calls wait up to 300 s; longer runs go asynchronous |
| Docs | Zillow data access (partner / Bridge) | Claude connector directory: Zillow | Apify API: run-sync |
Official API facts checked 2026-11-09. Property data may carry broker and MLS restrictions. Public listing data only; not legal advice.
Which Actor for which job
All of them list $0.99 per 1,000 results on the Store, plus a start fee per run.
| Actor | Returns | Fields include | Call it |
|---|---|---|---|
| Zillow Daily Mortgage Rate & Lender Quote Scraper | Zillow mortgage rate records by product and state, plus optional Zillow lender directory profiles. | loanType, productType, scope | run-sync · Apify |
| Zillow Distressed Property Finder by City or ZIP | Distressed Zillow listings — foreclosures, pre-foreclosures, pre-market REO and auctions — with price, property specs, distress… | zpid, distressType, homeStatus | run-sync · Apify |
| Zillow For-Sale, Rent & Sold Listing Extractor | One record per Zillow property, home or rental building. Records keep the 33 legacy fields and add sold, tax, parcel, builder… | zpid, price, zestimate | run-sync · Apify |
| Zillow Market Trends Scraper | One dataset with three record types: regionMarketTrends (ZHVI, ZORI, sale and list metrics, forecasts and benchmarks per… | location, locationType, slug | run-sync · Apify |
| Zillow Property Manager Directory by City | Property manager profiles from Zillow — business and contact details, ratings, reviews, licenses, team, service areas, rental… | name, businessName, phone | run-sync · Apify |
| Zillow Research County Home Value Trend Scraper | ZHVI trend records with true 1/3/6/12-month changes, benchmarks, and ranks, plus tidy monthly history observations. | countyName, stateCode, stateName | run-sync · Apify |
| Zillow Research Home Value & Market Heat Scraper | Zillow Research observations: home values, rents, inventory, days to pending, price cuts, sales, market heat, forecasts, new… | regionName, regionType, date | run-sync · Apify |
| Zillow Upcoming Open House Finder by City or ZIP | One row per open-house showing with date, start/end time, type, status, property facts, agent/broker, MLS, photos and a link to… | zpid, address, city | run-sync · Apify |
Call Zillow Distressed Property Finder by City or ZIP
The call waits for the run and returns the records as JSON. Swap the Actor ID for any Actor in the table. Set APIFY_TOKEN first; runs bill to that account.
curl
curl -X POST "https://api.apify.com/v2/actors/dataspryva~zillow-distressed-property-finder-by-city-or-zip/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"locations":["Austin, TX"],"distressTypes":["foreclosure"],"includeDetails":false,"includeAuctionDetails":false,"maxItems":3}' Install: pip install "apify-client>=3"
Python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {
"locations": [
"Austin, TX",
],
"distressTypes": [
"foreclosure",
],
"includeDetails": False,
"includeAuctionDetails": False,
"maxItems": 3,
}
run = client.actor("dataspryva/zillow-distressed-property-finder-by-city-or-zip").call(run_input=run_input)
if run is None:
raise RuntimeError("The Actor run could not be started")
print(run.status, "dataset", run.default_dataset_id)
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item) Install: npm install apify-client
JavaScript
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"locations": [
"Austin, TX"
],
"distressTypes": [
"foreclosure"
],
"includeDetails": false,
"includeAuctionDetails": false,
"maxItems": 3
};
const run = await client.actor("dataspryva/zillow-distressed-property-finder-by-city-or-zip").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]); Generated from the Actor's published schema and checked, not executed.
Same data, other routes
- Zillow MCP server: these Actors as tools in Claude, Cursor, ChatGPT, VS Code and Codex.
- Zillow price drops to email: an n8n workflow you can import.
- Zillow new listings to Slack: an n8n workflow you can import.
- Zillow listings to Google Sheets: an n8n workflow you can import.
- Every Actor with a one-request API
When a call fails
Why does the workflow or script stop with HTTP 408?
The synchronous endpoint waits at most 300 seconds. After that it answers 408 while the run keeps going in Apify. Lower the result limit, or start the run asynchronously, wait for it to finish and then read its dataset.
Source: Apify API: run Actor synchronously and get dataset items
What do 400, 401, 402 and 403 from the Apify API mean?
Read error.type in the response body. 400 is invalid Actor input. 401 (user-or-token-not-found) means a token reached Apify but it is wrong or revoked. 402 with x402-payment-required means no token reached Apify at all: the n8n credential or the Authorization: Bearer header is missing, and Apify is offering its pay-per-run x402 route for agents instead; any other 402 is an exhausted usage limit on the account that pays for the run. 403 is a token without permission for that Actor or storage.
Source: Apify API: authentication; Apify documentation: agentic payments with x402; Apify API: run Actor synchronously and get dataset items
Why does starting an Actor through the API return run information instead of scraped results?
The Run Actor endpoint starts the Actor and immediately returns a Run object without waiting for completion. For results stored in the default dataset, pass the response's defaultDatasetId to Get dataset items; to wait and receive output directly, use the synchronous endpoint for dataset items or a key-value store record.
Source: Apify Run Actor API
Why are rows and hidden fields missing from my Apify dataset export?
The clean parameter enables both skipEmpty and skipHidden, removing empty items and fields whose names begin with #. This can produce fewer items than the requested limit; to retain those rows and fields, disable clean and ensure skipEmpty and skipHidden are also disabled.
Source: Apify Get dataset items API
Questions
Is there an official Zillow API?
Zillow does not publish an open self-serve listing API. Data access for industry partners runs through Zillow Group and MLS-related programs. Partner terms; no public self-serve price.
How much does Zillow data cost through an Apify Actor?
The Actors listed here charge from $0.40 a run plus $0.99 per 1,000 results on the Apify Store (Free plan), checked 2026-11-12, billed to the Apify account whose token makes the call. Actor start events and platform usage can add to that.
Can I get Zillow data as JSON in one HTTP request?
Yes, through Apify's run-sync-get-dataset-items endpoint: POST the Actor input with your token and the response is the dataset as JSON. It waits up to 300 seconds; longer runs need the asynchronous run endpoint.
Can an AI agent use the same Zillow data?
Yes. The Zillow MCP page bundles these Actors into one Apify MCP URL for Claude, Cursor, ChatGPT, VS Code and Codex, and lists Zillow connector for Claude.
Is it allowed to collect Zillow data?
Property data may carry broker and MLS restrictions. Public listing data only; not legal advice. Read Zillow's terms before you build on the data.
Sources
- Zillow data access (partner / Bridge) documentation, checked 2026-11-09
- Claude connector directory: Zillow, checked 2026-11-11
- Apify API: run Actor synchronously, checked 2026-11-11
- Zillow terms