Zillow Email Scraper API
Last updated: · REST · JSON
Send GET https://proxy.scrapier.io/api/v2/social-media-platform-email/?keywords=marketing with your key in the X-API-Key header. You get the page of emails back as JSON. 1 credit per page of emails; failed calls are free.
- 1 credit per page of emails
- Failed calls free
- 3 parallel requests per key
Call the Zillow Email Scraper API
Use the Zillow Email Scraper API from your own apps, scripts or agents. You need a Scrapier account and the API key from your dashboard. Pick a language.
import requests# Replace YOUR_API_KEY with the key from your Scrapier dashboardAPI_KEY = "YOUR_API_KEY"params = { "keywords": "marketing", "platform": "Zillow", "email_domains": "@gmail.com", "country": "us", "language": "en", "include_all_emails": "false",}r = requests.get( "https://proxy.scrapier.io/api/v2/social-media-platform-email/", headers={"X-API-Key": API_KEY}, params=params, timeout=210,)r.raise_for_status()# The result sits under data.emailsresult = r.json()["data"]["emails"]print(result)
// Replace YOUR_API_KEY with the key from your Scrapier dashboardconst API_KEY = "YOUR_API_KEY";const params = new URLSearchParams({ keywords: "marketing", platform: "Zillow", email_domains: "@gmail.com", country: "us", language: "en", include_all_emails: "false",});const res = await fetch(`https://proxy.scrapier.io/api/v2/social-media-platform-email/?${params}`, { headers: { "X-API-Key": API_KEY }, signal: AbortSignal.timeout(210_000),});if (!res.ok) throw new Error(`HTTP ${res.status}`);const { data } = await res.json();console.log(data.emails);
# One GET request. The key goes in a header, never in the URL.GET /api/v2/social-media-platform-email/?keywords=marketing&platform=Zillow&email_domains=@gmail.com&country=us&language=en&include_all_emails=false HTTP/1.1Host: proxy.scrapier.ioX-API-Key: YOUR_API_KEYAccept: application/json
# Scrapier publishes an OpenAPI spec that covers every endpoint. No API key needed.curl -O https://proxy.scrapier.io/api/v2/openapi.json# Import openapi.json into Postman, Insomnia, Bruno or a code generator,# then add your key as the X-API-Key header.
# 1. Add the Scrapier MCP server to Claude Codeclaude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"# 2. Ask your agent. It finds the endpoint with search_endpoints# and calls it with run_scrape:"Find public email addresses on Zillow pages that mention marketing and list them with their page URLs"run_scrape("social-media-platform-email", {keywords: "marketing"})
Zillow Email Scraper API in Python
Plain requests is all you need — no SDK. Every response is typed JSON.
Install
Zillow Email Scraper API in JavaScript
Works in Node 18+, Deno, Bun and edge runtimes with the built-in fetch.
Check your setup
Zillow Email Scraper API over HTTP
One GET request. Auth is a single X-API-Key header.
Check your setup
Zillow Email Scraper API OpenAPI definition
Download the spec once, then import it into the tools you already use. No key is needed to fetch it.
Download the spec
Zillow Email Scraper API over MCP
The same endpoint is a tool call for Claude Code, Cursor and Windsurf. Same keywords, same 1 credit per page of emails.
Install
Other ways to call it
Zillow Email Scraper API Interactive Playground
Edit the request, watch the code update, then run it. Without a key it shows the catalog sample and bills nothing. With your key it makes a real call from your browser; the key goes only to proxy.scrapier.io and is never stored.
GET /api/v2/social-media-platform-email/?keywords=marketingPress Run request to send it. Without a key you get the catalog sample.
Failed calls are not billed.
The sample is the same for every input: it shows the response shape, not the account you typed.
Example response, catalog sample from 9 Nov 2026
{
"success": true,
"data": {
"keyword": "marketing",
"network": "Zillow.com",
"page": 1,
"page_size": 20,
"emails": [
{
"network": "Zillow.com",
"keyword": "marketing",
"title": "We are digital marketing experts. We offer services & plans to ...",
"description": "Strategy & Planning SEO & Analytics Social Media Marketing Content Marketing ... thakurinnovation2058@gmail.com #DigitalMarketing #BrandGrowth ...",
"url": "https://www.zillow.com/p/DT24GiFkdWe/",
"email": "thakurinnovation2058@gmail.com",
"scraped_at": "2026-10-03T07:21:48.617Z"
}
],
"next_cursor": "zc1.eNrtj7EOgzAMRNOtY7_hZqtKUCemrv0GFEVpCxEiAZSECTH3t2v6CUwg9TxYej6fdEKIz4wOJYKNXZ3b3oEwoiwInvGM0dvcDDGw5dGnbF20gS11sK0374FXn_h2dyu4voaAhQMYVZWSpEj-RmlNMOa5YqQGpGRxI0zRg3Kcaq0XsWedDpB4rP5_7VrnzZ-XjVFfJ8AqQA"
}
}Data You Can Extract
Zillow Email Scraper is a Zillow email extractor built on public search. Every field below comes from the catalog sample response, as typed JSON.
Email and source page
4 fields in the response.
- title
- description
- url
Search context and timing
3 fields in the response.
- network
- keyword
- scraped_at
Response envelope and paging
6 fields in the response.
- success
- data.keyword
- data.network
- data.page
- data.page_size
- data.next_cursor
Response Schema Reference
Every field in the sample response. Field names stay the same on every call.
| Field | Type | Example | Description |
|---|---|---|---|
emails.email | string | "thakurinnovation2058@gmail.com" | The email address found on the page |
emails.title | string | "We are digital marketing experts. We offer …" | Title of the page where the address appeared |
emails.description | string | "Strategy & Planning SEO & Analytics Social …" | Snippet of the page text around the match |
emails.url | string | "https://www.zillow.com/p/DT24GiFkdWe/" | Link to the Zillow page the address was found on |
emails.network | string | "Zillow.com" | The site the match came from, Zillow.com |
emails.keyword | string | "marketing" | The keyword this match was found for |
emails.scraped_at | string | "2026-10-03T07:21:48.617Z" | ISO 8601 time the result was collected |
success | boolean | true | true on every 200 response |
data.keyword | string | "marketing" | The keyword you sent, echoed back |
data.network | string | "Zillow.com" | The site searched; Zillow.com in the catalog sample |
data.page | integer | 1 | Page number of this response; 1 on the first call |
data.page_size | integer | 20 | Results per page; 20 in the catalog sample |
data.next_cursor | string | "zc1.eNrtj7EOgzAMRNOtY7_hZqtKUCemrv0GFEVpCxE…" | Pass back as cursor for the next page; null on the last page |
Request Parameters Reference
| Name | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
keywords | string | Yes | — | Search keyword, one per call. Required on the first call. Default marketing. Aliases: keyword, query, q | marketing |
cursor | string | No | — | Pass back data.next_cursor to fetch the next page; null means the last page. Leave empty on the first call | — |
platform | string | No | Zillow | Platform name or any domain. Default Zillow. Fixed by the cursor after the first call | Zillow |
email_domains | string | No | @gmail.com | Email domains to look for, comma-separated; empty means any. Default @gmail.com. Fixed by the cursor | @gmail.com |
location | string | No | — | Optional location term or terms. Fixed by the cursor | — |
country | string | No | us | Google country code (gl). Default us. Fixed by the cursor | us |
language | string | No | en | Google language code (hl). Default en. Fixed by the cursor | en |
include_all_emails | boolean | No | false | Boolean, default false. Fixed by the cursor | true |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool. On by default; leave as is | true |
raw_data | boolean | No | false | Return the raw upstream payload under raw_responses instead of the formatted emails | true |
One keyword per call: to run ten keywords, make ten calls. Booleans are the strings true or false. Options marked fixed by the cursor keep their first-call value on later pages.
Pagination in the Zillow Email Scraper API
The Zillow Email Scraper API returns results in pages. Pass data.next_cursor back as cursor to get the next page; when it is null there are no more. Each successful call, first page or later, costs 1 credit.
Access Without Zillow Login
The Zillow Email Scraper API needs no Zillow account, no login and no session cookies. You send your Scrapier key in the X-API-Key header and get JSON back. It reads public data only: what any visitor sees without logging in.
Speed, Cost and Concurrency
| Metric | Value | Source |
|---|---|---|
| Cost of a successful call | 1 credit | Scrapier catalog |
| Cost of a failed call | 0 credits | Any non-2xx response |
| Parallel requests per key | 3 | Above that: 429 with Retry-After |
| Recommended client timeout | 210 seconds | Scrapier docs, every endpoint |
Latency of the Zillow Email Scraper API
Scrapier does not publish a latency or success-rate figure for this endpoint. Each call reads Zillow at call time, so response time depends on Zillow and on the size of the result. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
Limits of the Endpoint
Honest constraints of the Zillow Email Scraper API.
- Public data only.
- A failed call, for example a missing or unavailable page of emails, returns a non-2xx status and costs 0 credits.
- Data is read live at call time.
- 3 parallel requests per key; above that the API answers
429withRetry-After. - Large results come in pages; pass
data.next_cursorback ascursor. - Fields Zillow does not show are not returned.
Scrapier vs the Official Zillow API
A manual Google search is the better choice for a handful of one-off lookups. It also lets you judge each page in context before you copy anything.
| Feature | Scrapier email scraper | Searching Google by hand |
|---|---|---|
| What it does | Runs the Zillow-specific search for you and returns matches as JSON | You type each search and copy results from the page |
| Fields returned | 7 fields per match: email, title, description, URL and scrape time | Whatever you copy by hand |
| Paging | <code>next_cursor</code> walks the results page by page | Click through result pages yourself |
| Repeat runs | Same call on a schedule, same field names | Redo the work each time |
| Setup time | Minutes: sign up and send a request | None, but slow past a few searches |
| Cost | 1 credit per page of emails, from $1.20 per 1,000 pages | Your time |
Errors and Retry Handling
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Page of emails data returned in data.emails | Yes | — |
| 400 | Bad or missing input | No | Check keywords: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Retry logic for the Zillow Email Scraper API
import time, requests def get_email(value, key, tries=5): for attempt in range(tries): r = requests.get( "https://proxy.scrapier.io/api/v2/social-media-platform-email/", headers={"X-API-Key": key}, params={"keywords": value}, timeout=210, ) if r.status_code == 429: time.sleep(int(r.headers.get("Retry-After", 2 ** attempt))) elif r.status_code >= 500: time.sleep(2 ** attempt) else: r.raise_for_status() return r.json() raise RuntimeError("gave up after retries")
Pricing and Rate Limits
| Plan | Monthly price | Pages Of Emails included | Cost per 1,000 |
|---|---|---|---|
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Billing rules for the Zillow Email Scraper API
The Zillow Email Scraper API bills 1 credit per successful page of emails. Failed calls, meaning any non-2xx status, cost 0 credits. Every plan allows 3 parallel requests per key. The free tier lets you try it before you pay.
Bulk Lookups and CSV
keywords takes one value per call. For a list, loop and run up to 3 requests in parallel per key, then flatten each row into one CSV line.
import csv, requests from concurrent.futures import ThreadPoolExecutor values = ["marketing"] # your list def fetch(value): r = requests.get( "https://proxy.scrapier.io/api/v2/social-media-platform-email/", headers={"X-API-Key": "YOUR_API_KEY"}, params={"keywords": value}, timeout=210, ) r.raise_for_status() out = r.json()["data"]["emails"] return out if isinstance(out, list) else [out] # 3 parallel requests per key is the limit with ThreadPoolExecutor(max_workers=3) as pool: rows = [row for part in pool.map(fetch, values) for row in part] cols = ["email", "title", "description", "url", "network", "keyword"] with open("out.csv", "w", newline="") as f: w = csv.DictWriter(f, fieldnames=cols, extrasaction="ignore") w.writeheader() w.writerows(rows)
CSV export from the Zillow Email Scraper API
email,title,description,url,network,keyword thakurinnovation2058@gmail.com,We are digital marketing experts. We offer services & plans to ...,Strategy & Planning SEO & Analytics Social Media Marketing Content Marketing ... thakurinnovation2058@gmail.com #DigitalMarketing #BrandGrowth ...,https://www.zillow.com/p/DT24GiFkdWe/,Zillow.com,marketing
AI Agent Access via MCP
MCP for the Zillow Email Scraper API
The same endpoint is available to AI agents through the Scrapier MCP server at https://mcp.scrapier.io/mcp. One command registers it in Claude Code: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY". The agent finds the endpoint with search_endpoints and calls it with run_scrape and the endpoint id social-media-platform-email. It takes the same keywords input and costs the same 1 credit per page of emails. Setup for every client is on the Zillow Email Scraper MCP page.
Integration Paths by Role
n8n and Make
- Add an HTTP Request step
- GET the endpoint with your
X-API-Keyheader - Map the
data.emailsfields to your columns
Loop and paginate
MCP tool in your agent
Call run_scrape with endpoint social-media-platform-email from Claude, Cursor or Windsurf. Setup is on the MCP page.
CSV and flattened JSON
Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.
Legal and Compliance Notes
Collecting email addresses that people have published on public pages is lawful in many places, but the answer depends on who the address belongs to, where you are and how you use it. Scrapier returns only what a public search shows, and many results are third-party addresses, so privacy law such as GDPR, CAN-SPAM and CASL applies to how you store and contact them. Collect only what you need and respect opt-outs. Consult legal counsel before bulk outreach. This is not legal advice; see our Terms of Use.
Frequently Asked Questions
Is there a Zillow page of emails API?
Yes. Scrapier's Zillow Email Scraper API returns any public page of emails as JSON with one GET request and an X-API-Key header. No Zillow app or login.
How do I call it from Python?
Use <code>requests.get</code> on <code>https://proxy.scrapier.io/api/v2/social-media-platform-email/</code> with <code>params={'keywords': 'marketing'}</code> and <code>headers={"X-API-Key": KEY}</code>. Read <code>r.json()["data"]["emails"]</code>.
What happens when a call fails?
Any non-200 response is free. Retry 429 and 5xx with backoff; the API already retries upstream failures.
How much does it cost?
1 credit per successful call — about $1.58 per 1,000 pages of emails on the Pro plan. Failed calls are free.
Is there an OpenAPI spec?
Yes. It needs no key and covers every Scrapier endpoint.
Fetch public Zillow pages of emails as typed JSON in one request
1 credit per page of emails · failed calls free