# edX Email Scraper (`leads-scraper/edx-email-scraper`) Actor

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

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

### edX Email Scraper — public emails from indexed course and institution pages

The **edX Email Scraper** searches publicly indexed `edx.org` pages with Google's `site:` operator and extracts contact emails from the titles and snippets it finds.

Everything runs through the Apify GOOGLE_SERP proxy. There is no login, no edX API, no browser and no cookies.

**Understand the shape of the data first.** edX publishes **course and institution pages** rather than personal instructor profiles. Most rows this Actor returns therefore carry a **course or school name** instead of a personal handle.

In practice that means `accountName` often holds an institution or programme label, `fullName` is empty, and both `username` and `profileUrl` are frequently `null` and `""`. The email and the snippet are still real.

That makes the edX Email Scraper a tool for **institution-level and programme-level contact discovery** — partner enquiry addresses, programme support lines, departmental contacts printed in a course description — rather than a directory of named instructors.

***

### Quick start with the edX Email Scraper

1. Open the edX Email Scraper on Apify and enter programme-style keywords such as `professional certificate data analysis`.
2. Add every email domain you are willing to accept to `customDomains`, including institutional ones.
3. Set `maxEmails` to a realistic ceiling and start the run.
4. Export the dataset as CSV, JSON or Excel once it finishes.

The edX Email Scraper streams rows into the dataset as it finds them, so you can tell within a minute whether a keyword is matching catalogue copy or real contact lines.

Expect institution-level rows: that is what the edX Email Scraper is good at, and it is what edX publishes.

***

### What the edX Email Scraper actually does

The edX Email Scraper does **not** log into edX, does not use an edX API, and does not open the edX website. No browser, no JavaScript rendering, no authentication.

All data comes from **publicly indexed Google search results**: the result title, the site label and the snippet Google prints.

A generated query looks like `site:edx.org professor department contact "@gmail.com"`. Result pages are fetched asynchronously with `aiohttp` through the search proxy.

Parsing is **structural** — the edX Email Scraper locates the `<h3>` title and then the smallest surrounding block, rather than depending on Google's CSS class names.

***

### Key features of the edX Email Scraper

| Feature | What it means in practice |
|---|---|
| Google `site:` targeting | Every query is scoped to `edx.org` |
| Query expansion | Base, quoted and `intitle:` phrasings plus one variant per modifier; base queries run first |
| Course-oriented modifiers | Defaults include `enroll`, `coaching` and `workshop` |
| Domain filtering | Only emails ending in one of your `customDomains` survive |
| Global deduplication | Each unique address is pushed 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 `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another address in the same block |
| Async concurrency | `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries | Up to 3 attempts per page, exponential backoff, fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty |
| Re-queue | Blocked or failed queries are retried once at the end of the run |
| Resumable state | Key-value store state keyed by a hash of the input; saves fire on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Whole-page fallback parser | A Google layout change degrades to "emails without account details", not "no emails" |
| Truncation flag | `possiblyTruncated` marks addresses touched by Google's snippet ellipsis |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

***

### How the edX Email Scraper works

1. Reads the input: keywords, location, allowed email domains and run limits.
2. Builds Google queries with `site:edx.org`, one per keyword × domain × phrasing.
3. Fetches result pages through the Apify GOOGLE_SERP proxy.
4. Locates each result block structurally and extracts the title, institution label and snippet.
5. Applies the domain-filtered regex, normalisation and junk filtering to the block text.
6. Deduplicates globally and pushes each lead straight to the dataset.

Because the edX Email Scraper writes rows as it finds them, you can inspect early results and stop the run if the keyword is producing course marketing copy rather than contact lines.

***

### Input reference for the edX Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["instructor", "professor"]` | Search terms (subject, programme, job title) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; `@` 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 × domain in 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` | Parallel queries |

#### Example input

```json
{
  "keywords": ["micromasters supply chain", "computer science professor", "professional certificate cybersecurity"],
  "location": "",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com"],
  "maxEmails": 60,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "enroll", "coaching", "workshop"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Programme names — MicroMasters, professional certificate, executive education — work better as edX Email Scraper keywords than bare job titles, because that is the language edX pages actually use.

***

### Output fields from the edX Email Scraper

Every dataset item produced by the edX Email Scraper contains 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 — on edX usually a school, partner or programme name |
| `fullName` | Display name parsed from a profile-style title; empty for course and institution titles |
| `username` | URL-safe handle when edX 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` | Snippet text, 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 |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example output

