Property search monitoring
Use Zillow endpoints to turn property search monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Zillow public property search and home detail pages into structured data for property research workflows.
Collect Zillow autocomplete, property detail, and property search data for real estate and property intelligence workflows.
Endpoint families
3
Documented params
16
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
6
Schema refs
3
{
"platform": "Zillow",
"endpoint": "zillow-autocomplete",
"method": "GET",
"path": "/zillow/autocomplete",
"auth": "apiKey"
}Related use cases
Use cases
Collect Zillow autocomplete, property detail, and property search data for real estate and property intelligence workflows.
Use Zillow endpoints to turn property search monitoring into repeatable API requests with documented inputs and JSON responses.
Use Zillow endpoints to turn home detail enrichment into repeatable API requests with documented inputs and JSON responses.
Use Zillow endpoints to turn rental and sale market research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/zillow/autocomplete
/zillow/property/{zpid}
/zillow/search
Endpoint catalog
/zillow/autocompleteReturns normalized Zillow public web autocomplete candidates. Semantic candidates may include region_id/region_type compatibility aliases plus region_ids/region_types arrays; prefer complete bounds metadata for Zillow search when present.
/zillow/property/{zpid}Returns normalized Zillow public property details using Zillow's public persisted GraphQL property payload, including optional typed sections for address parts, listing attribution, pricing, history, media, facts, schools, and nearby homes when present.
/zillow/searchReturns normalized Zillow public listing search results. Callers must pass complete map bounds from autocomplete when available, or a region id fallback.
Start building