Zillow API docs

Send a Zillow link or an address. Get back the listing price, status, Zestimate, rent Zestimate, home facts, photos, price history, tax history and broker as JSON.

Base URL and authentication

All endpoints live under https://api.propertiesapi.com/v1. Send your key in the x-api-key header. Requests without a key get 401 missing_api_key; an unknown key gets 401 invalid_api_key.

curl -G "https://api.propertiesapi.com/v1/zillow/property" \
  -H "x-api-key: $PROPERTIESAPI_KEY" \
  --data-urlencode "address=2640 Steiner St, San Francisco, CA 94115"

Use with Claude

PropertiesAPI also runs a remote MCP server at https://api.propertiesapi.com/mcp, so Claude Code, Claude Desktop and claude.ai can look up Zillow homes with your API key, at the same credits as the API. See Use PropertiesAPI with Claude.

Bulk lookup and Google Sheets

For a list of homes, upload a CSV of Zillow links, zpids or addresses in your dashboard and download it back with the main fields on every row (Bulk lookup), or use the Google Sheets script for =ZILLOW(A2) formulas. Both use the same credits as the API.

SDKs and integrations

Official clients for Python and Node.js install from this site (not from PyPI or npm); an n8n community node and a Zapier app aren't published yet. See SDKs and integrations for what they do and how to call the API from n8n and Zapier today.

Endpoints

The response

A successful lookup returns { data, meta }. data is the property, with camelCase fields. The main ones:

• zpid, detailUrl, address (plus streetAddress, unit, city, state, zipcode, latitude, longitude): which property this is. An apartment building has zpid: null; use its detailUrl as its id.
• homeStatus, statusText and price: the listing status and listing price. A sold home whose sale price isn't disclosed has price: null, never 0.
• Apartment buildings (zillow.com/apartments/... links): you get the building, and price, beds, baths, livingArea and unit describe its lowest-priced unit available now (no move-in date, or one on or before the lookup date; if none is available yet, its lowest-priced unit). The other units aren't returned yet.
• zestimate and rentZestimate: Zillow's estimates, when Zillow shows them.
• beds, baths, livingArea, lotSize, yearBuilt, homeType: the home facts.
• daysOnZillow (Zillow's own day count, usually set for sold and off-market homes too; for days on market use calculated.days_on_market), imgSrc and photos (a list of image URLs).
• calculated: figures PropertiesAPI calculates from the returned fields, such as price per square foot, gross yield and price drops. See the property endpoint.
• priceHistory, taxHistory and schools: lists of past events, tax years and nearby schools.
• brokerName, agentName and their phones: who listed it.

meta has credits, cached, cache_key, fetched_at, source, release, took_ms and completeness (which of the commonly missing fields this response supplied), plus warning when something needs checking. When source_age is "approximate", the source served a copy it may have collected earlier: fetched_at is when we received it, so the data can be a few hours older. Which fields are filled can depend on how the home was first looked up (by link, zpid or address). With raw=true, data.raw is the unmapped source record: it is unstable, so don't parse it. See every field on the property endpoint page, or read what each one means, with recorded examples, in the response field reference.

Null fields

If Zillow doesn't show a field for a property, it comes back as null. Lists come back empty. Don't treat null as zero.

Latency

A live lookup (x-cache: MISS) takes typically 6 seconds, up to about 20. Set a client timeout of at least 120 seconds: an occasional lookup takes longer. Repeat lookups of the same home within 24 hours come from our cache and are free. For many properties, use batch instead of calling one at a time.

Errors

Errors use standard HTTP status codes and one JSON shape, { error: { code, message, details? }, meta: { took_ms } }:

{
  "error": {
    "code": "not_found",
    "message": "No Zillow property matches this input"
  },
  "meta": {
    "took_ms": 11840
  }
}

Codes with a retry-after wait (429 rate_limited, daily_share_exhausted and env_key_daily_cap; 503 upstream_busy, upstream_unavailable, store_unavailable, live_lookups_capped, state_unavailable and storage_full) can be retried after that many seconds (not upstream_blocked: its 502 carries retry-after too, but collection is paused, so it isn't retried automatically); the daily caps wait until midnight UTC. Retry 500, other 502 codes and 504 with exponential backoff. Don't retry other 4xx errors without changing the request. Other 503 codes mean live lookups are off on our side: retrying soon won't help. Errors aren't billed.

Rate limits

Two limits apply to every account. Each one is per account: all of its API keys count together.

• Requests a minute counts every request, cache hits included. Each address, link or zpid in a batch counts as one request. Past it you get 429 rate_limited; wait the retry-after seconds. x-ratelimit-limit and x-ratelimit-remaining show where you are.
• Live lookups a day (Free only) counts lookups that go to Zillow, including ones that find nothing. Cache hits are free and don't count. Past it you get 429 daily_share_exhausted until 00:00 UTC; cached properties still work. Buying a prepaid pack or a plan lifts it. Buying a pack also ends the free trial: from then on lookups use your prepaid credits.
• Lookups running at once. Each account can have 8 live lookups running at the same time. A live lookup takes typically 6 seconds, up to about 20, so this is what sets real throughput. Past it you get 503 upstream_busy; retry after retry-after. Cache hits don't count.
• Failed lookups. If too many of an account's live lookups within a UTC day find nothing or fail, new uncached lookups pause until 00:00 UTC with 429 too_many_failed_lookups. Check the addresses, links or zpids you send.
• Rarely, a service-wide safety limit answers 503 live_lookups_capped. It isn't about your account; wait the retry-after seconds.

For big lists, pace batches to your plan's per-minute limit and retry 429s after retry-after.

Headers and plans

Responses, errors included, carry these headers:

Plans:

Overage on paid plans: your plan's rate per 1,000 lookups, shown on each plan. No cap on usage: after your included lookups, each lookup is billed at your plan's rate. Optionally set a monthly limit. Or pay as you go: $10 per 1,000 lookups, prepaid, in packs from $20 for 2,000 lookups up to $250 for 25,000 lookups. No subscription; credits last 12 months, and on a plan they are used after its included lookups. Buying a pack ends the free trial: from then on lookups use your prepaid credits. Repeat lookups of the same home within 24 hours come from our cache and are free. Zillow links and addresses cost the same: 1 credit per successful lookup. Batch takes up to 50 items per request. See pricing for details.

OpenAPI spec

Download /openapi.json (OpenAPI 3.1). It's generated from the same definitions as these pages.

Acceptable use

The data is provided as-is, without any guarantee of accuracy or completeness. Don't use it for consumer reports or decisions covered by the FCRA, such as credit, insurance, employment or tenant screening.

Zillow is a trademark of Zillow, Inc. PropertiesAPI is an independent service and is not affiliated with, endorsed by or sponsored by Zillow.