# Land And Farm Email Scraper (`leads-scraper/land-and-farm-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/land-and-farm-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

### Land And Farm Email Scraper for farm and acreage broker emails

The Land And Farm Email Scraper collects publicly indexed contact emails belonging to the farm, ranch and acreage brokers whose listings appear on landandfarm.com.
Supply keywords, an optional location and the email domains you want to keep, and it returns a deduplicated dataset of land broker leads.
Every field comes from Google's public index; nothing is fetched from the platform itself.

**Yield note, stated plainly: Land And Farm indexes land listings rather than broker profiles, so rows usually carry a broker email without a resolvable profile URL.**
In a measured live run, roughly 10 parsed result blocks produced 9 identified broker records, only 1 resolvable profile URL and 9 unique emails.
Read that carefully, because it is a genuinely unusual shape: the email yield is close to the best in this category while the URL yield is close to the worst.

Land And Farm is an aggregator. It pulls farm, ranch and acreage inventory from a very wide set of independent rural brokerages into one national listing surface.
That aggregation is exactly why the Land And Farm Email Scraper finds so many distinct broker addresses: you reach small brokerages that never build a searchable profile page anywhere.
Those brokers publish their addresses on purpose, because a 240-acre pasture tract sells to whoever can actually reach the listing agent.

#### Understanding the identity versus URL split

Nine identified records and nine emails against one profile URL is the number that defines the Land And Farm Email Scraper.
The indexed pages here are aggregated property listings, and a listing title names the broker or brokerage without exposing a URL-safe handle.
So the Land And Farm Email Scraper reads a name from the title and an address from the block, but has nothing to construct a canonical profile URL from.

The good news is that the two fields you need for outreach, name and email, are present on most rows.
What you lose is the ability to click through and research the broker before writing to them.
If a clickable profile is essential to your workflow, the [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) resolves handles on almost every row instead.

This is a Google indexing outcome rather than a defect.
No input change will manufacture a handle that Google never printed, so plan on enriching by name and brokerage.

#### What the Land And Farm Email Scraper actually does

The Land And Farm Email Scraper builds Google queries with the `site:` operator against `landandfarm.com`, fetches result pages through the Apify GOOGLE_SERP proxy with `aiohttp`, and parses each block structurally.
It locates the `<h3>` title, walks up to the smallest surrounding block, then runs a domain-filtered regular expression over that block's text.
Structural parsing means it never depends on Google's CSS class names, so a markup change degrades a run instead of ending it.

It does not log into Land And Farm, never uses a Land And Farm API and never opens landandfarm.com in a browser.
There is no JavaScript rendering, no authentication and no cookies in the pipeline.

### Key features of the Land And Farm Email Scraper

Everything below ships with the Actor today; none of it is a roadmap item.

| Feature | What it does on an aggregated land listing source |
|---|---|
| Query expansion | Each keyword x domain pair runs as a base query, a quoted query, an `intitle:` query and one variant per modifier, base queries first. |
| Global deduplication | Essential here: an aggregator repeats the same brokerage across hundreds of tracts, and each address is written once. |
| Email normalisation | Handles `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 local parts. |
| 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 control | An `asyncio` worker pool with a shared stop signal on `maxEmails`. |
| Retries and block detection | Three attempts per page with exponential backoff, a fresh proxy session per request, and CAPTCHA or consent pages retried rather than counted as empty. |
| Failed-query requeue | Blocked or failed queries are retried once at the end of the run. |
| Resumable state | Key-value store state keyed by an input hash, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING`. |
| Whole-page fallback parser | A Google layout change degrades to emails without account details rather than to zero results. |
| Run summary | Pages fetched, blocked pages, retries and emails per page are logged. |

Deduplication carries more weight in the Land And Farm Email Scraper than anywhere else in this family.
A single regional brokerage may appear on hundreds of syndicated tracts, and without global deduplication it would dominate your dataset.

### How the Land And Farm Email Scraper works

A Land And Farm Email Scraper run begins by reading your input and hashing it into a resumable state key.
The query set is built by multiplying keywords by email domains and, when `expandQueries` is on, by every query modifier.
A representative query looks like `site:landandfarm.com "farm for sale" contact "@gmail.com" "Missouri"`.