The first row is the ordinary edX case — an institution-level address with no personal handle behind it. The second row shows the rarer case where a bio page did expose one.

```json
[
  {
    "network": "edX",
    "keyword": "micromasters supply chain",
    "query": "site:edx.org micromasters supply chain contact \"@gmail.com\"",
    "title": "Supply Chain Analytics MicroMasters Program | edX",
    "accountName": "edX",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "... Programme admissions and cohort enquiries: scm.programme.office@gmail.com. Enrol now ...",
    "email": "scm.programme.office@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T13:15:52.310Z"
  },
  {
    "network": "edX",
    "keyword": "computer science professor",
    "query": "site:edx.org intitle:\"computer science professor\" email \"@yahoo.com\"",
    "title": "Ravi Subramanian | edX",
    "accountName": "ravi-subramanian",
    "fullName": "Ravi Subramanian",
    "username": "ravi-subramanian",
    "profileUrl": "https://www.edx.org/bio/ravi-subramanian",
    "url": "https://www.edx.org/bio/ravi-subramanian",
    "description": "Lecturer in computer science. Course correspondence: r.subramanian.cs@yahoo.com",
    "email": "r.subramanian.cs@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T13:16:21.774Z"
  }
]
```

***

### Use cases for the edX Email Scraper

edX Email Scraper data is institution-shaped, so the use cases that work are the ones aimed at programmes and schools rather than named individuals.

| Use case | How the edX Email Scraper helps |
|---|---|
| University partner and programme outreach | Snippets often carry a programme office or admissions address |
| EdTech B2B prospecting | `accountName` and `title` identify the partner institution |
| Curriculum and competitor research | Course descriptions summarise positioning and level |
| Corporate learning and L\&D sourcing | Find programmes matching a skills gap, then contact the listed address |
| Academic content partnerships | Reach the programme contact printed on the course page |
| Accreditation and credential research | Professional certificate pages name the awarding body |
| Regional programme mapping | Add a `location` phrase to bias toward institutions in a region |
| Multi-platform education list building | Merge edX Email Scraper rows with sibling Actors for coverage |

Where an address belongs to an academic and appears alongside their published course material, it was published so that learners and peers could write about that material. Keep your message relevant to it.

Every address here is personal or organisational data under **GDPR** and comparable laws. Have a lawful basis, identify yourself, respect institutional contact norms, and act on opt-outs immediately.

