Recognize that Zillow does not offer a public API for listing data; the Zillow API program that existed historically was shut down — any current Zillow integration requires a formal partnership agreement.
For agent/broker use cases, evaluate Bridge Interactive (a Zillow-owned platform) which provides RESO-compliant MLS data feeds under separate licensing with participating MLSs.
Apply for Bridge Interactive API access through the MLS or through Bridge directly; approval is MLS-specific and requires broker or agent affiliation.
Once credentialed, use Bridge's RESO Web API endpoints (OData-based) identically to other RESO-compliant servers — see the RESO Web API query route for implementation details.
For Zestimate-like AVM data, use ATTOM, CoreLogic, or HouseCanary APIs instead, as Zillow does not expose Zestimate values via API to third parties.
For public-facing consumer apps requiring broad listing coverage, consider aggregators like Estated or direct MLS IDX/RESO agreements.
Known gotchas
Bridge Interactive data access is gated per MLS; you cannot query listings from an MLS you are not credentialed with even through the same Bridge API key.
Do not attempt to scrape Zillow.com; their ToS explicitly prohibits scraping and they actively block it — this creates legal and operational risk.
Zillow's co-mingling rules for Bridge data are strict; data sourced via Bridge for one MLS cannot be displayed alongside data from a different source without clear attribution boundaries.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp