Zillow Scraper — Apify Actor

Scrape real-time property listings, agent data, and market statistics from Zillow.com.

Quick Start

Local

cd zillow_scraper_apify
pip install -r requirements.txt
apify run

Deploy to Apify Cloud

apify login
apify push

Tasks

Task	Required Input	Description
search-by-location	location	Search properties by city/zip/address slug
search-by-coordinates	lat, lng	Search properties near coordinates
search-by-address	address	Resolve a street address to full property details
property-details	zpid	Full property details by Zillow Property ID
similar-homes	zpid	Comparable homes ranked by similarity
market-stats	location	Regional market statistics (ZHVI, inventory, rents)
agent-search	location	Real estate agents by location
agent-details	agentname or agentUrl	Agent profile information
agent-reviews	agentname or agentUrl	Agent reviews
agent-properties	agentname or agentUrl	Agent's listed properties
autocomplete	query	Location and address autocomplete suggestions

Input

All inputs are passed as a JSON object. See .actor/INPUT_SCHEMA.json for the full schema.

Example: Search by location

{
  "task": "search-by-location",
  "location": "Austin-TX",
  "listType": "for-sale",
  "page": 1,
  "sort": "newest"
}

Example: Property details

{
  "task": "property-details",
  "zpid": 2060051934
}

Example: Similar homes

{
  "task": "similar-homes",
  "zpid": 2060051934,
  "count": 10,
  "listType": "for-sale"
}

Example: Market stats with history

{
  "task": "market-stats",
  "location": "Austin-TX",
  "history": true
}

Proxy Configuration

Zillow aggressively blocks datacenter IPs. For reliable scraping, provide proxy URLs:

{
  "task": "search-by-location",
  "location": "Austin-TX",
  "proxies": ["http://user:pass@proxy.example.com:8080"]
}

Without proxies, requests go direct and will likely be blocked after a few calls.

Architecture

This Actor is a Django-free port of the zillow-scraper REST API. The scraping engine (curl_cffi with TLS impersonation, session pooling, retry logic) is preserved exactly. What changed:

• Django removed: no ORM, no DRF, no middleware, no Celery
• Redis replaced: in-memory TTL cache per run (stateless Actor)
• Proxy selection simplified: no RapidAPI host detection, just pass proxy URLs
• Single entry point: one main.py routes tasks to scraper methods

Output

Results are pushed to the default Apify Dataset. You can preview, export (CSV/JSON/Excel), or access via API.

# Retrieve results via API
curl "https://api.apify.com/v2/datasets/YOUR_DATASET_ID/items?token=YOUR_TOKEN"

Scheduling

In Apify Console: Schedules > Create Schedule > set cron and target this Actor.

Development

# Run locally
apify run

# Test a specific task
apify run --input '{"task": "autocomplete", "query": "Austin TX"}'

# Deploy
apify push

License

Same as the parent project.