# Preply Email Scraper (`neuro-scraper/preply-email-scraper`) Actor

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

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

### Preply Email Scraper — Extract Public Contact Emails from Preply Tutor Pages

The **Preply Email Scraper** finds publicly indexed contact emails connected to Preply tutor profiles and question pages, and returns them as clean, structured lead data.

You give it keywords such as `tutor` or `language teacher`, choose the email domains you care about, and the Preply Email Scraper writes a dataset of leads with account names, tutor handles, snippets and profile URLs.

Preply is a global one-to-one tutoring marketplace, strongest in language learning but now spanning maths, music, programming and test preparation.

Every tutor gets a real public profile at `preply.com/en/tutor/{id}`, which is why Preply results usually carry a usable handle and a canonical profile link rather than just a display name.

**Important:** the Preply Email Scraper never logs into Preply, never uses a Preply API, and never opens `preply.com` itself. Every record comes from publicly indexed Google search results.

One honest expectation to set up front: Preply deliberately keeps tutor contact details private and routes students through its own messaging system, so publicly listed email addresses are less common here than on creator platforms.

That makes the Preply Email Scraper a Preply email extractor for tutor recruiting, edtech lead generation, language-school partnerships and market research — with steady rather than spectacular volume.

***

### Key Features of the Preply Email Scraper

Everything listed below is a capability the Preply Email Scraper genuinely has.

| Feature | What it means in practice |
|---|---|
| Google `site:` search collection | The Preply Email Scraper queries Google restricted to `preply.com`, so only Preply pages are parsed |
| Tutor-profile awareness | Handles are recovered from the `/tutor/` path, producing a clean `preply.com/en/tutor/{id}` link |
| Multilingual path handling | Locale segments such as `/en/`, `/es/`, `/de/`, `/fr/`, `/pt/`, `/ja/` and `/tr/` are handled when recovering a handle |
| Country targeting | `countryCode` steers the search proxy, which materially changes which tutors surface — a real lever on a marketplace this international |
| Query expansion | Each keyword × domain pair is searched in several phrasings: base, quoted, `intitle:`, plus one variant per query modifier |
| Domain-filtered extraction | Only addresses ending in your `customDomains` list are kept |
| Global deduplication | An email appears once across every query and every page of the run |
| Obfuscation-aware parser | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Discards a hit that is only the tail of another address in the same result block |
| Structural HTML parsing | Finds the `<h3>` title then the smallest enclosing block — it does not depend on Google's CSS class names |
| Whole-page fallback parser | If Google's markup changes, the run degrades to "emails without account details" rather than "no emails" |
| Concurrency | An `asyncio` worker pool runs several queries in parallel with a shared stop signal on `maxEmails` |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Blocked-query requeue | Failed or blocked queries are re-queued once at the end of the run |
| Resumable state | Progress is kept in the key-value store keyed by a hash of your input, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Streaming dataset writes | Each lead is pushed to the Apify dataset the moment it is found |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

***

### How the Preply Email Scraper Works

The pipeline is short and deliberately transparent. There is no browser, no JavaScript rendering, no authentication and no cookies.

**1. Read input.** The Preply Email Scraper loads your keywords, optional location phrase, email domains and run limits.

**2. Build queries.** It composes Google queries with the `site:` operator, for example `site:preply.com spanish tutor "@gmail.com" "Madrid"`.

**3. Fetch search pages.** Requests go out asynchronously with `aiohttp` through the Apify **GOOGLE_SERP** proxy, with retries and a fresh proxy session per attempt.

**4. Parse result blocks.** For each hit the scraper locates the `<h3>` title, walks up to the smallest surrounding block, and reads the title, site label and snippet.

**5. Extract and normalise addresses.** A domain-filtered regex pulls emails out of the block text, then normalisation and the junk filter clean the result.

**6. Deduplicate and push.** Every unique address is written to the dataset immediately, so you can begin exporting mid-run.

Because base queries run before expanded ones, the first rows the Preply Email Scraper writes are usually the highest-signal ones.

#### Why `countryCode` is a real lever on Preply

Preply localises heavily. The same tutor catalogue is indexed under many language paths, and Google's results shift accordingly.

Running `countryCode: "ES"` with Spanish keywords, then `DE` with German keywords, then `BR` with Portuguese ones, reaches parts of the index a single default run never touches.