The Land And Farm Email Scraper fetches result pages concurrently through the Apify GOOGLE_SERP proxy and parses them block by block.
Emails are extracted, normalised, domain-filtered and deduplicated globally before each lead is pushed to the dataset immediately.
Runs stop as soon as `maxEmails` unique addresses have been collected, with the stop signal shared across all workers.

Because email yield here is high, raise `maxEmails` above the default of 20 or a run will end almost as soon as it starts.
Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

### Land And Farm Email Scraper input fields

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["land broker", "farm for sale"]` | 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","listing agent","inquiries","broker"]` | 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 |

Only `keywords` is required, so the Land And Farm Email Scraper runs on defaults out of the box.
Because the index is listing-driven, land-use terms such as `"pasture"`, `"cropland"` and `"acreage for sale"` outperform agent-directory phrasing.

#### Location targeting in the Land And Farm Email Scraper

`location` is the most valuable input in this Actor, and on an aggregator it behaves differently again from a broker-profile platform.
Land And Farm organises inventory into state and county landing pages, so those phrases align with the grain of what Google has indexed.
Running the Land And Farm Email Scraper once per state or county gives markedly better relevance than one national sweep.

State phrases are the primary tool here, because the aggregator's own structure is state-first: `"Missouri"`, `"Kentucky"`, `"Oklahoma"`, `"Virginia"`, `"Tennessee"`.
Farm-belt and Southeastern states carry the deepest inventory, and land licensing, water rights and property tax rules are all state-level anyway.
Pair a state-level `location` with `countryCode: "US"` so the search proxy resolves to the right index.

County phrases are the precision tool and match how rural listing titles are written: `"Callaway County"`, `"Barren County"`, `"Bedford County"`.
Use them when you are sizing one territory rather than building broad coverage, and expect fewer but sharper rows.

Named farming regions work as a third option: `"Bluegrass"`, `"Ozarks"`, `"Shenandoah Valley"`, `"Piedmont"`.
Avoid metro names entirely on this Actor; a query for `"Kansas City"` will mostly miss the acreage inventory that makes this source useful.

#### Example input JSON

