# Zillow Rentals Email Scraper (`leads-scraper/zillow-rentals-email-scraper`) Actor

Zillow Rentals Email Scraper SD - Zillow Rentals Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Zillow results by keyword, location and email domain - Zillow email extractor.

- **URL**: https://apify.com/leads-scraper/zillow-rentals-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Zillow Rentals Email Scraper - rental contact extraction from a mixed-inventory portal

The Zillow Rentals Email Scraper pulls publicly indexed rental contact emails out of Google's index of Zillow and writes them to an Apify dataset. It targets proptech vendors, multifamily marketing agencies and suppliers selling into rental housing.

Two honest facts up front. Zillow indexes individual home detail pages far more than manager profiles, so most rows carry an email without a resolvable handle.

And in a measured run against live Google, roughly ten parsed result blocks produced seven unique emails but only three identities and three resolvable profile URLs. Email yield is solid; identity coverage is thin.

The second thing to understand is the rental narrowing, because zillow.com carries for-sale inventory, agent pages and rentals in a single index.

If your workflow needs named accounts, run the Zillow Rentals Email Scraper for reach and add the [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) or the [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) for structure.

#### Why the Zillow Rentals Email Scraper adds an `inurl:` filter

A plain `site:zillow.com` query would return mostly for-sale content. To bias toward rentals, the Zillow Rentals Email Scraper appends `inurl:apartments` to every query it builds.

A typical query therefore looks like `site:zillow.com property manager inurl:apartments "@gmail.com" "Houston"`. The fragment is applied consistently across every query variant, not just the base query.

Be clear about the limits. This is a heuristic URL filter that strongly biases the result set toward rental pages; it is not a guarantee that every returned page is a rental page.

Some pages whose URL contains `apartments` will not be the rental listing you expected, and some genuine rental pages will be excluded because their URLs are shaped differently. Spot-check `url` and `title` before a large send.

#### Who the Zillow Rentals Email Scraper is for

Property management software vendors, leasing and tour-scheduling tools, tenant screening providers, and smart-lock or IoT installers all sell to the person whose address is published on the listing.

Renovation and turn suppliers, landscaping firms and maintenance contractors use the Zillow Rentals Email Scraper to build a metro-level territory list. Insurance brokers selling landlord and rental property policies work the same rows.

Landlords and leasing offices publish these addresses on purpose because they want inbound enquiries. That makes this a B2B contact list rather than a consumer harvest.

### What the Zillow Rentals Email Scraper actually does

The Zillow Rentals Email Scraper is a Google search-results parser with a domain-filtered email extractor attached. It never touches Zillow directly.

1. Reads your input: keywords, location, email domains and limits.
2. Builds Google queries with the `site:` operator against `zillow.com`, plus the `inurl:apartments` narrowing operator described above.
3. Fetches Google result pages through the Apify GOOGLE_SERP proxy using async `aiohttp` requests.
4. Parses each result block structurally by locating the `<h3>` title and then the smallest surrounding block, rather than depending on Google's CSS class names.
5. Extracts emails from the block text with a domain-filtered regular expression.
6. Deduplicates globally and pushes every lead to the Apify dataset immediately.

It does not log into Zillow, does not use any Zillow API, and does not open the Zillow website. There is no browser, no JavaScript rendering, no authentication and no cookies.

Everything the Zillow Rentals Email Scraper returns comes from publicly indexed Google search results: titles, snippets and site labels. If an address is not in that index, the Zillow Rentals Email Scraper cannot find it.

### Key features of the Zillow Rentals Email Scraper

| Feature | What it means in practice |
|---|---|
| Rental narrowing | An `inurl:apartments` operator on every query, biasing a mixed sale-and-rental domain toward rental pages. |
| Query expansion | Base, quoted, `intitle:` and one variant per query modifier. Base queries run first. |
| Global deduplication | Every email is emitted once across all queries and all pages of the run. |
| Email normalisation | Case-insensitive; understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` sign. |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals. |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br`. |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same result block. |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails`. |
| Retries | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request. |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty. |
| Re-queue | Blocked or failed queries are retried once at the end of the run. |
| Resumable state | Saved in the key-value store keyed by an input hash; throttled saves plus `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. |
| Fallback parser | If Google's markup changes, the whole-page parser degrades to "emails without account details" instead of "no emails". |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page. |

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, subject to what Google has indexed for the Zillow Rentals Email Scraper's query set.