Treating those as separate Preply Email Scraper runs and merging the exports is usually more productive than one large undifferentiated crawl.

***

### What Data Does the Preply Email Scraper Extract?

The Preply Email Scraper produces exactly one dataset item per unique email, and every item carries the same 14 fields.

Alongside the address you get the account label Google printed, a parsed display name, the tutor handle when Preply exposes one, a canonical tutor profile link, and the snippet the email came from.

You also get full provenance: the keyword and the exact Google query behind the lead, plus a UTC timestamp.

That provenance is practical. It shows which language and subject keywords actually surface contactable tutors in your target market.

Nothing beyond these 14 fields is collected. The Preply Email Scraper reports no lesson prices, no ratings, no student data and nothing behind a login.

***

### Preply Email Scraper Input Schema

Every field below is taken verbatim from the Actor's input schema, including its default value.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["tutor", "language teacher"]` | Search terms describing the Preply accounts you want (language, subject, specialism) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are collected; the leading `@` is optional |
| `maxEmails` | integer (1–10000) | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (`ES`, `DE`, `BR`, `US`…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair with several phrasings |
| `queryModifiers` | array | `["email", "contact", "enroll", "coaching", "workshop"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer (1–50) | `30` | Page cap per query |
| `maxConcurrency` | integer (1–20) | `5` | How many queries run in parallel |

#### JSON input example

```json
{
  "keywords": ["spanish tutor", "business english teacher", "IELTS preparation"],
  "location": "Madrid",
  "customDomains": ["@gmail.com", "@hotmail.com", "@outlook.com"],
  "maxEmails": 250,
  "countryCode": "ES",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "enroll", "coaching", "workshop"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Language-plus-specialism keywords such as `business english teacher` or `DELF preparation tutor` outperform a bare `tutor` by a wide margin.

***

### Preply Email Scraper Output Schema

Every dataset item produced by the Preply Email Scraper contains all 14 fields listed 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 (tutor handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for question or article pages |
| `username` | URL-safe handle when Preply exposes one; otherwise `null` |
| `profileUrl` | Canonical tutor URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or page snippet, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain (e.g. `@gmail.com`) |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email — verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

#### JSON output example

```json
{
  "network": "Preply",
  "keyword": "business english teacher",
  "query": "site:preply.com business english teacher \"@gmail.com\" \"Madrid\"",
  "title": "Elena R. - Business English Tutor | Preply",
  "accountName": "elena-r-8241735",
  "fullName": "Elena R.",
  "username": "elena-r-8241735",
  "profileUrl": "https://preply.com/en/tutor/elena-r-8241735",
  "url": "https://preply.com/en/tutor/elena-r-8241735",
  "description": "Business English and IELTS tutor based in Madrid. Corporate group bookings and workshop enquiries: elena.r.english@gmail.com",
  "email": "elena.r.english@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T10:44:19Z"
}
```

***

### How to Use the Preply Email Scraper

**Step 1 — open the Actor.** Launch the [Preply Email Scraper](https://apify.com/neuro-scraper/preply-email-scraper) on the Apify platform.

**Step 2 — enter language and subject keywords.** Tutors describe themselves by language, exam and niche, so `TOEFL tutor`, `conversational japanese` and `french for kids` beat generic terms.

**Step 3 — set `countryCode`.** This is a genuine lever on Preply: `ES`, `DE`, `FR`, `BR`, `JP` and `TR` each surface a different slice of the index.

**Step 4 — choose email domains.** Start with `@gmail.com`, then add `@hotmail.com`, `@outlook.com` and `@yandex.com` depending on the market you are targeting.

**Step 5 — set `maxEmails` and run.** Leave `expandQueries` on so the Preply Email Scraper can work past Google's per-query ceiling.

**Step 6 — export.** Download the Preply Email Scraper dataset as JSON, CSV or XLSX, or pull it into your CRM through the Apify API.

If you want the children's-education equivalent — group classes rather than one-to-one lessons — the **Outschool Email Scraper** is the closest sibling to this workflow.

***

### Use Cases for the Preply Email Scraper

| Use case | How the Preply Email Scraper helps |
|---|---|
| Tutor recruiting | Source experienced online tutors by language, subject and country |
| Language-school partnerships | Find independent teachers open to corporate or group work |
| Edtech product marketing | Reach tutors who already deliver lessons online and pay for tools |
| Course-platform growth | Recruit tutors to launch structured courses elsewhere |
| Test-prep collaborations | Identify IELTS, TOEFL, DELE and JLPT specialists |
| Corporate training sourcing | Build shortlists of business-language tutors in a target city |
| Affiliate and referral programs | Approach tutors with an existing student audience |
| Market research | Study how tutors position rates, specialisms and availability via `description` snippets |
| CRM enrichment | Attach tutor handles and profile URLs to records you already hold |
| Agency prospecting | Assemble outreach lists for language-learning and edtech clients |

Preply's tutor population is segmented by language and exam far more than by geography, so your keyword choice matters more than your `location` phrase.

In every one of these scenarios the Preply Email Scraper does the tedious part — reading thousands of search results — and leaves judgement to you.

***

### Why Choose This Preply Email Scraper

**It returns real profile links.** Because Preply publishes `/en/tutor/{id}` pages, most rows come with a `profileUrl` you can actually open and verify.

**It is honest about its source.** The Preply Email Scraper reads Google's public index. Nothing more, nothing concealed.

**It is built for an international index.** Locale handling plus `countryCode` targeting make multi-market runs practical.

**It is resilient.** Structural parsing plus a whole-page fallback means a Google layout change degrades output quality instead of breaking the crawler.

**It is part of a family.** The same engine powers sibling Actors across the education category, including the [Udemy Email Scraper](https://apify.com/leads-scraper/udemy-email-scraper) for marketplace instructors and the [Kajabi Email Scraper](https://apify.com/neuro-scraper/kajabi-email-scraper) for independent coaching businesses.

***

### Limitations of the Preply Email Scraper

These are real constraints. Read them before setting expectations.

- **Platform messaging reduces public emails.** Preply keeps tutor contact details private by default and routes students through its own messaging system, so publicly listed addresses are less common than on creator platforms. Expect steady, moderate volume rather than a flood.
- **Only publicly indexed emails.** If an address is not visible in Google's index, the Preply Email Scraper cannot find it. Private data is never accessed.
- **Google's ~300-result cap.** One query returns roughly 300 results at most. Query expansion exists precisely to work around this, so keep `expandQueries` on.
- **`possiblyTruncated`.** When Google's snippet ellipsis touches an address, the flag is set to `true`. Verify those rows before sending.
- **Apify GOOGLE_SERP proxy required.** The Actor cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
- **`username` and `profileUrl` availability.** These are only filled in when Google's result exposes a handle. Rows sourced from Preply's question or article pages will have `accountName` and `fullName` but an empty `username` and `profileUrl`. That is a Google limitation, not a bug.
- **No guaranteed volume.** Results vary with keywords, domains, language and country.

Nothing here is affiliated with, endorsed by or officially supported by Preply.

***

### Related Actors

| Actor | What it collects |
|---|---|
| [Preply Email and Phone Number Scraper](https://apify.com/neuro-scraper/preply-email-and-phone-number-scraper) | Emails and phone numbers from Preply |
| [Preply Phone Number Scraper](https://apify.com/neuro-scraper/preply-phone-number-scraper) | Public phone numbers from Preply |
| [Academia.edu Email Scraper](https://apify.com/neuro-scraper/academia-edu-email-scraper) | Public contact emails from Academia.edu |
| [Buy Me a Coffee Email Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-email-scraper) | Public contact emails from Buy Me a Coffee |
| [Carrd Email Scraper](https://apify.com/neuro-scraper/carrd-email-scraper) | Public contact emails from Carrd |
| [Domestika Email Scraper](https://apify.com/neuro-scraper/domestika-email-scraper) | Public contact emails from Domestika |
| [edX Email Scraper](https://apify.com/leads-scraper/edx-email-scraper) | Public contact emails from edX |
| [Gumroad Email Scraper](https://apify.com/leads-scraper/gumroad-email-scraper) | Public contact emails from Gumroad |
| [Kaggle Email Scraper](https://apify.com/neuro-scraper/kaggle-email-scraper) | Public contact emails from Kaggle |
| [Kajabi Email Scraper](https://apify.com/neuro-scraper/kajabi-email-scraper) | Public contact emails from Kajabi |
| [Ko-fi Email Scraper](https://apify.com/neuro-scraper/ko-fi-email-scraper) | Public contact emails from Ko-fi |
| [Linktree Email Scraper](https://apify.com/leads-scraper/linktree-email-scraper) | Public contact emails from Linktree |
| [MasterClass Email Scraper](https://apify.com/neuro-scraper/masterclass-email-scraper) | Public contact emails from MasterClass |
| [Meetup Email Scraper](https://apify.com/leads-scraper/meetup-email-scraper) | Public contact emails from Meetup |
| [Pluralsight Email Scraper](https://apify.com/leads-scraper/pluralsight-email-scraper) | Public contact emails from Pluralsight |
| [ResearchGate Email Scraper](https://apify.com/neuro-scraper/researchgate-email-scraper) | Public contact emails from ResearchGate |
| [Skillshare Email Scraper](https://apify.com/neuro-scraper/skillshare-email-scraper) | Public contact emails from Skillshare |
| [Teachable Email Scraper](https://apify.com/neuro-scraper/teachable-email-scraper) | Public contact emails from Teachable |
| [Udemy Email Scraper](https://apify.com/leads-scraper/udemy-email-scraper) | Public contact emails from Udemy |
| [Academia.edu Email and Phone Number Scraper](https://apify.com/neuro-scraper/academia-edu-email-and-phone-number-scraper) | Emails and phone numbers from Academia.edu |
| [Buy Me a Coffee Email and Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-email-and-phone-number-scraper) | Emails and phone numbers from Buy Me a Coffee |
| [Carrd Email and Phone Number Scraper](https://apify.com/neuro-scraper/carrd-email-and-phone-number-scraper) | Emails and phone numbers from Carrd |
| [Domestika Email and Phone Number Scraper](https://apify.com/neuro-scraper/domestika-email-and-phone-number-scraper) | Emails and phone numbers from Domestika |
| [edX Email and Phone Number Scraper](https://apify.com/neuro-scraper/edx-email-and-phone-number-scraper) | Emails and phone numbers from edX |
| [Gumroad Email and Phone Number Scraper](https://apify.com/leads-scraper/gumroad-email-and-phone-number-scraper) | Emails and phone numbers from Gumroad |
| [Kaggle Email and Phone Number Scraper](https://apify.com/neuro-scraper/kaggle-email-and-phone-number-scraper) | Emails and phone numbers from Kaggle |
| [Kajabi Email and Phone Number Scraper](https://apify.com/neuro-scraper/kajabi-email-and-phone-number-scraper) | Emails and phone numbers from Kajabi |
| [Ko-fi Email and Phone Number Scraper](https://apify.com/neuro-scraper/ko-fi-email-and-phone-number-scraper) | Emails and phone numbers from Ko-fi |
| [Linktree Email and Phone Number Scraper](https://apify.com/leads-scraper/linktree-email-and-phone-number-scraper) | Emails and phone numbers from Linktree |
| [MasterClass Email and Phone Number Scraper](https://apify.com/neuro-scraper/masterclass-email-and-phone-number-scraper) | Emails and phone numbers from MasterClass |
| [Meetup Email and Phone Number Scraper](https://apify.com/neuro-scraper/meetup-email-and-phone-number-scraper) | Emails and phone numbers from Meetup |
| [Pluralsight Email and Phone Number Scraper](https://apify.com/neuro-scraper/pluralsight-email-and-phone-number-scraper) | Emails and phone numbers from Pluralsight |
| [ResearchGate Email and Phone Number Scraper](https://apify.com/neuro-scraper/researchgate-email-and-phone-number-scraper) | Emails and phone numbers from ResearchGate |
| [Skillshare Email and Phone Number Scraper](https://apify.com/neuro-scraper/skillshare-email-and-phone-number-scraper) | Emails and phone numbers from Skillshare |
| [Teachable Email and Phone Number Scraper](https://apify.com/neuro-scraper/teachable-email-and-phone-number-scraper) | Emails and phone numbers from Teachable |
| [Academia.edu Phone Number Scraper](https://apify.com/neuro-scraper/academia-edu-phone-number-scraper) | Public phone numbers from Academia.edu |
| [Buy Me a Coffee Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-phone-number-scraper) | Public phone numbers from Buy Me a Coffee |
| [Carrd Phone Number Scraper](https://apify.com/neuro-scraper/carrd-phone-number-scraper) | Public phone numbers from Carrd |
| [Domestika Phone Number Scraper](https://apify.com/neuro-scraper/domestika-phone-number-scraper) | Public phone numbers from Domestika |
| [edX Phone Number Scraper](https://apify.com/neuro-scraper/edx-phone-number-scraper) | Public phone numbers from edX |
| [Gumroad Phone Number Scraper](https://apify.com/leads-scraper/gumroad-phone-number-scraper) | Public phone numbers from Gumroad |
| [Kaggle Phone Number Scraper](https://apify.com/neuro-scraper/kaggle-phone-number-scraper) | Public phone numbers from Kaggle |

### Preply Email Scraper Example Run

A corporate language-training provider needs business English tutors across three European markets.

They run the Preply Email Scraper three times — `countryCode: "ES"`, `"DE"` and `"FR"` — each with `keywords: ["business english teacher", "corporate english tutor"]` and `customDomains: ["@gmail.com", "@outlook.com"]`.

Query expansion turns two keywords into a dozen phrasings per run, the Preply Email Scraper paginates through Google, and each dataset fills with tutor handles, bios and addresses.

They merge the three exports, open a sample of `profileUrl` links to confirm specialism, drop rows flagged `possiblyTruncated`, and hand a clean CSV to their recruiting team.

***

### Preply Email Scraper FAQ

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

No. It never logs in, never uses a Preply API and never opens `preply.com`. All data comes from publicly indexed Google search results.

#### Where do the emails actually come from?

From Google result titles, site labels and snippets for pages on `preply.com` — typically tutor profiles and question pages where an address was published publicly.

#### Do Preply tutors publish their email addresses?

Some do, many do not. Preply keeps tutor contact details private and pushes students toward in-platform messaging, so the Preply Email Scraper finds a meaningful but not exhaustive slice of the tutor population.

#### Will I get real profile URLs?

Usually yes. Preply publishes tutor pages at `preply.com/en/tutor/{id}`, so most rows carry a working `profileUrl` alongside the email.

#### Should I set `countryCode`?

On Preply, yes. It is a genuine lever — `ES`, `DE`, `FR`, `BR`, `JP` and `TR` each surface a different slice of the index, so separate runs beat one generic crawl.

#### Is this a Preply email extractor or a full profile scraper?

It is a Preply email extractor. It returns the 14 documented fields and nothing else — no lesson prices, no ratings, no availability calendars.

#### Do I need an Apify proxy?

Yes. The Preply Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

#### How many emails can one run collect?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded only by your `maxEmails` value and what Google has indexed.

#### Why is `username` empty on some rows?

Because Google did not expose a tutor handle in that result — common for Preply's question and article pages. Those rows still carry `accountName`, `fullName` and the snippet.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the email, so the address may be cut off. Verify those rows before sending anything.

#### Should I leave query expansion enabled?

Yes. Google caps a single query at roughly 300 results, and expansion is how the Preply Email Scraper reaches past that ceiling.

#### Does the Preply Email Scraper deduplicate?

Yes, globally. An email appears once per run regardless of how many queries or pages surfaced it.

#### What happens if a run is interrupted?

Progress is stored in the key-value store keyed by a hash of your input and flushed on `PERSIST_STATE`, `MIGRATING` and `ABORTING`, so restarting resumes rather than starting over.

#### Is this affiliated with Preply?

No. The Preply Email Scraper is an independent tool and is not affiliated with, endorsed by or officially supported by Preply.

#### How should I use the results responsibly?

Follow GDPR, CAN-SPAM and any other law that applies to you. Publicly visible does not mean consent to bulk marketing — keep outreach relevant and honour opt-outs.

***

### Leave a review

If the Preply 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, bug reports or a custom build request? Email **neurodata.apify@gmail.com** and include your run ID so the Preply Email Scraper logs can be checked quickly.

# Actor input Schema

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

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

## `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": [
    "tutor",
    "language teacher"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "enroll",
    "coaching",
    "workshop"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Preply 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": [
        "tutor",
        "language teacher"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "enroll",
        "coaching",
        "workshop"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/preply-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": [
        "tutor",
        "language teacher",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "enroll",
        "coaching",
        "workshop",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/preply-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": [
    "tutor",
    "language teacher"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "enroll",
    "coaching",
    "workshop"
  ]
}' |
apify call neuro-scraper/preply-email-scraper --silent --output-dataset

```

## MCP server setup

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