```json
{
  "keywords": ["farm for sale", "acreage for sale", "land broker"],
  "location": "Missouri",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com", "@hotmail.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "listing agent", "inquiries", "broker"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

### Land And Farm Email Scraper output fields

Every dataset item written by the Land And Farm 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 non-profile results |
| `username` | URL-safe handle when Land And Farm 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 |

Expect `username: null` and an empty `profileUrl` on the large majority of rows, alongside a usable `email` and `fullName`.
The example shows two typical listing rows and one of the rarer resolved-handle rows, rather than pretending the split does not exist.

#### Example output JSON

```json
[
  {
    "network": "Land And Farm",
    "keyword": "farm for sale",
    "query": "site:landandfarm.com \"farm for sale\" contact \"@gmail.com\" \"Missouri\"",
    "title": "240 Acres Pasture and Cropland, Callaway County MO - Delphine Brackett | Land And Farm",
    "accountName": "Delphine Brackett",
    "fullName": "Delphine Brackett",
    "username": null,
    "profileUrl": "",
    "url": "https://www.landandfarm.com/property/240_Acres_Callaway_County-1184722",
    "description": "240 acres mixed pasture and cropland with pond and barn. Showings: delphine.brackett.land@gmail.com",
    "email": "delphine.brackett.land@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-18T15:11:29Z"
  },
  {
    "network": "Land And Farm",
    "keyword": "acreage for sale",
    "query": "site:landandfarm.com \"acreage for sale\" broker \"@yahoo.com\" \"Missouri\"",
    "title": "78 Acres Recreational Acreage, Osage County MO | Land And Farm",
    "accountName": "Heartland Acreage Realty",
    "fullName": "Sutton Vaillancourt",
    "username": null,
    "profileUrl": "",
    "url": "https://www.landandfarm.com/property/78_Acres_Osage_County-1177310",
    "description": "78 wooded acres with creek frontage and food plots. Enquiries to sutton.vaillancourt.acres@yahoo.com",
    "email": "sutton.vaillancourt.acres@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-03-18T15:12:04Z"
  },
  {
    "network": "Land And Farm",
    "keyword": "land broker",
    "query": "site:landandfarm.com intitle:\"land broker\" \"@gmail.com\" \"Missouri\"",
    "title": "Orrin Falkenrath - Land Broker | Land And Farm",
    "accountName": "Orrin Falkenrath",
    "fullName": "Orrin Falkenrath",
    "username": "orrin-falkenrath",
    "profileUrl": "https://www.landandfarm.com/orrin-falkenrath",
    "url": "https://www.landandfarm.com/orrin-falkenrath",
    "description": "Farm, timber and recreational tracts across central Missouri. Contact orrin.falkenrath.farms@gmail.com",
    "email": "orrin.falkenrath.farms@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-18T15:13:41Z"
  }
]
```

### Use cases for the Land And Farm Email Scraper

| Audience | How they use the Land And Farm Email Scraper |
|---|---|
| Agricultural and farm credit lenders | Reach the long tail of independent brokers whose buyers need acreage and farm financing. |
| Rural insurance brokers | Target agents whose clients need farm, ranch, crop and outbuilding cover. |
| Land surveyors | Prospect brokers in counties where boundary, plat and split-parcel work is routine. |
| Timber and mineral buyers | Find brokers listing wooded tracts and parcels with severed mineral rights. |
| Hunting-lease and recreational operators | Reach brokers marketing food plots, creek frontage and deer-lease acreage. |
| Rural appraisal firms | Find brokers who commission acreage and agricultural valuations. |
| Title and closing firms | Build state-level lists of the brokers routing rural closings. |
| Fencing, pond and land-improvement contractors | Reach brokers whose listings mention wells, ponds, fencing and access work. |

The Land And Farm Email Scraper is a top-of-funnel sourcing step, not a whole go-to-market motion.
Its particular strength is reaching small independent brokerages that larger, profile-driven platforms simply do not index.

### Land And Farm Email Scraper examples

A rural insurance brokerage building a Missouri book runs the Land And Farm Email Scraper with `keywords` set to `["farm for sale", "acreage for sale"]` and `location` `"Missouri"`, with `maxEmails` at 300.
They widen `customDomains` with `@outlook.com` and `@hotmail.com`, which matters a great deal here because independent rural brokers rarely run branded mail.
Rows arrive with names and emails but almost no `profileUrl`, so the team enriches by name and brokerage before the first send.

A land surveying firm sizing three counties runs the Land And Farm Email Scraper separately for `"Callaway County"`, `"Osage County"` and `"Boone County"`.
County-level runs match the language of rural listing titles, so relevance is far higher than a national sweep.
Comparing dataset sizes shows where broker density justifies a field crew.

A timber buyer wants the widest possible net across the Southeast.
They run the Land And Farm Email Scraper for its email yield, then merge with the [LandWatch Email Scraper](https://apify.com/leads-scraper/landwatch-email-scraper) and the [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) and deduplicate on `email`.
Because rural brokers syndicate to multiple land portals, deduplication removes real overlap rather than noise.

### Responsible use of scraped land broker contacts

Everything the Land And Farm Email Scraper returns was already published on a public web page and indexed by Google.
That does not make every downstream use lawful, and knowing which rules apply to you is your responsibility.
The notes below are practical guidance, not legal advice.

Under CAN-SPAM in the United States, commercial email must avoid deceptive headers and subject lines, identify itself as an advertisement where required, carry a valid physical postal address, and honour opt-out requests promptly.
Under the GDPR and UK GDPR, a named individual's business address is still personal data, so you need a lawful basis, a genuine legitimate-interest assessment where you rely on one, transparency about the source, and a working route to object or erase.
ePrivacy rules and several EU member states add consent requirements for electronic marketing beyond the GDPR baseline.

One point deserves particular care with Land And Farm Email Scraper output.
Because you are reaching small independent brokerages using personal consumer mailboxes, an address here is often closer to a personal account than a corporate one.
Keep messages professional and specific to the broker's county, hold `possiblyTruncated` rows out of a first send, maintain a suppression list across runs, and retain `query` and `foundAt` as provenance.

### Limitations of the Land And Farm Email Scraper

**Land And Farm indexes land listings rather than broker profiles, so rows usually carry a broker email without a resolvable profile URL.**
In a measured live run, roughly 10 parsed blocks produced 9 identified records and 9 unique emails but only 1 profile URL.
Build your workflow around name-plus-email enrichment rather than around clickable profiles.

The Land And Farm Email Scraper only finds accounts whose email is publicly visible in Google's index.
A broker who keeps their address behind a contact form or inside an image will never appear, however many pages you fetch.

Google caps a single query at roughly 300 results, which is exactly why query expansion exists.
Because email yield is high here, that cap binds sooner than on a thin source, so leaving `expandQueries` on genuinely matters.

`username` and `profileUrl` are only populated when Land And Farm exposes a handle in the Google result, which here is the exception rather than the rule.
Those rows still carry `accountName` and usually `fullName`. That is a Google limitation, not a bug.

`possiblyTruncated: true` means Google's snippet ellipsis touched the address and it may be incomplete.
The Land And Farm Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
Free Apify plans stop at 100 emails per run, and results vary with keywords, domains and location, so no volume is guaranteed.

### Land And Farm Email Scraper FAQ

#### How many results should I expect from the Land And Farm Email Scraper?

Strong email volume with weak URL resolution: a measured live run produced 9 identified records, 9 unique emails and just 1 profile URL per roughly 10 parsed blocks.
Land And Farm indexes land listings rather than broker profiles, so rows usually carry a broker email without a resolvable profile URL.

#### Why do I get names and emails but not profile URLs?

Because the indexed pages are aggregated property listings. A listing title names the broker but exposes no URL-safe handle to build a canonical profile URL from.
The two fields outreach actually needs, name and email, are present on most rows.

#### Can I make the Land And Farm Email Scraper produce the missing profile URLs?

No. No configuration will manufacture a handle Google never printed.
If clickable profiles matter, use the [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper) instead.

#### Does the Land And Farm Email Scraper log into Land And Farm?

No. It never logs in, never calls an API and never opens landandfarm.com in a browser.
Every field comes from publicly indexed Google search results.

#### Is this an official Land And Farm tool?

No. It is an independent Apify Actor and is not affiliated with, supported by or endorsed by Land And Farm.

#### What keywords work best in the Land And Farm Email Scraper?

Land-use and listing language beats agent-directory language on an aggregator.
`"farm for sale"`, `"acreage for sale"`, `"pasture"` and `"cropland"` outperform profile-style phrasing.

#### Should I use states or counties in `location`?

States first, because the aggregator organises inventory state-first; counties when you need precision on one territory.
Metro names perform poorly, since acreage is not described that way.

#### Which email domains should I use with the Land And Farm Email Scraper?

Widen past the defaults immediately: add `@outlook.com` and `@hotmail.com` to `@gmail.com` and `@yahoo.com`.
Small rural brokerages use consumer mailboxes at a much higher rate than institutional firms.

#### What does `possiblyTruncated` mean?

Google's snippet cut the text with an ellipsis close enough to the address that it may be incomplete.
Verify those rows before sending.

#### Will one syndicating brokerage flood my dataset?

No. The Land And Farm Email Scraper deduplicates globally, so a brokerage on hundreds of syndicated tracts appears once.

#### Does a Land And Farm Email Scraper run resume if it is interrupted?

Yes. State lives in the key-value store keyed by an input hash, with saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING`.

