# Zillow Email Scraper: Public Emails as JSON | Scrapier (https://scrapier.io/scrapers/zillow/email/)

> Zillow Email Scraper: find public email addresses on Zillow pages by keyword, with title, description and URL as JSON. 1 credit per call. Get a free API key.

Last updated: 2026-11-12

**GET**/api/v2/social-media-platform-email/

## Zillow Email Scraper

Public email addresses found on Zillow pages for a keyword, as typed JSON: email, page title, description, URL and scrape time, with a cursor for the next page. 1 credit per call. No Zillow login, no proxies to manage.

[Get a free API key →](https://app.scrapier.io/sign-up) [View API docs](https://scrapier.io/scrapers/zillow/email/api/)

Free API key · 1 credit per page of emails · failed calls free

Last updated 9 Nov 2026

// GET /api/v2/social-media-platform-email/?keywords=marketing · sample from the catalog
{
  "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"
  }
}

Copy for your AI agent

Pricing

[1 credit / page of emails](https://scrapier.io/pricing/)

From $1.58 per 1,000 on Pro

Endpoint facts

Credits per call**1**

Pagination**cursor**

Zillow login**Not needed**

Format**JSON**

Auth

`X-API-Key: <your key>`

MCP tool

`run_scrape · social-media-platform-email`

One of six tools in the Scrapier MCP server, which reach all 199 endpoints.

Platform

[Zillow: 3 endpoints →](https://scrapier.io/scrapers/zillow/)

Quick answer

Zillow Email Scraper searches Google for public email addresses on zillow.com pages that match your keyword and returns the matches as JSON: `email`, `title`, `description`, `url` and `scraped_at`, with `next_cursor` for more. It costs 1 credit per successful call and needs no Zillow login.

Every request is fetched live at call time · failed calls are free

Zillow Email Scraper is a Zillow email extractor built on public search. For a keyword, it looks for pages on zillow.com that show an email address, and each call returns a page of matches with the email, the page title, the snippet text, the page URL and the time it was scraped. You can narrow the search by email domain and location. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or load into a lead sheet. It is one of 3 Zillow endpoints on the same API key used by 12,000+ developers. Next, page through the results.

## What data can I extract with Zillow Email Scraper?

Using this Zillow Email Scraper, you can extract the following data from public Zillow pages of emails:

Email address

Page title

Description snippet

Zillow page URL

Network (Zillow.com)

Keyword that matched

Scrape time

Result page number

Page size

Cursor for the next page

Keyword, echoed back

Network, echoed back

Want the exact field names? See the [example output](#output).

Playground

## Try Zillow Email Scraper Live

Press **Run** to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.

Zillow**Zillow Email Scraper**Live

Platform

Endpoint

Parameters

### \+ Run live with your API key

Response

Sample dataCatalog sample, run to see live data

## How to use Zillow Email Scraper

Hand it to your AI assistant, or run it yourself in five steps.

### Copy to your AI assistant

Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.

Use the Scrapier Zillow Email Scraper to get public Zillow pages of emails. Endpoint: GET https://proxy.scrapier.io/api/v2/social-media-platform-email/?keywords={keywords} with header "X-API-Key: YOUR\_API\_KEY" and a 210-second timeout. Send one value per call in keywords; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.emails: network, keyword, title, description, url, email, scraped\_at. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR\_API\_KEY" and call run\_scrape with endpoint "social-media-platform-email" (find it with search\_endpoints).

**Zillow Email Scraper MCP Server**

Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Zillow pages of emails on its own: no glue code, no scraping logic in your prompts.

[MCP setup →](https://scrapier.io/scrapers/zillow/email/mcp/)

### Run it yourself

1. **Get your free Scrapier API key**Sign up at [app.scrapier.io](https://app.scrapier.io/sign-up); the free tier lets you try it first.
2. **Open Zillow Email Scraper in the catalog**It lives under [Scrapers / Zillow](https://scrapier.io/scrapers/zillow/).
3. **Enter a keyword**Put one search keyword in `keywords`, such as `marketing`. Optionally set `email_domains` (for example `@gmail.com`), `location`, `country` and `language`.
4. **Send your API request**One GET with your key in the `X-API-Key` header, or one `run_scrape` call from your agent.
5. **Save your results**The matches come back as JSON in `data.emails`. Pass `data.next_cursor` back as `cursor` for the next page until it is null.

### How to scale to bulk Zillow pages of emails

`keywords` takes one keyword per call, and each call returns one page of matches, so for more results you loop: send the keyword, read `next_cursor`, send it back as `cursor` and stop when it is null. For several keywords, loop over them. Run up to 3 requests in parallel per API key; above that the API answers 429 with a `Retry-After` header, and throttled calls cost nothing. Each page is 1 credit and failed calls are free, so 1,000 pages cost 1,000 credits, inside the Hobby plan's 15,000.

## Features

Zillow Email Scraper turns a public web search into clean, structured rows at low cost. It suits lead research, outreach lists, contact enrichment and any workflow that needs email addresses people have published on Zillow pages.

It extracts, per page of emails

- **Email**the address itself, in `email`, one per result
- **Source page**`url`, `title` and `description` of the page it came from
- **Keyword**one keyword per call, echoed back in `keyword`
- **Filters**`email_domains`, `location`, `country` and `language`
- **Freshness**`scraped_at` shows when each result was collected
- **Paging**`next_cursor` walks the results page by page

Searching, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at **1 credit per page of emails** and **0 credits for a failed call**.

## Use cases

- **Lead generation team** searches Zillow pages for a niche keyword such as "marketing" and loads the emails, titles and URLs into a sheet for a human to review before any outreach.
- **Real estate marketer** builds a list of public business contacts that mention a city or service, using `location`, then checks each source `url` before reaching out.
- **Sales ops analyst** filters by `email_domains` to see which addresses are on company domains, and adds them to a CRM with the page URL as the source.
- **Data enrichment engineer** runs a keyword list on a schedule, deduplicates on `email` and keeps `scraped_at` so every contact has a collection date.
- **AI engineer** gives an outreach-research agent a tool that finds public contact emails for a topic, so the agent can draft a shortlist with sources attached.

Running these from an agent? Use the [MCP integration](https://scrapier.io/scrapers/zillow/email/mcp/) and let Claude or Cursor call the scraper directly.

## Why choose this Scraper API?

**Public pages only, with the source.**

Every result carries the Zillow page `url`, `title` and `description` it was found on, so you can see where an address was published and decide whether to use it.

**Filters that match how people search.**

Narrow results with `email_domains`, `location`, `country` and `language` instead of filtering thousands of rows yourself after the fact.

**One key, 3 Zillow endpoints.**

The same key and response envelope also reach Zillow search and property details, so a lead list and a property record come from one account and one integration.

## Input

The scraper takes one search keyword per call in `keywords` (default `marketing`). Everything else is optional: `email_domains` (default `@gmail.com`), `location`, `country`, `language` and `platform` (default Zillow). Send parameters in the query string (GET) or as a JSON body (POST). It finds addresses through public search, so results depend on what is indexed.

| Name | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `keywords` | string | Yes | — | Search keyword, one per call. Required on the first call. Default `marketing`. Aliases: `keyword`, `query`, `q` |
| `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 |
| `email_domains` | string | No | `@gmail.com` | Email domains to look for, comma-separated; empty means any. Default `@gmail.com`. Fixed by the cursor |
| `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 |
| `language` | string | No | `en` | Google language code (`hl`). Default `en`. Fixed by the cursor |
| `include_all_emails` | boolean | No | `false` | Boolean, default `false`. Fixed by the cursor |
| `use_proxy` | boolean | No | `true` | Route through Scrapier's residential proxy pool. On by default; leave as is |
| `raw_data` | boolean | No | `false` | Return the raw upstream payload under `raw_responses` instead of the formatted emails |

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.

### Example input

POST body · input.json

{
  "keywords": "marketing",
  "platform": "Zillow",
  "email\_domains": "@gmail.com",
  "location": "",
  "country": "us",
  "language": "en",
  "include\_all\_emails": "false",
  "use\_proxy": "true",
  "raw\_data": "false"
}

### Error codes

| 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](https://docs.scrapier.io/errors/). Any non-2xx response costs 0 credits.

## Output

Typed JSON with the same schema on every call. One call returns one page: an `emails` array with 7 fields per match, inside the standard `data` envelope with the keyword, the network, the page number and the cursor for the next page. Field names stay the same on every call, so code and agents read them directly.

### Example output

200 OK · 1 credit · catalog sample

{
  "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"
  }
}

The catalog's sample response for `keywords=marketing`, labelled as a sample: live calls return the account's current values.

### Email and source page

| 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 |

### Search context and timing

| Field | Type | Example | Description |
| --- | --- | --- | --- |
| `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 |

### Response envelope and paging

| Field | Type | Example | Description |
| --- | --- | --- | --- |
| `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 |

## How does it work?

01

Scrapier sends each request through its residential proxy pool (`use_proxy`, on by default), so you never manage IPs or proxy accounts.

02

Retries and parsing happen on Scrapier's side. The endpoint searches Google for pages on zillow.com that show an email matching your `email_domains` and keyword, then returns the matches as typed JSON.

03

Only publicly visible data is returned: addresses already published on pages Google shows. No Zillow account or cookie is used, and no private account data is read.

04

The schema is stable. The field names in `data.emails` stay the same from call to call.

## How do you integrate Zillow Email Scraper into your stack?

It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the [API tab](https://scrapier.io/scrapers/zillow/email/api/).

### MCP integration for AI agents

claude mcp add -t http scrapier …

This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including `social-media-platform-email`: the agent finds it with `search_endpoints` and calls it with `run_scrape`. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. [Full MCP setup →](https://scrapier.io/scrapers/zillow/email/mcp/)

### No-code tools (n8n, Make, LangChain)

**n8n**

Use the HTTP Request node with your Scrapier API key in an `X-API-Key` header and point it at `/api/v2/social-media-platform-email/` with a `keywords` query parameter. Map `data.emails` into the next node and loop on `data.next_cursor`.

**Make**

Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map `email` and `url` straight into Sheets or your CRM.

**LangChain**

Wrap the endpoint in a `requests`\-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds `social-media-platform-email` with `search_endpoints` itself.

## Pricing and Rate Limits

One Zillow page of emails costs 1 credit, so 1,000 pages of emails cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a `Retry-After` header.

| Plan | Monthly price | Credits | Pages of emails included | Per 1,000 pages of emails |
| --- | --- | --- | --- | --- |
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | [Custom volume and terms](https://scrapier.io/enterprise/#contact) |

Prices from the live billing page. [See all plans and limits](https://scrapier.io/pricing/).

## Call cost and timing

**1**credit per successful call

**0**credits for a failed call

**3**parallel requests per key

**210s**recommended client timeout

### How we measure this

Credit cost, pagination and the sample come from the live catalog (`GET /api/v2/endpoints`, /social-media-platform-email/, checked 9 Nov 2026). Concurrency and timeout guidance come from the [rate limits page](https://docs.scrapier.io/rate-limits/) of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.

## Zillow Email Scraper vs the Official Zillow API

| 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 |

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.

## Is it legal to scrape Zillow data?

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](https://scrapier.io/terms/).

## Frequently asked questions

### What does Zillow Email Scraper return?

The top five fields are email, title, description, url and scraped\_at, plus network and keyword: 7 fields per match in data.emails, with page, page\_size and next\_cursor in the envelope. Each successful call costs 1 credit and needs no Zillow login.

### How does Zillow Email Scraper find emails?

It searches Google for pages on zillow.com that show an email address matching your keyword and email domain, then returns what the search shows. It does not read Zillow accounts or private data, and results depend on what Google has indexed.

### Does it need a Zillow account or login?

No. The endpoint uses no Zillow account or cookies: you send your Scrapier API key in the X-API-Key header and a keyword, and get JSON back. Only publicly visible search results are returned.

### Whose emails will I get?

Addresses that appear on public Zillow pages, such as agent or business profiles and posts. Many belong to third parties who published them. Check the url field to see the source page, and treat each address as personal data.

### How do I get more than one page of emails?

Each call returns one page. Read next\_cursor from the response, send it back unchanged as cursor with the same keyword, and repeat until next\_cursor is null. Every page is a separate call at 1 credit.

### Can I filter by email domain or location?

Yes. Set email\_domains to a domain such as @gmail.com, and add location, country or language to narrow the search. These options are locked in the cursor, so keep them the same while you page through results.

### Can I scrape multiple keywords at once?

Yes, with one call per keyword: keywords takes a single value. Loop over your list and run up to 3 requests in parallel per API key. 1,000 pages cost 1,000 credits; failed and throttled calls are free.

### Does it work with Claude, ChatGPT and other AI agent tools?

Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header. The agent finds the endpoint with search\_endpoints and calls it with run\_scrape. Any agent that can call HTTP can use the REST API directly.

### Is there a free Zillow email scraper?

Scrapier has a free tier to try the API, then each successful call is 1 credit and failed calls cost nothing. Plans are Hobby $29 for 15,000 credits, Pro $79 for 50,000 and Scale $299 for 250,000.

### Does it return data in a format LLMs can use directly?

Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.

### How much does it cost to scrape 1,000 pages of emails?

1,000 credits, because each page of emails is one call at 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.

### How do I scrape Zillow emails with Python?

Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/social-media-platform-email/ with params={"keywords": "marketing"}, your key in the X-API-Key header and timeout=210. Read r.json()\["data"\]\["emails"\]: it is already JSON, so no HTML parsing is needed.

### Is it legal to scrape Zillow emails?

It depends on whose address it is, your country and your use, so this is not legal advice. Scrapier returns public search results only. Privacy and marketing laws such as GDPR and CAN-SPAM apply to how you store and contact people. Ask a lawyer about your case.

## Related scrapers

| Scraper | What it extracts |
| --- | --- |
| [Search Scraper](https://scrapier.io/scrapers/zillow/search/) | Homes from a Zillow search URL, a page at a time: address, price, beds, baths, living area and status. |
| [Property Detail Scraper](https://scrapier.io/scrapers/zillow/property/) | One property by Zillow URL or street address: price, home type and status, beds, baths and zpid. |

All 3 Zillow endpoints are on the [Zillow scraper hub](https://scrapier.io/scrapers/zillow/).

## Your feedback

Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.

[Report an issue](https://scrapier.io/contact/)[Email support](mailto:support@scrapier.io)

Get started

## Start Scraping Zillow Pages Of Emails

Public Zillow pages of emails as JSON, 1 credit each, from REST or MCP.

[Get a free API key →](https://app.scrapier.io/sign-up)[View pricing](https://scrapier.io/pricing/)

---
Canonical page: https://scrapier.io/scrapers/zillow/email/
Site index for AI agents: https://scrapier.io/llms.txt