### How the Zillow Rentals Email Scraper builds its queries

Query expansion exists because Google caps a single query at roughly 300 results. The `inurl:` filter narrows the pool further, so expansion matters more here than on a rentals-only domain.

With `expandQueries` on, each keyword and email-domain pair is searched in several phrasings. The Zillow Rentals Email Scraper runs the base query first, then the quoted variant, then an `intitle:` variant, then one variant per entry in `queryModifiers`.

The default modifiers are `email`, `contact`, `leasing office`, `inquiries` and `property manager` - the words that appear next to a published address on a rental page.

Leave expansion on. Because Zillow's indexed rental pages are mostly individual home detail pages rather than account pages, breadth is what makes the Zillow Rentals Email Scraper produce a usable list.

The `query` field is worth keeping in your export, since it records the exact `inurl:` fragment behind each row and makes the narrowing auditable.

### Input settings for the Zillow Rentals Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["property manager", "apartments for rent"]` | Search terms describing the accounts you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional |
| `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email", "contact", "leasing office", "inquiries", "property manager"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1-20 | `5` | Parallel queries |

#### Location targeting in the Zillow Rentals Email Scraper

`location` is the highest-leverage input in the schema, and it is doing extra work here because the `inurl:` filter has already shrunk the candidate pool.

Start at metro level rather than neighbourhood level: `Houston TX`, `Detroit MI`, `Cleveland OH`, `Memphis TN`, `Oklahoma City OK`. Zillow's rental depth in large single-family rental markets is genuinely useful.

Move to a submarket only after a metro run shows healthy volume: `The Heights Houston`, `Corktown Detroit`, `Ohio City Cleveland`, `Midtown Memphis`. Narrowing too early is the most common cause of an empty run on this Actor.

Run one location per run. The value is appended verbatim to every query, so `Houston OR Dallas` becomes a literal phrase and typically returns less rather than more.

Set `countryCode: "US"` so the proxy resolves from a US exit, and add the state abbreviation for ambiguous names - `Columbus OH` and `Columbus GA` are separate rental markets.

If a location comes back thin, widen one step at a time and raise `maxPagesPerQuery` before concluding the Zillow Rentals Email Scraper is misconfigured.

#### Choosing keywords and email domains

Because the indexed pages skew toward individual homes, landlord-shaped keywords work as well as manager-shaped ones. Try `landlord`, `property manager`, `apartments for rent`, `leasing office` and `management company`.

`customDomains` drives volume more than any other field. Free-mail domains are the default because individual landlords genuinely publish `@gmail.com` and `@yahoo.com` addresses on rental listings.

Add `@outlook.com` and `@hotmail.com` when a run looks thin. The Zillow Rentals Email Scraper keeps only addresses ending in a domain you listed.

### Output data from the Zillow Rentals Email Scraper

Every dataset item produced by the Zillow Rentals Email Scraper carries all fourteen fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for listing-style titles |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, for example `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

When a handle exists the profile URL follows the shape `https://www.zillow.com/{username}`. Only about three in ten parsed results carried one in testing, so build your pipeline around `email`, `accountName` and `description`.

### Example runs with the Zillow Rentals Email Scraper

A metro run for an insurance broker prospecting Houston landlords:

