# Scoot Email Scraper (`neuro-scraper/scoot-email-scraper`) Actor

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

- **URL**: https://apify.com/neuro-scraper/scoot-email-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-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

### Scoot Email Scraper - public business contact emails from scoot.co.uk

The Scoot Email Scraper collects publicly indexed contact emails that appear in Google search results for `scoot.co.uk`. Scoot is a long-running UK business finder, one of the directories that local tradespeople and small firms have used to publish a contact route for decades.

The honest headline has to come first. **Scoot has a small and ageing indexed footprint, so expect low volume.** That is a property of the platform, not of the extraction pipeline, and no amount of keyword tuning changes it.

What is genuinely good about the Scoot Email Scraper is quality per page. On the listings Google does hold, identity resolution and email extraction both work extremely well.

So the right way to think about this Actor is: a small, clean UK dataset rather than a big one. Local-services agencies, SMB SaaS vendors and franchise development teams working the UK market are the people it suits.

#### A measured live result, stated plainly

A live Google run of the Scoot Email Scraper returned **10 result blocks, 10 rows with account identity, 10 resolvable profile URLs and 8 unique emails**. Those are observed figures.

Ten out of ten on identity is as good as this family gets. Scoot exposes a clean listing slug that Google prints, so the Scoot Email Scraper reconstructs a working `profileUrl` on every row.

Eight unique emails from ten blocks is also strong. The caveat is not the hit rate on a page - it is how many pages exist to be found in the first place.

### Features of the Scoot Email Scraper

Every feature below is genuinely implemented. Nothing here is aspirational.

| Feature | What it means in practice |
|---|---|
| Google SERP parsing | Reads Google result pages through the Apify GOOGLE_SERP proxy. No browser, no JavaScript rendering |
| Structural block detection | Locates the `<h3>` title, then the smallest surrounding block. Does not depend on Google's CSS class names |
| Domain filter | Only emails ending in one of your `customDomains` values are kept |
| Query expansion | Base, quoted, `intitle:` and one variant per query modifier. Base queries run first |
| Global deduplication | An email seen once is never pushed twice, across every query and every page |
| 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 locals |
| Boundary-correct matching | `@gmail.com` does 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 block |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries | Up to 3 attempts per page, exponential backoff, a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Re-queueing | Blocked or failed queries are retried once at the end of the run |
| Resumable run | State is stored in the key-value store, keyed by a hash of the input, and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Fallback parser | If Google's markup changes, the run degrades to "emails without account details" rather than "no emails" |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |
| Dataset output | Rows push immediately and export to CSV, JSON, Excel or XML from the Apify dataset |

None of those features change the underlying arithmetic. The Scoot Email Scraper is careful and resilient, but it is still limited by how much of `scoot.co.uk` Google currently holds.

Query expansion is the one that helps most. When the index is small, running many query variants is the only way to reach the corners of it.

### How the Scoot Email Scraper works

The pipeline is six steps and there is nothing hidden inside it.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google search queries with the `site:` operator against `scoot.co.uk`, for example `site:scoot.co.uk tradesman "@gmail.com" "Leeds"`.
3. It fetches Google result pages through the Apify GOOGLE_SERP proxy using `aiohttp`, asynchronously.
4. It parses each result block structurally, finding the `<h3>` title and the smallest block around it.
5. It extracts emails from that block's text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead straight into the Apify dataset.

The Scoot Email Scraper does **not** log into Scoot, does not use any Scoot API, and does not open the directory in a browser. Every field comes from publicly indexed Google search results - titles, snippets and site labels, with no authentication and no cookies.

### Who the Scoot Email Scraper is built for

This is a UK local business Actor, so its audience is people selling services to small British firms.

Local-services agencies use it to build outreach lists for web design, SEO, print and signage work in a defined town or county. SMB SaaS vendors use it to reach owner-operated trades that still run on paper diaries.

Franchise development teams use it to identify independent operators in a category worth converting. Field sales teams use it to plan territory coverage across a UK region.

