Zillapi

Look up any U.S. property by address, with one HTTPS call. No SDK, no auth dance, just a bearer token.

curl -s "https://api.zillapi.com/v1/properties/by-address" \ -G --data-urlencode "address=1600 Pennsylvania Ave NW, Washington DC 20500" \ -H "Authorization: Bearer $ZILLAPI_KEY" \ | jq '.data | {zpid, address, zestimate, bedrooms, bathrooms, livingArea}'

You get back a wrapped JSON envelope,{ "data": {...}, "request_id": "..." }, with 300+ typed fields on the property: Zestimate, beds, baths, square footage, year built, lot size, tax history, school ratings, listing agent, photos, and theresoFactsMLS attribute blob.

The gap that opened in 2021 is what third-party REST wrappers fill. They normalize requests against Zillow's own data layer, cache responses, expose a clean OpenAPI surface, and meter usage in credits instead of broker contracts. The Zillow API ecosystem in 2026 is essentially this category: a handful of independent services offering the same shape of contract, a bearer token, a JSON response, per-credit pricing, that the original ZWSID program offered fifteen years ago.

The Zillow API surface in this repo covers nine functional areas mapped to nine REST endpoints. Each is one HTTPS call, returns wrapped JSON, and bills against your credit balance only on success.

- Look up a property by address,/v1/properties/by-address. Free-form U.S. address; we geocode and resolve a zpid upstream.
- Look up a property by Zillow URL,/v1/properties/by-url. Paste anyhomedetails,b,community, orapartmentsURL.
- Look up a property by zpid,/v1/properties/{zpid}. Cache-served when fresh.
- Get the Zestimate,/v1/properties/{zpid}/zestimate. Returns the Zestimate, rent Zestimate, tax-assessed value, and last-sold price as a four-field response.
- Search for-sale or for-rent listings,/v1/listings(GET, bbox-based) or/v1/search(POST, structured filters). Up to ~820 results per call withPAGINATION, more withPAGINATION_WITH_ZOOM_IN.
- Pull price + ownership history,/v1/properties/{zpid}/price-historyand/v1/properties/{zpid}/tax-history.
- Get school ratings + agent contact,/v1/properties/{zpid}/schools(GreatSchools ratings, distance, level) and/v1/properties/{zpid}/agent(agent name, email, phone, broker).
- Photos and open houses,/v1/properties/{zpid}/photos(full-resolution + responsive widths) and/v1/properties/{zpid}/open-houses.
- Async batches + signed webhooks,POST /v1/properties/batchfor up to 500 records per job; webhook deliveries are HMAC-signed.

Six languages, each in its own folder. Every snippet is one screen, uses the language's stdlib or a single zero-friction dependency, and resolves to the same canonical shape: a wrapped JSON envelope underdatawith arequest_idfor support traceability.

curlplusjqis the fastest way to verify a key works and inspect the response shape. No build step, no installer, every Unix box has both.

curl -s "https://api.zillapi.com/v1/properties/by-address" \ -G --data-urlencode "address=1600 Pennsylvania Ave NW, Washington DC 20500" \ -H "Authorization: Bearer $ZILLAPI_KEY" \ | jq '.data | {zpid, address, zestimate, bedrooms, bathrooms}'

The Python ecosystem is the most common landing zone for this API. We usehttpxbecause it has a clean sync API and built-in connection pooling;requestsworks identically if you prefer it.