REAL ESTATE · UNITED STATES
Zillow - Listings & Property Details
Search Zillow homes for sale, for rent or recently sold by city, ZIP code or search link, or paste property links.
About this data
Search Zillow homes for sale, for rent or recently sold by city, ZIP code or search link, or paste property links. Each listing becomes one row with price, beds, baths, area, address, coordinates, Zestimate, rent estimate, days on Zillow, photos and broker. Failures are reported, not charged.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
Zillow Listings
POST /v1/us/zillow/listings
One US location, up to three first-page listings for sale, rent or sold: listing ID/link/status, price/currency, bedrooms/bathrooms, area and lot size, property type, address/coordinates, Zestimate/rent estimate, days listed, broker and photos where published.
Autocomplete/bounds resolution is included; property-page expansion and owner profiles are excluded.
Input
Send a JSON body to POST https://api.ssh.autos/v1/us/zillow/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
location | string | required | 2–100 characters |
listingType | string | optional | one of forSale, forRent, sold; default "forSale" |
maxResults | integer | optional | 1–3; default 3 |
Returned fields
The answer is JSON: records, a list of up to 3, and summary, the run status and counts. Each record has these 47 fields; a field the source does not publish comes back null.
47 fields per record
| Field | Type | Notes |
|---|---|---|
zpid | string | Zillow property id (null for apartment buildings). |
url | string | Zillow page for the listing. |
source | string | one of search, property |
searchInput | string | The place, link or property you supplied. |
detailLevel | string | one of listing, full |
listingStatus | string | — |
statusText | string | — |
price | number | — |
priceText | string | — |
currency | string | — |
bedrooms | number | — |
bathrooms | number | — |
livingArea | number | — |
lotAreaValue | number | — |
lotAreaUnit | string | — |
homeType | string | — |
yearBuilt | integer | — |
address | string | — |
streetAddress | string | — |
city | string | — |
state | string | — |
zipcode | string | — |
latitude | number | — |
longitude | number | — |
zestimate | number | — |
rentZestimate | number | — |
taxAssessedValue | number | — |
daysOnZillow | integer | — |
dateSold | string | — |
brokerName | string | — |
agentName | string | — |
agentPhone | string | — |
mlsId | string | — |
mlsName | string | — |
hoaFee | number | — |
propertyTaxRate | number | — |
pageViewCount | integer | — |
favoriteCount | integer | — |
imageUrl | string | — |
photos | array of strings | — |
priceHistory | array of objects | — |
taxHistory | array of objects | — |
isBuilding | boolean | — |
buildingName | string | — |
units | array of objects | — |
scrapedAt | string | — |
error | null | Always null in the dataset; failures are in the run summary. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/us/zillow/listings -m POST -b '{"location": "Austin, TX", "maxResults": 2}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Zillow Scraper - Listings & Property Details. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt