# LoopNet Email Scraper (`leads-scraper/loopnet-email-scraper`) Actor

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

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

### LoopNet Email Scraper for commercial real estate broker prospecting

The LoopNet Email Scraper collects publicly indexed contact emails belonging to commercial brokers, listing agents and brokerage teams that appear on LoopNet.
It turns a keyword plus a location into a clean, deduplicated dataset you can load straight into a CRM or an outreach sequence.
Every row comes from Google's public index of loopnet.com pages, never from a logged-in session.

LoopNet is the largest commercial listing marketplace in the United States, so its broker pages are unusually well indexed.
In a measured live run, roughly 10 parsed result blocks produced 10 identified broker records, 10 resolvable profile URLs and 9 unique emails.
That makes the LoopNet Email Scraper one of the two strongest performers in this Real Estate and Property category, alongside the [Land.com Email Scraper](https://apify.com/leads-scraper/land-com-email-scraper).

The LoopNet Email Scraper is built for teams that sell into commercial brokerage rather than for anyone chasing private data.

Commercial brokers publish contact addresses deliberately, because a deal that nobody can reach is a deal that dies.
A listing agent wants an inbound call about a vacant 40,000 sq ft flex building; that is the entire economic point of the profile.
The LoopNet Email Scraper simply reads what those professionals already chose to make public.

#### What the LoopNet Email Scraper actually does

The Actor builds Google queries with the `site:` operator against `loopnet.com`, fetches the result pages through the Apify GOOGLE_SERP proxy, and parses each block structurally.
It locates the `<h3>` title, walks up to the smallest surrounding block, then extracts emails from that block's text with a domain-filtered regular expression.
Because parsing is structural rather than CSS-class based, a Google layout change degrades gracefully instead of breaking.

It does not log into LoopNet, use any LoopNet API, or open loopnet.com in a browser.
There is no JavaScript rendering, no authentication and no cookies anywhere in the pipeline.
All commercial real estate broker email list data comes from titles, snippets and site labels that Google already publishes.

### Key features of the LoopNet Email Scraper

Every capability below is part of the shipped LoopNet Email Scraper, not a roadmap item.

| Feature | What it means for CRE lead generation |
|---|---|
| Query expansion | Each keyword x domain pair is searched as a base query, a quoted query, an `intitle:` query and one variant per modifier. Base queries run first. |
| Global deduplication | An email found by five different queries is written to the dataset once. |
| Email normalisation | 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 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 that fires on `maxEmails`. |
| Retries and block detection | Up to three attempts per page with exponential backoff, a fresh proxy session per request, and CAPTCHA or consent pages detected and retried rather than treated as empty. |
| Failed-query requeue | Blocked or failed queries are re-queued once at the end of the run. |
| Resumable state | State is stored in the key-value store keyed by a hash of the input, and saves fire on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. |
| Whole-page fallback parser | If Google's markup changes, the run degrades to emails without account details rather than to no emails. |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page. |

### How the LoopNet Email Scraper works

Step one is input parsing: your keywords, location phrase, email domains and limits are read and hashed into a resumable state key.
Step two builds the query set, multiplying every keyword by every domain and, when expansion is on, by every query modifier.
A single query such as `site:loopnet.com "industrial broker" "@gmail.com" "Dallas"` is one of dozens the LoopNet Email Scraper will issue.

Step three has the LoopNet Email Scraper fetch Google result pages concurrently through the Apify GOOGLE_SERP proxy using `aiohttp`.
Step four parses each block, step five extracts and normalises emails, and step six deduplicates globally before pushing to the dataset.
Rows land in the dataset immediately, so you can watch a commercial real estate broker email list build in real time in the Apify console.

The LoopNet Email Scraper stops as soon as `maxEmails` unique addresses have been collected.
That stop signal is shared across all concurrent workers, so you do not overshoot your budget.
Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

### LoopNet Email Scraper input fields

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["commercial broker", "commercial real estate"]` | 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 LoopNet Email Scraper will run on defaults alone.
In practice the combination of `keywords`, `location` and `customDomains` decides almost everything about your result quality.

#### Location targeting in the LoopNet Email Scraper

`location` is the single highest-leverage input in this Actor, because commercial brokerage is a territorial business.
A broker in Charlotte does not compete with a broker in Sacramento, so a national run mixes markets you will never sell into.
Running the LoopNet Email Scraper once per target market produces far cleaner lists than one undifferentiated national sweep.

Work at three levels. Metro level is the workhorse: `"Dallas Fort Worth"`, `"Inland Empire"`, `"Northern New Jersey"`, `"Phoenix"`.
Metro phrases match how brokers actually describe their coverage in profile copy and listing headers.

County level is best for industrial and land-adjacent commercial product: `"Maricopa County"`, `"Cook County"`, `"Riverside County"`.
County names appear constantly in entitlement, zoning and site-selection language, which is exactly where development-oriented brokers write.

State level is the right choice for regional lenders, appraisal firms and title companies with statewide licences: `"Texas"`, `"Ohio"`, `"Georgia"`.
Pair a state-level `location` with `countryCode: "US"` so the search proxy stays in the right index.
Sub-market phrases such as `"Uptown Charlotte"` or `"Route 78 corridor"` also work and often surface leasing specialists that a metro query buries.

#### Example input JSON

```json
{
  "keywords": ["industrial broker", "office leasing agent", "retail investment sales"],
  "location": "Dallas Fort Worth",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com"],
  "maxEmails": 250,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "listing agent", "inquiries", "broker"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

### LoopNet Email Scraper output fields

Every dataset item written by the LoopNet 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 LoopNet 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 |

The default dataset view surfaces the eight columns most people export, but the LoopNet Email Scraper always writes the full record underneath.
Keep `query` and `foundAt` in your export; they are your provenance trail if a recipient ever asks where you got their address.

#### Example output JSON

```json
[
  {
    "network": "LoopNet",
    "keyword": "industrial broker",
    "query": "site:loopnet.com \"industrial broker\" \"@gmail.com\" \"Dallas Fort Worth\"",
    "title": "Greg Marshall - Industrial Broker - Dallas, TX | LoopNet",
    "accountName": "Greg Marshall",
    "fullName": "Greg Marshall",
    "username": "greg-marshall",
    "profileUrl": "https://www.loopnet.com/greg-marshall",
    "url": "https://www.loopnet.com/greg-marshall",
    "description": "Industrial and flex space specialist covering DFW. Inquiries: greg.marshall.cre@gmail.com",
    "email": "greg.marshall.cre@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-11T09:24:17Z"
  },
  {
    "network": "LoopNet",
    "keyword": "office leasing agent",
    "query": "site:loopnet.com intitle:\"office leasing agent\" \"@yahoo.com\" \"Dallas Fort Worth\"",
    "title": "Office Leasing Agent - Las Colinas Tower | LoopNet",
    "accountName": "Rivera Commercial Group",
    "fullName": "Ana Rivera",
    "username": "ana-rivera",
    "profileUrl": "https://www.loopnet.com/ana-rivera",
    "url": "https://www.loopnet.com/ana-rivera",
    "description": "Class A office leasing, Las Colinas and Irving submarkets. Contact ana.rivera.leasing@yahoo.com",
    "email": "ana.rivera.leasing@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-11T09:24:52Z"
  }
]
```

### Use cases for the LoopNet Email Scraper

| Audience | How they use the LoopNet Email Scraper |
|---|---|
| CRE technology vendors | Build a market-by-market list of deal management, underwriting and property marketing buyers. |
| Lenders and debt brokers | Reach listing agents on assets that will need bridge, construction or permanent financing. |
| Title and escrow firms | Prospect the brokerages that route closings in a specific county. |
| Appraisal firms | Find the brokers who order valuations for a given asset class and metro. |
| Tenant-rep recruiters | Source licensed brokers by specialty and submarket for hiring pipelines. |
| Construction and facilities suppliers | Reach the leasing and asset teams who specify tenant improvement work. |
| Property marketing agencies | Pitch photography, drone, video and OM production to active listing agents. |
| Market researchers | Assemble a sampling frame of brokers for a survey or a rent study. |

Across all of these, the LoopNet Email Scraper is a top-of-funnel sourcing step rather than a complete go-to-market motion.
It gives you a defensible starting list; the segmentation, verification and messaging are still your job.

### LoopNet Email Scraper examples

A CRE software vendor launching in one metro sets `keywords` to `["investment sales broker", "capital markets broker"]` and `location` to `"Phoenix"`.
With `maxEmails` at 150 and `expandQueries` on, the LoopNet Email Scraper works through base, quoted, `intitle:` and modifier variants until the cap is reached.
The resulting commercial property leads are already segmented by keyword, so the vendor can write two different opening lines.

A construction supplier targets tenant improvement work across three counties.
They run the LoopNet Email Scraper three times with `location` set to `"Maricopa County"`, `"Pima County"` and `"Clark County"`, keeping keywords identical.
Comparing dataset sizes tells them where broker density and email visibility are highest before they commit a rep to the territory.

A title company wants statewide coverage and points the LoopNet Email Scraper at `location` `"Ohio"` with `countryCode: "US"`.
They widen `customDomains` to include `@outlook.com` and `@hotmail.com`, which meaningfully raises yield because many independent brokers use consumer mailboxes.
They then run the [Crexi Email Scraper](https://apify.com/leads-scraper/crexi-email-scraper) and the **Showcase Email Scraper** over the same territory and merge on `email`.

### Responsible use of scraped commercial contacts

Everything the LoopNet Email Scraper returns was already published on a public web page and indexed by Google.
That does not make every use of it lawful, and it is your responsibility to know which rules apply to you.
This section is practical guidance, not legal advice.

Under CAN-SPAM in the United States, commercial email must not use deceptive headers or subject lines, must disclose that it is an advertisement where required, must include a valid physical postal address, and must honour opt-out requests promptly.
Under the GDPR and the UK GDPR, a business contact address for an identified individual is still personal data, so you need a lawful basis, a genuine legitimate-interest assessment where you rely on one, transparency about where the data came from, and a working route to object or erase.
Several EU member states and the ePrivacy rules add consent requirements for electronic marketing that go beyond the GDPR baseline.

Practical habits matter as much as the legal text when you work with LoopNet Email Scraper output.
Keep `possiblyTruncated` rows out of your first send, verify addresses before a large campaign, suppress anyone who opts out across every future run, and keep the `query` and `foundAt` fields as your provenance record.
Send relevant, specific messages; a broker who receives a genuinely useful pitch about their own submarket rarely complains.

### Limitations of the LoopNet Email Scraper

The LoopNet 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 an image will never appear, regardless of how many pages you fetch.

Google caps a single query at roughly 300 results, which is precisely why query expansion exists.
Leaving `expandQueries` on is the difference between one 300-result ceiling and dozens of them.

`username` and `profileUrl` are only populated when LoopNet exposes a handle in the Google result.
LoopNet resolves handles well in practice, but where Google prints only a display name those rows carry `accountName` and `fullName` with an empty `username` and `profileUrl`. That is a Google limitation, not a bug.

`possiblyTruncated: true` means Google's snippet ellipsis touched the address and it may be cut off; verify before sending.
The LoopNet 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.

### LoopNet Email Scraper FAQ

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

In a measured live run, about 10 parsed result blocks produced 10 identified records, 10 profile URLs and 9 unique emails.
That is among the best ratios in this category, but yield still depends on your keywords, domains and location.

#### Does the LoopNet Email Scraper log into LoopNet?

No. It never logs in, never calls a LoopNet API and never opens loopnet.com in a browser.
Every field is derived from publicly indexed Google search results.

#### Is this an official LoopNet or CoStar tool?

No. It is an independent Apify Actor and is not affiliated with, supported by or endorsed by LoopNet or CoStar.

#### Which email domains should I use with the LoopNet Email Scraper?

Start with the defaults `@gmail.com` and `@yahoo.com`, then add `@outlook.com` and `@hotmail.com`.
Independent commercial brokers use consumer mailboxes far more often than large national brokerages do.

#### Can the LoopNet Email Scraper target a single submarket?

Yes. Put the submarket phrase in `location`, for example `"Uptown Charlotte"` or `"Inland Empire"`.
Narrow location phrases usually produce fewer but far more relevant commercial real estate broker email list rows.

#### What does `possiblyTruncated` mean?

Google's snippet cut the text with an ellipsis close enough to the email that the address may be incomplete.
Treat those rows as leads to verify rather than as send-ready contacts.

#### Why are some rows missing `username` and `profileUrl`?

Google sometimes prints only a display name for a page, with no handle to build a canonical URL from.
Those rows still carry a usable email, `accountName` and `fullName`.

#### How do I get more results out of the LoopNet Email Scraper?

Add keywords, add email domains, raise `maxEmails`, keep `expandQueries` on, and split one broad run into several location-specific runs.
Running sibling Actors such as the [CommercialSearch Email Scraper](https://apify.com/neuro-scraper/commercialsearch-email-scraper) over the same territory and merging on `email` is the most effective single tactic.

#### Does a LoopNet Email Scraper run resume if it is interrupted?

Yes. State is stored in the key-value store keyed by a hash of your input, and saves fire on `PERSIST_STATE`, `MIGRATING` and `ABORTING`.

#### Do I need my own proxy?

No, but you do need Apify proxy credentials, because the LoopNet Email Scraper uses the Apify GOOGLE_SERP proxy.

#### What should I do about duplicate people across platforms?

Deduplicate on `email` after merging datasets.
The LoopNet Email Scraper deduplicates globally within a run, but a broker listed on several marketplaces will appear once per Actor.

#### How long does a LoopNet Email Scraper run take?

It depends on `maxEmails`, `maxPagesPerQuery` and `maxConcurrency`.
Raising `maxConcurrency` speeds a run up but increases the chance of blocked pages, which the Actor detects and retries.

#### Can I schedule the LoopNet Email Scraper?

Yes. Schedule it like any Apify Actor and let the dataset accumulate; deduplicate on `email` downstream between runs.

### Related Actors

| Actor | What it collects |
|---|---|
| [LoopNet Email and Phone Number Scraper](https://apify.com/leads-scraper/loopnet-email-and-phone-number-scraper) | Emails and phone numbers from LoopNet |
| [LoopNet Phone Number Scraper](https://apify.com/leads-scraper/loopnet-phone-number-scraper) | Public phone numbers from LoopNet |
| [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 |
| [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 LoopNet 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 LoopNet 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 LoopNet 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 LoopNet.

## `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": [
    "commercial broker",
    "commercial real estate"
  ],
  "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 LoopNet 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": [
        "commercial broker",
        "commercial real estate"
    ],
    "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/loopnet-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": [
        "commercial broker",
        "commercial real estate",
    ],
    "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/loopnet-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": [
    "commercial broker",
    "commercial real estate"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "listing agent",
    "inquiries",
    "broker"
  ]
}' |
apify call leads-scraper/loopnet-email-scraper --silent --output-dataset

```

## MCP server setup

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