Because the footprint is small, the Scoot Email Scraper works best as a supplementary source rather than a primary one. Pair it with [Touch Local Email Scraper](https://apify.com/leads-scraper/touch-local-email-scraper), which sits in the same UK directory network, and with [Fyple Email Scraper](https://apify.com/neuro-scraper/fyple-email-scraper) for broader multi-country coverage.

### Input fields for the Scoot Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["local business", "tradesman"]` | Search terms - niche, job title, industry |
| `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", "enquiries", "owner", "get a quote"]` | 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 |

#### How the Scoot Email Scraper input fields actually behave

`customDomains` is the highest-leverage field here, because the default two domains miss most UK small business mail. Add `@btinternet.com`, `@sky.com`, `@virginmedia.com`, `@hotmail.co.uk`, `@yahoo.co.uk` and `@live.co.uk` before anything else.

`keywords` should name a trade. `plumber`, `electrician`, `mobile hairdresser`, `driving instructor` and `man and van` all match the Scoot index better than the broad defaults `local business` and `tradesman`.

`location` narrows to a town or county and is worth setting on almost every run. UK directories are organised around place, so `"Leeds"`, `"West Midlands"` or `"Kent"` reshapes the results considerably.

`queryModifiers` only fire when `expandQueries` is `true`. The defaults `enquiries`, `owner` and `get a quote` are tuned for local listings, where those exact phrases sit beside published addresses.

`maxEmails` is a hard stop shared across the worker pool, and on a small index you should set it generously so the run explores the whole expanded query set. `maxConcurrency` and `maxPagesPerQuery` trade speed against politeness; the defaults of 5 and 30 are fine.

### JSON input example for the Scoot Email Scraper

```json
{
  "keywords": ["plumber", "electrician", "driving instructor"],
  "location": "Leeds",
  "customDomains": ["@gmail.com", "@yahoo.co.uk", "@btinternet.com", "@sky.com", "@hotmail.co.uk"],
  "maxEmails": 100,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "enquiries", "owner", "get a quote"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

The UK webmail domains are the point of that example. `@btinternet.com` and `@sky.com` are everywhere in British trade listings and neither is in the default filter.

That is a realistic configuration for the Scoot Email Scraper: three trades, a city, `GB` as the country code, and a domain filter that matches how UK sole traders actually keep their mail.

### Output fields of the Scoot Email Scraper

Every dataset item carries all fourteen fields.

| 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 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 - verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

On Scoot, `username` and `profileUrl` are populated on essentially every row, because listing pages carry a stable slug. The Scoot Email Scraper builds the canonical link as `https://www.scoot.co.uk/{username}`.

Check `possiblyTruncated` before you send. When it is `true`, Google's snippet ellipsis may have clipped the address and you should confirm it on the source page.

### JSON output example from the Scoot Email Scraper

```json
[
  {
    "network": "Scoot",
    "keyword": "plumber",
    "query": "site:scoot.co.uk plumber contact \"@btinternet.com\" \"Leeds\"",
    "title": "Aire Valley Plumbing & Heating - Leeds - Scoot",
    "accountName": "Aire Valley Plumbing & Heating",
    "fullName": "Aire Valley Plumbing & Heating",
    "username": "aire-valley-plumbing-heating-leeds",
    "profileUrl": "https://www.scoot.co.uk/aire-valley-plumbing-heating-leeds",
    "url": "https://www.scoot.co.uk/aire-valley-plumbing-heating-leeds",
    "description": "Domestic plumbing, boiler servicing and bathroom fitting across Leeds. Free quotes by email.",
    "email": "airevalleyplumbing@btinternet.com",
    "emailDomain": "@btinternet.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-29T16:12:07Z"
  },
  {
    "network": "Scoot",
    "keyword": "driving instructor",
    "query": "site:scoot.co.uk driving instructor \"get a quote\" \"@gmail.com\" \"Leeds\"",
    "title": "Northgate Driving School - Leeds - Scoot",
    "accountName": "Northgate Driving School",
    "fullName": "Northgate Driving School",
    "username": "northgate-driving-school-leeds",
    "profileUrl": "https://www.scoot.co.uk/northgate-driving-school-leeds",
    "url": "https://www.scoot.co.uk/northgate-driving-school-leeds",
    "description": "DVSA approved instructors offering manual and automatic lessons in north Leeds.",
    "email": "northgate.driving@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-29T16:13:44Z"
  }
]
```

Both rows carry a clean handle, which is the normal shape here. Quality per record is the strength of the Scoot Email Scraper; quantity of records is not.

### Use cases for the Scoot Email Scraper

| Audience | What they do with the data |
|---|---|
| UK local-services agencies | Build outreach lists for web design, SEO, print or signage in a town or county |
| SMB SaaS vendors | Reach owner-operated trades still running on paper diaries |
| Franchise development teams | Identify independent operators in a category worth converting |
| Field sales teams | Plan territory coverage across a UK region before working a route |
| Payment and POS providers | Approach small retail and hospitality businesses in a chosen town |
| Insurance and finance brokers | Prospect sole traders by trade and postcode area |
| Trade suppliers and merchants | Reach tradespeople who buy materials locally |
| Local data researchers | Sample how UK trades publish contact routes in older directories |

Each of those targets a business inbox that an owner published in a directory so customers could get in touch. That is the honest boundary of what the Scoot Email Scraper does.

### Targeting tips for the Scoot Email Scraper

`location` and `countryCode` are both real levers, and on a UK-only directory they should be treated as near-mandatory.

Set `countryCode` to `GB` so the search proxy sees the UK view of the index. Leaving it empty makes the Scoot Email Scraper compete against international results that have nothing to do with British trades.

Set `location` to a town, city or county rather than "UK". Because the underlying directory is organised around place, `"Sheffield"`, `"Surrey"` or `"Greater Manchester"` reaches genuinely different listings.

Since the index is small, run more keywords rather than more pages. Fifteen specific trades will find more than two generic ones ever will, and the modifiers `owner` and `get a quote` reach the exact listing text where addresses appear.

For broader UK coverage, pair it with [Touch Local Email Scraper](https://apify.com/leads-scraper/touch-local-email-scraper) from the same directory network, and widen further with [Cybo Email Scraper](https://apify.com/neuro-scraper/cybo-email-scraper) or [Lacartes Email Scraper](https://apify.com/neuro-scraper/lacartes-email-scraper).

### Limitations of the Scoot Email Scraper

Read all of these before your first run.

- **Scoot has a small and ageing indexed footprint, so expect low volume.** Yield per page is good; the number of pages is the constraint.
- Because listings can be old, some addresses may no longer be monitored. Verify before running a campaign on them.
- The Scoot Email Scraper only finds addresses that are **publicly visible in Google's index**. Anything Google has not indexed is invisible to it.
- Google caps a single query at roughly 300 results, which is exactly why query expansion exists and defaults to on.
- `possiblyTruncated: true` means Google's snippet ellipsis may have cut the email short. Verify it before sending.
- It requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
- Free Apify plans are capped at 100 emails per run; paid plans are uncapped. On this Actor the platform's footprint usually binds before the plan cap does.
- `username` and `profileUrl` are only populated when Google exposes a handle. Scoot almost always does, but rows from category or search pages can still arrive with `username: null` and an empty `profileUrl`. That is a Google limitation, not a bug.
- Results vary with keywords, domains and location. No volume is guaranteed by the Scoot Email Scraper or by any Actor in this family.

### Responsible use of Scoot Email Scraper output

The addresses the Scoot Email Scraper surfaces are business contacts that owners published in a UK directory so that customers could reach them. Treat them as exactly that.

UK GDPR and PECR both apply here, and a sole trader's address is personal data. Record your legitimate interest, identify yourself and your company in the first line, and make the relevance of the message obvious.

Honour opt-outs immediately and permanently, keep your list current, and screen against the Corporate Telephone Preference Service equivalents where relevant. Do not use this output for bulk unsolicited mail.

### FAQ about the Scoot Email Scraper

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

Fewer than from most Actors in this family, because Scoot has a small and ageing indexed footprint. A live Google run returned 10 result blocks, 10 identified accounts, 10 profile URLs and 8 unique emails - excellent per-page quality, but the pool of pages is limited. Run many specific trade keywords and expect a small, clean dataset rather than a large one.

#### Why is the footprint described as ageing?

Scoot is a long-established UK directory whose indexed listings include older records. That means some contact details may be out of date, so verification before outreach is sensible.

#### Does the Scoot Email Scraper log into Scoot or use its API?

No. It builds Google `site:scoot.co.uk` queries, fetches result pages through the Apify GOOGLE_SERP proxy and parses them. There is no browser, no login, no API and no cookies.

#### Why do nearly all rows have a working profile URL?

Because Scoot listing pages carry a stable slug that Google prints. The Scoot Email Scraper derives `username` from it and builds `profileUrl` as `https://www.scoot.co.uk/{username}`.

#### What is the fastest way to increase Scoot Email Scraper yield?

Add UK webmail domains to `customDomains` - `@btinternet.com`, `@sky.com`, `@virginmedia.com`, `@hotmail.co.uk`, `@yahoo.co.uk` - and run many specific trade keywords instead of two generic ones.

#### Should I set `countryCode`?

Yes, set it to `GB`. Scoot is a UK-only directory, and a UK search proxy view materially improves what the Scoot Email Scraper finds.

#### Which Actor should I run alongside it?

[Touch Local Email Scraper](https://apify.com/leads-scraper/touch-local-email-scraper), which covers a sibling UK directory in the same network, and [Fyple Email Scraper](https://apify.com/neuro-scraper/fyple-email-scraper) for broader multi-country local coverage.

#### Why does the Scoot Email Scraper turn `expandQueries` on by default?

Google caps one query at roughly 300 results. Expansion runs base, quoted and `intitle:` variants plus one per modifier, which matters even more when the index is small. Base queries always run first.

#### Can I run the Scoot Email Scraper on a free Apify plan?

Yes. Free plans are capped at 100 emails per run, which on this Actor is usually well above what the platform's footprint will yield anyway. Paid plans are uncapped.

#### What happens if a Scoot Email Scraper run is interrupted?

State is saved in the key-value store, keyed by a hash of your input, and written on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events. Restarting with the same input resumes rather than starting over.

#### Which export formats does the Scoot Email Scraper support?

Anything the Apify dataset supports - CSV, JSON, Excel and XML - plus the API for pushing rows straight into a CRM.

#### Is the Scoot Email Scraper affiliated with Scoot?

No. It is an independent Actor that reads publicly indexed Google results, with no relationship to or endorsement from the platform.

### Related Actors

More email scrapers from the same Business & Professional Directories family, built on the same Google SERP pipeline.

| Actor | What it collects |
|---|---|
| [Scoot Email and Phone Number Scraper](https://apify.com/neuro-scraper/scoot-email-and-phone-number-scraper) | Emails and phone numbers from Scoot |
| [Scoot Phone Number Scraper](https://apify.com/neuro-scraper/scoot-phone-number-scraper) | Public phone numbers from Scoot |
| [Angi Email Scraper](https://apify.com/leads-scraper/angi-email-scraper) | Public contact emails from Angi |
| [Bark Email Scraper](https://apify.com/leads-scraper/bark-email-scraper) | Public contact emails from Bark |
| [Better Business Bureau Email Scraper](https://apify.com/leads-scraper/better-business-bureau-email-scraper) | Public contact emails from Better Business Bureau |
| [Bizapedia Email Scraper](https://apify.com/neuro-scraper/bizapedia-email-scraper) | Public contact emails from Bizapedia |
| [Brownbook Email Scraper](https://apify.com/neuro-scraper/brownbook-email-scraper) | Public contact emails from Brownbook |
| [Callupcontact Email Scraper](https://apify.com/neuro-scraper/callupcontact-email-scraper) | Public contact emails from CallUpContact |
| [Capterra Email Scraper](https://apify.com/leads-scraper/capterra-email-scraper) | Public contact emails from Capterra |
| [Clutch Email Scraper](https://apify.com/leads-scraper/clutch-email-scraper) | Public contact emails from Clutch |
| [Crunchbase Email Scraper](https://apify.com/leads-scraper/crunchbase-email-scraper) | Public contact emails from Crunchbase |
| [Cybo Email Scraper](https://apify.com/neuro-scraper/cybo-email-scraper) | Public contact emails from Cybo |
| [Cylex Email Scraper](https://apify.com/neuro-scraper/cylex-email-scraper) | Public contact emails from Cylex |
| [EC21 Email Scraper](https://apify.com/neuro-scraper/ec21-email-scraper) | Public contact emails from EC21 |
| [Europages Email Scraper](https://apify.com/leads-scraper/europages-email-scraper) | Public contact emails from Europages |
| [ExportHub Email Scraper](https://apify.com/neuro-scraper/exporthub-email-scraper) | Public contact emails from ExportHub |
| [FindUsLocal Email Scraper](https://apify.com/neuro-scraper/finduslocal-email-scraper) | Public contact emails from FindUsLocal |
| [Foursquare Email Scraper](https://apify.com/neuro-scraper/foursquare-email-scraper) | Public contact emails from Foursquare |
| [Fyple Email Scraper](https://apify.com/neuro-scraper/fyple-email-scraper) | Public contact emails from Fyple |
| [G2 Email Scraper](https://apify.com/neuro-scraper/g2-email-scraper) | Public contact emails from G2 |
| [Hotfrog Email Scraper](https://apify.com/leads-scraper/hotfrog-email-scraper) | Public contact emails from Hotfrog |
| [Houzz Email Scraper](https://apify.com/leads-scraper/houzz-email-scraper) | Public contact emails from Houzz |
| [Infobel Email Scraper](https://apify.com/neuro-scraper/infobel-email-scraper) | Public contact emails from Infobel |
| [Kompass Email Scraper](https://apify.com/leads-scraper/kompass-email-scraper) | Public contact emails from Kompass |
| [Lacartes Email Scraper](https://apify.com/neuro-scraper/lacartes-email-scraper) | Public contact emails from Lacartes |
| [Manta Email Scraper](https://apify.com/leads-scraper/manta-email-scraper) | Public contact emails from Manta |
| [MapQuest Email Scraper](https://apify.com/neuro-scraper/mapquest-email-scraper) | Public contact emails from MapQuest |
| [N49 Email Scraper](https://apify.com/neuro-scraper/n49-email-scraper) | Public contact emails from N49 |
| [Porch Email Scraper](https://apify.com/neuro-scraper/porch-email-scraper) | Public contact emails from Porch |
| [Thomasnet Email Scraper](https://apify.com/leads-scraper/thomasnet-email-scraper) | Public contact emails from Thomasnet |
| [Thumbtack Email Scraper](https://apify.com/leads-scraper/thumbtack-email-scraper) | Public contact emails from Thumbtack |
| [Touch Local Email Scraper](https://apify.com/leads-scraper/touch-local-email-scraper) | Public contact emails from Touch Local |
| [TradeIndia Email Scraper](https://apify.com/leads-scraper/tradeindia-email-scraper) | Public contact emails from TradeIndia |
| [Trustpilot Email Scraper](https://apify.com/leads-scraper/trustpilot-email-scraper) | Public contact emails from Trustpilot |
| [Tupalo Email Scraper](https://apify.com/leads-scraper/tupalo-email-scraper) | Public contact emails from Tupalo |
| [Yalwa Email Scraper](https://apify.com/leads-scraper/yalwa-email-scraper) | Public contact emails from Yalwa |
| [Yellow Pages Email Scraper](https://apify.com/leads-scraper/yellow-pages-email-scraper) | Public contact emails from Yellow Pages |
| [Angi Email and Phone Number Scraper](https://apify.com/neuro-scraper/angi-email-and-phone-number-scraper) | Emails and phone numbers from Angi |
| [Bark Email and Phone Number Scraper](https://apify.com/neuro-scraper/bark-email-and-phone-number-scraper) | Emails and phone numbers from Bark |
| [Better Business Bureau Email and Phone Number Scraper](https://apify.com/leads-scraper/better-business-bureau-email-and-phone-number-scraper) | Emails and phone numbers from Better Business Bureau |
| [Bizapedia Email and Phone Number Scraper](https://apify.com/neuro-scraper/bizapedia-email-and-phone-number-scraper) | Emails and phone numbers from Bizapedia |
| [Brownbook Email and Phone Number Scraper](https://apify.com/neuro-scraper/brownbook-email-and-phone-number-scraper) | Emails and phone numbers from Brownbook |

### Leave a review

If the Scoot 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.

# Actor input Schema

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

Search terms describing the Scoot 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 Scoot.

## `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": [
    "local business",
    "tradesman"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "enquiries",
    "owner",
    "get a quote"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Scoot 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": [
        "local business",
        "tradesman"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "enquiries",
        "owner",
        "get a quote"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/scoot-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": [
        "local business",
        "tradesman",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "enquiries",
        "owner",
        "get a quote",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/scoot-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": [
    "local business",
    "tradesman"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "enquiries",
    "owner",
    "get a quote"
  ]
}' |
apify call neuro-scraper/scoot-email-scraper --silent --output-dataset

```

## MCP server setup

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