```json
{
  "keywords": ["landlord", "property manager"],
  "location": "Houston TX",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 200,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "leasing office", "inquiries", "property manager"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Two dataset rows, honestly reflecting the handle gap described above:

```json
[
  {
    "network": "Zillow",
    "keyword": "landlord",
    "query": "site:zillow.com landlord inurl:apartments \"@gmail.com\" \"Houston TX\"",
    "title": "Apartments for Rent in The Heights, Houston, TX | Zillow",
    "accountName": "Heights Rentals",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Landlord contact: heightsrentalshou@gmail.com. Units listed monthly.",
    "email": "heightsrentalshou@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T17:04:52Z"
  },
  {
    "network": "Zillow",
    "keyword": "property manager",
    "query": "site:zillow.com property manager inurl:apartments contact \"@yahoo.com\" \"Houston TX\"",
    "title": "Westheimer Court Apartments - Houston, TX | Zillow",
    "accountName": "Westheimer Court Apartments",
    "fullName": "Westheimer Court Apartments",
    "username": "westheimer-court-houston-tx",
    "profileUrl": "https://www.zillow.com/westheimer-court-houston-tx",
    "url": "https://www.zillow.com/westheimer-court-houston-tx",
    "description": "Property manager on site. Leasing enquiries: westheimercourt@yahoo.com",
    "email": "westheimercourt@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T17:09:30Z"
  }
]
```

The first row is the common case on this platform, the second the exception. Expect the Zillow Rentals Email Scraper to return roughly seven rows like the first for every three like the second.

For a broader sweep, move `location` to a state and raise `maxEmails`. Leave `maxConcurrency` at 5 unless you have a reason to change it; the Zillow Rentals Email Scraper already runs its queries in parallel.

### Use cases for the Zillow Rentals Email Scraper

| Audience | How they use the Zillow Rentals Email Scraper |
|---|---|
| Property management software vendors | Reach small operators and single-family rental owners in a metro |
| Leasing and tour-scheduling tools | Target listings that already publish an address and field enquiries by email |
| Tenant screening providers | Reach independent landlords who screen manually or not at all |
| Smart-lock and IoT installers | Prospect scattered-site rental portfolios across a metro |
| Renovation and turn suppliers | Build a make-ready, flooring and appliance outreach list |
| Maintenance and landscaping contractors | Assemble a territory list for scattered rental properties |
| Multifamily marketing agencies | Identify under-marketed rentals worth a creative or paid media pitch |
| Insurance brokers | Reach landlords and small owners for landlord and rental property policies |
| Market researchers | Study how rental contact publishing differs on a sale-dominant portal |

### Responsible use, GDPR, CAN-SPAM and Fair Housing

Everything the Zillow Rentals Email Scraper collects is already published on public pages and indexed by Google. That does not shift your obligations as the sender onto anyone else.

Under GDPR and similar regimes, have a lawful basis for processing business contact data, honour deletion and objection requests, and say in your first message where you found the address. Under CAN-SPAM, use accurate headers and subject lines, disclose your identity and postal address, and honour opt-outs promptly.

Fair Housing is genuinely relevant to US rental outreach, and worth extra care on a platform where many contacts are individual landlords. Keep messaging focused on your product and avoid anything that could read as steering or as encouraging discrimination based on a protected characteristic.

None of this is legal advice. Check your campaign against your own jurisdiction's rules, and verify addresses before you send at volume. The Zillow Rentals Email Scraper surfaces candidates; the sending decision stays with you.

### Limitations of the Zillow Rentals Email Scraper

- **Handle resolution is weak here.** Zillow indexes individual home detail pages far more than manager profiles, so most rows carry an email without a resolvable handle. Only about three in ten parsed results returned a `username` and `profileUrl` in testing.
- **The rental narrowing is a heuristic.** `inurl:apartments` biases results toward rental pages on a mixed sale-and-rental domain, but it does not guarantee every returned page is a rental page, and it may exclude rental pages whose URLs are shaped differently.
- It only finds contacts whose email is publicly visible in Google's index. Addresses behind a contact form or rendered in an image will not be found.
- Google caps a single query at roughly 300 results. Query expansion works around that ceiling; the `inurl:` filter narrows the pool further.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the email. Verify those rows before sending.
- The Apify GOOGLE_SERP proxy is required. The Zillow Rentals Email Scraper cannot run without Apify proxy credentials.
- Free Apify plans stop at 100 emails per run; paid plans are uncapped.
- Results vary with keywords, domains and location. No volume is guaranteed, and the Zillow Rentals Email Scraper is not affiliated with or endorsed by Zillow.

### Zillow Rentals Email Scraper FAQ

#### How many results should I expect from the Zillow Rentals Email Scraper?

In a measured run against live Google, roughly ten parsed result blocks produced seven unique emails but only three identities and three profile URLs. Plan for good email volume and thin identity data. Counts vary with location, keywords and domain filter.

#### Why is `username` null on most rows?

Because Zillow indexes individual home detail pages far more than manager profiles, so most rows carry an email without a resolvable handle. Google shows a listing title rather than an account handle.

#### Why does every query contain `inurl:apartments`?

Because zillow.com carries for-sale listings, agent pages and rentals in one index. The fragment biases the result set toward rental pages. It is a heuristic filter, not a guarantee.

#### Could a non-rental page still slip through?

Yes, and some genuine rental pages will be missed. Spot-check `url` and `title` before a large send.

#### Does the Zillow Rentals Email Scraper log into Zillow?

No. It reads Google search results through the Apify GOOGLE_SERP proxy. No login, no API key, no browser, no cookies.

#### Which input matters most?

`location`. Because the `inurl:` filter has already narrowed the pool, starting at metro level rather than neighbourhood level protects your yield in the Zillow Rentals Email Scraper.

#### Can I target corporate domains instead of free-mail?

Yes. Replace `customDomains` with the domains you want; only addresses ending in one of them are kept.

#### What does `possiblyTruncated` mean?

Google cut the snippet near the email, so the address may be incomplete. Filter or verify those rows before a send.

#### Can I run the Zillow Rentals Email Scraper outside Apify?

No. The GOOGLE_SERP proxy is a required dependency and needs Apify proxy credentials.

#### Will I get duplicate addresses?

No. Deduplication is global across every query and page, so each unique email appears once per run.

#### Is 100 emails a hard cap?

Only on free plans. Paid plans are uncapped, though the practical ceiling is whatever Google has indexed under the `inurl:` filter.

#### Which sibling Actors should I add for account-shaped rows?

[ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) and [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) resolved a handle for every parsed result in the same test, which complements the Zillow Rentals Email Scraper well.

### Related Actors

| Actor | What it collects |
|---|---|
| [Apartment List Email Scraper](https://apify.com/leads-scraper/apartment-list-email-scraper) | Public contact emails from Apartment List |
| [ApartmentFinder Email Scraper](https://apify.com/leads-scraper/apartmentfinder-email-scraper) | Public contact emails from ApartmentFinder |
| [Apartments.com Email Scraper](https://apify.com/leads-scraper/apartments-com-email-scraper) | Public contact emails from Apartments.com |
| [Century 21 Agent Email Scraper](https://apify.com/neuro-scraper/century-21-agent-email-scraper) | Public contact emails from Century 21 |
| [Coldwell Banker Agent Email Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-scraper) | Public contact emails from Coldwell Banker |
| [CommercialCafe Email Scraper](https://apify.com/neuro-scraper/commercialcafe-email-scraper) | Public contact emails from CommercialCafe |
| [CommercialSearch Email Scraper](https://apify.com/neuro-scraper/commercialsearch-email-scraper) | Public contact emails from CommercialSearch |
| [Compass Agent Email Scraper](https://apify.com/neuro-scraper/compass-agent-email-scraper) | Public contact emails from Compass |
| [Crexi Email Scraper](https://apify.com/leads-scraper/crexi-email-scraper) | Public contact emails from Crexi |
| [Domain Agents Email Scraper](https://apify.com/leads-scraper/domain-agents-email-scraper) | Public contact emails from Domain |
| [Homes & Land Email Scraper](https://apify.com/neuro-scraper/homes-and-land-email-scraper) | Public contact emails from Homes & Land |
| [Homes.com Email Scraper](https://apify.com/leads-scraper/homes-com-email-scraper) | Public contact emails from Homes.com |
| [HotPads Email Scraper](https://apify.com/leads-scraper/hotpads-email-scraper) | Public contact emails from HotPads |
| [Keller Williams Agent Email Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-scraper) | Public contact emails from Keller Williams |
| [Land And Farm Email Scraper](https://apify.com/leads-scraper/land-and-farm-email-scraper) | Public contact emails from Land And Farm |
| [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) | Public contact emails from Land.com |
| [LandWatch Email Scraper](https://apify.com/leads-scraper/landwatch-email-scraper) | Public contact emails from LandWatch |
| [LoopNet Email Scraper](https://apify.com/leads-scraper/loopnet-email-scraper) | Public contact emails from LoopNet |
| [OnTheMarket Email Scraper](https://apify.com/leads-scraper/onthemarket-email-scraper) | Public contact emails from OnTheMarket |
| [RealEstate.com.au Agents Email Scraper](https://apify.com/neuro-scraper/realestate-com-au-agents-email-scraper) | Public contact emails from realestate.com.au |
| [Realtor.ca Email Scraper](https://apify.com/leads-scraper/realtor-ca-email-scraper) | Public contact emails from Realtor.ca |
| [Realtor.com Rentals Email Scraper](https://apify.com/leads-scraper/realtor-com-rentals-email-scraper) | Public contact emails from Realtor.com |
| [Redfin Rentals Email Scraper](https://apify.com/leads-scraper/redfin-rentals-email-scraper) | Public contact emails from Redfin |
| [RE/MAX Agent Email Scraper](https://apify.com/leads-scraper/remax-agent-email-scraper) | Public contact emails from RE/MAX |
| [Rent.com Email Scraper](https://apify.com/leads-scraper/rent-com-email-scraper) | Public contact emails from Rent.com |
| [RentCafe Email Scraper](https://apify.com/leads-scraper/rentcafe-email-scraper) | Public contact emails from RentCafe |
| [Zumper Email Scraper](https://apify.com/leads-scraper/zumper-email-scraper) | Public contact emails from Zumper |
| [Apartment List Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartment-list-email-and-phone-number-scraper) | Emails and phone numbers from Apartment List |
| [ApartmentFinder Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartmentfinder-email-and-phone-number-scraper) | Emails and phone numbers from ApartmentFinder |
| [Apartments.com Email and Phone Number Scraper](https://apify.com/neuro-scraper/apartments-com-email-and-phone-number-scraper) | Emails and phone numbers from Apartments.com |
| [Century 21 Email and Phone Number Scraper](https://apify.com/neuro-scraper/century-21-agent-email-and-phone-number-scraper) | Emails and phone numbers from Century 21 |
| [Coldwell Banker Email and Phone Number Scraper](https://apify.com/neuro-scraper/coldwell-banker-agent-email-and-phone-number-scraper) | Emails and phone numbers from Coldwell Banker |
| [CommercialCafe Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialcafe-email-and-phone-number-scraper) | Emails and phone numbers from CommercialCafe |
| [CommercialSearch Email and Phone Number Scraper](https://apify.com/neuro-scraper/commercialsearch-email-and-phone-number-scraper) | Emails and phone numbers from CommercialSearch |
| [Compass Email and Phone Number Scraper](https://apify.com/neuro-scraper/compass-agent-email-and-phone-number-scraper) | Emails and phone numbers from Compass |
| [Crexi Email and Phone Number Scraper](https://apify.com/leads-scraper/crexi-email-and-phone-number-scraper) | Emails and phone numbers from Crexi |
| [Domain Email and Phone Number Scraper](https://apify.com/leads-scraper/domain-agents-email-and-phone-number-scraper) | Emails and phone numbers from Domain |
| [Homes & Land Email and Phone Number Scraper](https://apify.com/neuro-scraper/homes-and-land-email-and-phone-number-scraper) | Emails and phone numbers from Homes & Land |
| [Homes.com Email and Phone Number Scraper](https://apify.com/leads-scraper/homes-com-email-and-phone-number-scraper) | Emails and phone numbers from Homes.com |
| [Keller Williams Email and Phone Number Scraper](https://apify.com/neuro-scraper/keller-williams-agent-email-and-phone-number-scraper) | Emails and phone numbers from Keller Williams |
| [Land And Farm Email and Phone Number Scraper](https://apify.com/neuro-scraper/land-and-farm-email-and-phone-number-scraper) | Emails and phone numbers from Land And Farm |
| [Land.com Email and Phone Number Scraper](https://apify.com/leads-scraper/land-com-email-and-phone-number-scraper) | Emails and phone numbers from Land.com |

### Leave a review

If the Zillow Rentals Email Scraper saved you time, please leave a star rating and a short
review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, a bug report, or a custom build request for the Zillow Rentals Email Scraper? Contact **neurodata.apify@gmail.com**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Zillow accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Zillow.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "property manager",
    "apartments for rent"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "leasing office",
    "inquiries",
    "property manager"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Zillow Rentals Email Scraper, stored in the run's default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "property manager",
        "apartments for rent"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "leasing office",
        "inquiries",
        "property manager"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/zillow-rentals-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "property manager",
        "apartments for rent",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "leasing office",
        "inquiries",
        "property manager",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/zillow-rentals-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "property manager",
    "apartments for rent"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "leasing office",
    "inquiries",
    "property manager"
  ]
}' |
apify call leads-scraper/zillow-rentals-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/zillow-rentals-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/IdfsPufRF9ZXVXeaj/builds/FmtpXAxSCDZgb7apB/openapi.json