Zillow Scraper API
One REST API for Zillow real-estate data. Turn a homedetails URL or a city into clean JSON: price, beds, baths, square footage, photos, the listing agent, and every listing on a results page, with residential proxies and PerimeterX handling built in.
Free 1,000 requests. Median response 2.6s. No credit card.
curl "https://api.zillowscraperapi.com/api/v1/zillow/property?url=https://www.zillow.com/homedetails/2092-zpid/&api_key=$API_KEY" Scrape Zillow without getting blocked
Anti-bot bypass
Proxy rotation
JS rendering
Structured JSON
Pay for success
One REST call
Choose from multiple Zillow Scraper API endpoints
Listings & Property Data
Agent
Rental Data API
Home Price & Sales Data API
What you can build
Comp and valuation models
Price and sales data by ZIP
Rental market tracking
Real-estate portals and apps
Agent and brokerage lead lists
Spreadsheet and BI exports
Simple, usage-based pricing
- All endpoints included
- Structured JSON output
- Anti-bot + rotating proxies
- 10 concurrent requests
- Community support
- Everything in Free
- Higher concurrency
- Email support
- Everything in Vibe
- Priority request routing
- Priority support
- Everything in Pro
- 500+ concurrent requests
- SLA + dedicated support
Pay-as-you-go top-ups run $0.90 per 1,000 successful requests. Median response 2.6s. You only pay for requests that succeed.
Drops into your stack
No-code
LLM and RAG
SDKs and REST
FAQ
It is a set of REST endpoints that take a Zillow URL, a zpid, or a location and return the data as structured JSON: a single property's full record, or every listing on a for-sale, for-rent, or sold results page. We handle the residential proxies, Zillow's PerimeterX challenge, and the parsing, so you call one endpoint with your api_key and get clean fields back.
Not for listing data. Zillow retired its Bridge Interactive feeds and its older GetSearchResults and GetDeepSearchResults endpoints, so there is no official Zillow API that returns for-sale, rental, or sold listings to general developers. The data still renders on the public pages, which is what this API reads and returns as JSON.
Two endpoints cover the core needs. The property endpoint takes a homedetails URL or a zpid and returns the full home record: address, price, price per square foot, beds, baths, living area, year built, the photo gallery, the description, and the listing agent. The search endpoint takes a location and returns every listing on a results page, with a status filter for for_sale, for_rent, or sold.
Zillow uses PerimeterX, which serves a Press-and-Hold challenge to untrusted traffic and blocks datacenter IPs, returning a page with no listing data. The API routes requests through residential proxies with anti-bot handling and automatic retries, so the real page loads and its embedded record is parsed. You never solve the challenge or manage a proxy pool yourself.
Scraping publicly visible web pages is generally treated as lawful in the United States, and courts have declined to treat access to public data as a Computer Fraud and Abuse Act violation, though Zillow's Terms of Use restrict automated collection, so review the terms and robots.txt for your use case and avoid personal or copyrighted data you do not have the right to use. This is general information, not legal advice.
Responses return in a median of about 2.6 seconds end to end, including proxy routing, PerimeterX handling, retries, and parsing. The free tier covers 1,000 requests, Pro pricing runs about $0.60 per 1,000 requests, and pay-as-you-go top-ups are $0.90 per 1,000 successful requests. You are billed only for successful results.