#### Do I need my own proxy?

No, but Apify proxy credentials are required, because the Land And Farm Email Scraper uses the Apify GOOGLE_SERP proxy.

### Related Actors

| Actor | What it collects |
|---|---|
| [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 And Farm Phone Number Scraper](https://apify.com/neuro-scraper/land-and-farm-phone-number-scraper) | Public phone numbers from Land And Farm |
| [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.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 |
| [Zillow Rentals Email Scraper](https://apify.com/leads-scraper/zillow-rentals-email-scraper) | Public contact emails from Zillow |
| [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 |

### Leave a review

If the Land And Farm 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 about the Land And Farm Email Scraper, bug reports or a request for a custom build: contact neurodata.apify@gmail.com.

# Actor input Schema

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

Search terms describing the Land And Farm 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 Land And Farm.

## `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": [
    "land broker",
    "farm for sale"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "listing agent",
    "inquiries",
    "broker"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Land And Farm 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": [
        "land broker",
        "farm for sale"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "listing agent",
        "inquiries",
        "broker"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/land-and-farm-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": [
        "land broker",
        "farm for sale",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "listing agent",
        "inquiries",
        "broker",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/land-and-farm-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": [
    "land broker",
    "farm for sale"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "listing agent",
    "inquiries",
    "broker"
  ]
}' |
apify call leads-scraper/land-and-farm-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/land-and-farm-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/eIkw6kYWyoGSRrDH0/builds/IoSWXnKxjG51gCdTG/openapi.json