For creator-published contact details in higher volume, see the [Udemy Email Scraper](https://apify.com/leads-scraper/udemy-email-scraper) and the [Teachable Email Scraper](https://apify.com/neuro-scraper/teachable-email-scraper); for scholarly correspondence lines, the [ResearchGate Email Scraper](https://apify.com/neuro-scraper/researchgate-email-scraper) and the [Academia.edu Email Scraper](https://apify.com/neuro-scraper/academia-edu-email-scraper) are the better sources.

***

### Getting better runs from the edX Email Scraper

Use programme vocabulary in the edX Email Scraper. `MicroMasters`, `professional certificate` and `executive education` match how edX titles its pages; `instructor` does not.

Broaden `customDomains` early in the edX Email Scraper. Institutional pages often print a departmental address on a university domain rather than a consumer one, so add those domains explicitly if you want them.

Leave `expandQueries` on. Google caps one query at roughly 300 results, and the modifier variants are how the edX Email Scraper widens coverage.

Keep `maxEmails` realistic. The edX Email Scraper reads a course-catalogue index, not a contact directory, and a modest ceiling gives you a clean, quick run.

***

### Limitations of the edX Email Scraper

- **edX publishes course and institution pages rather than personal instructor profiles, so most rows carry a course or school name instead of a handle.** Expect empty `fullName`, `username: null` and `profileUrl: ""` on the majority of rows.
- The edX Email Scraper only finds addresses that are **publicly visible in Google's index**.
- Google caps a single query at roughly **300 results**, which is exactly why query expansion exists.
- `username` and `profileUrl` populate only when Google's result exposes a handle. This is a Google limitation, not a bug.
- `possiblyTruncated: true` means Google's snippet ellipsis touched the address — verify it before sending.
- Requires the **Apify GOOGLE_SERP proxy**; the edX Email Scraper cannot run without Apify proxy credentials.
- **Free Apify plans are capped at 100 emails per run.** Paid plans are uncapped.
- Results vary with keywords, domains and location, and no volume is guaranteed.

***

### edX Email Scraper FAQ

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

No volume is guaranteed, and this is not a high-yield platform. edX pages are catalogue entries, so only a minority print a contact address at all. Run several programme-style keywords with a wide domain list and treat `maxEmails` as a ceiling rather than a forecast.

#### Why are `username` and `profileUrl` usually empty?

Because the indexed pages are courses and institution listings, not personal profiles. With no handle in Google's result there is nothing to build a profile URL from, so the edX Email Scraper writes `null` and an empty string instead of guessing.

#### Why does `accountName` show a school instead of a person?

That is the label Google prints for these pages, and the edX Email Scraper reports it verbatim. On edX the account-level identity is usually the partner institution or the programme, which is exactly what the field reports.

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

No. It does not log in, use an edX API, or open the edX website. It reads Google search results only.

#### Can I collect university domain addresses?

Yes. Add the domains you want — for example a specific university domain — to the edX Email Scraper's `customDomains` list, and only matching addresses are kept.

#### What does `possiblyTruncated` mean?

The edX Email Scraper flags a row when Google's ellipsis cut the snippet where the address sits, so the captured value may be incomplete. Keep those rows aside and verify them.

#### Do I need Apify proxy credentials?

Yes. The GOOGLE_SERP proxy is required and the edX Email Scraper cannot run without it.

#### Why is `expandQueries` enabled by default?

Because one Google query returns roughly 300 results at most. Expansion adds quoted, `intitle:` and modifier phrasings so the edX Email Scraper reaches more of the index.

#### Will a run resume after a migration?

Yes. The edX Email Scraper keeps state in the key-value store keyed by a hash of your input, with saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING`.

#### What if Google changes its markup?

The edX Email Scraper parses structurally with a whole-page fallback, so a layout change degrades the run to "emails without account details" rather than returning nothing.

#### Is using this compliant with privacy law?

The edX Email Scraper reads only publicly indexed pages, but the addresses are still personal data. Under GDPR and similar regimes you need a lawful basis, clear identification and a working opt-out.

#### Can I export the dataset?

Yes. The edX Email Scraper dataset exports to JSON, CSV, Excel and the other Apify formats, and is reachable through the Apify API.

***

### Related Actors

| Actor | What it collects |
|---|---|
| [edX Email and Phone Number Scraper](https://apify.com/neuro-scraper/edx-email-and-phone-number-scraper) | Emails and phone numbers from edX |
| [edX Phone Number Scraper](https://apify.com/neuro-scraper/edx-phone-number-scraper) | Public phone numbers from edX |
| [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 |
| [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 |
| [Preply Email Scraper](https://apify.com/neuro-scraper/preply-email-scraper) | Public contact emails from Preply |
| [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 |
| [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 |
| [Preply Email and Phone Number Scraper](https://apify.com/neuro-scraper/preply-email-and-phone-number-scraper) | Emails and phone numbers from Preply |
| [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 |
| [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 |
| [Kajabi Phone Number Scraper](https://apify.com/neuro-scraper/kajabi-phone-number-scraper) | Public phone numbers from Kajabi |

### Leave a review

If the edX 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? Email **neurodata.apify@gmail.com** with your keywords, domain list and the result you were expecting.

# Actor input Schema

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

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

## `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": [
    "instructor",
    "professor"
  ],
  "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 edX 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": [
        "instructor",
        "professor"
    ],
    "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("leads-scraper/edx-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": [
        "instructor",
        "professor",
    ],
    "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("leads-scraper/edx-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": [
    "instructor",
    "professor"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "enroll",
    "coaching",
    "workshop"
  ]
}' |
apify call leads-scraper/edx-email-scraper --silent --output-dataset

```

## MCP server setup

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