# Academia.edu Email Scraper (`neuro-scraper/academia-edu-email-scraper`) Actor

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

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

### Academia.edu Email Scraper — emails published inside academic papers

The **Academia.edu Email Scraper** finds contact emails that appear on publicly indexed `academia.edu` pages and returns them as a structured Apify dataset.

It works entirely through Google's `site:` operator over the Apify GOOGLE_SERP proxy — no login, no Academia.edu API, no browser.

**Set your expectations before the first run.** Most indexed Academia.edu pages are **papers, not author profiles**. The emails this Actor finds usually come from the paper text itself — an affiliation block, an acknowledgements line, a corresponding-author footnote — and those pages carry no profile URL.

So a typical row from the Academia.edu Email Scraper has a valid `email`, a useful `description` snippet, and `username: null` with `profileUrl: ""`. That is honest output, not a failure.

Read that as the product definition: this is a tool for harvesting **author contact addresses printed in scholarly documents**, not a directory of Academia.edu member profiles.

***

### Quick start with the Academia.edu Email Scraper

1. Open the Academia.edu Email Scraper on Apify and enter one or two precise disciplinary keywords.
2. Add every email domain you are willing to accept to `customDomains`.
3. Set `maxEmails` to a realistic ceiling and start the run.
4. Export the dataset as CSV, JSON or Excel when it finishes.

The Academia.edu Email Scraper streams rows into the dataset as it finds them, so the first few results already tell you whether the keyword is working.

If a run comes back thin, widen the domain list before you change anything else.

***

### What the Academia.edu Email Scraper actually does

The Academia.edu Email Scraper does **not** log into Academia.edu, does not use an Academia.edu API, and does not open the Academia.edu website. There is no browser, no JavaScript rendering, no authentication and no cookies.

All data comes from **publicly indexed Google results** — the title, the site label, and the snippet Google prints beneath each link.

A query built by the Academia.edu Email Scraper looks like `site:academia.edu lecturer "corresponding author" "@gmail.com"`. Result pages are fetched asynchronously with `aiohttp` and parsed block by block.

Parsing is **structural**: the Academia.edu Email Scraper locates the `<h3>` title and then the smallest surrounding container. It does not rely on Google's CSS class names, so markup changes degrade the run instead of breaking it.

***

### Key features of the Academia.edu Email Scraper

| Feature | What it means in practice |
|---|---|
| Google `site:` targeting | Every query is scoped to `academia.edu` |
| Query expansion | Base, quoted and `intitle:` phrasings plus one variant per modifier; base queries run first |
| Scholarly modifiers | Defaults include `corresponding author`, `department` and `university` |
| Domain filtering | Only emails ending in one of your `customDomains` are kept |
| Global deduplication | Each unique address is written to the dataset once |
| Email normalisation | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Drops 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 block |
| Async concurrency | `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries | 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 treated as empty |
| Re-queue | Blocked or failed queries get one more attempt 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 Academia.edu Email Scraper works

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

Leads appear in the dataset while the Academia.edu Email Scraper is still running, so you can inspect the first rows and abort early if the keyword is wrong.

***

### Input reference for the Academia.edu Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["researcher", "lecturer"]` | Search terms (discipline, job title, topic) |
| `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","corresponding author","department","university"]` | 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": ["sociology lecturer", "archaeology conference paper"],
  "location": "",
  "customDomains": ["@gmail.com", "@yahoo.com", "@hotmail.com"],
  "maxEmails": 250,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "corresponding author", "department", "university"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Because Academia.edu hosts a great deal of work from institutions without central email hosting, personal consumer domains are common in the paper text. That is why they are the Academia.edu Email Scraper's defaults.

***

### Output fields from the Academia.edu Email Scraper

Every dataset item written by the Academia.edu 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 (handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for paper titles |
| `username` | URL-safe handle when Academia.edu 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 dominant shape on this platform: an email lifted from the body of a paper, with nothing to hang a profile URL on.

```json
[
  {
    "network": "Academia.edu",
    "keyword": "archaeology conference paper",
    "query": "site:academia.edu archaeology conference paper \"corresponding author\" \"@gmail.com\"",
    "title": "(PDF) Ceramic assemblages of the middle Danube: a reassessment",
    "accountName": "Academia.edu",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "... Department of Prehistory. Correspondence: m.varga.arch@gmail.com. Paper presented at ...",
    "email": "m.varga.arch@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:04:19.226Z"
  },
  {
    "network": "Academia.edu",
    "keyword": "sociology lecturer",
    "query": "site:academia.edu intitle:\"sociology lecturer\" \"@yahoo.com\"",
    "title": "Daniel Osei | Independent Researcher - Academia.edu",
    "accountName": "DanielOsei",
    "fullName": "Daniel Osei",
    "username": "DanielOsei",
    "profileUrl": "https://independent.academia.edu/DanielOsei",
    "url": "https://independent.academia.edu/DanielOsei",
    "description": "Sociology lecturer researching urban migration. Contact: d.osei.socio@yahoo.com",
    "email": "d.osei.socio@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:04:51.903Z"
  }
]
```

***

### Use cases for the Academia.edu Email Scraper

An author prints their address in a paper so that readers can write to them about that paper. Every good use of the Academia.edu Email Scraper starts from that premise.

| Use case | How the Academia.edu Email Scraper helps |
|---|---|
| Writing to authors about their work | Surfaces addresses from corresponding-author and affiliation lines |
| Building a discipline-specific scholarly contact list | Keyword and domain filters keep the list focused |
| Call-for-papers and special-issue invitations | Target authors already publishing on the theme |
| Finding thesis and preprint authors | Academia.edu indexes a lot of grey literature |
| Requesting datasets or replication material | The snippet usually names the study |
| Recruiting peer reviewers | Match a narrow methods keyword |
| Academic conference outreach | Add a `location` phrase for regional events |
| Scholarly publishing and tooling marketing | Reach researchers whose published methods fit your product |

Bulk commercial blasting to addresses harvested with the Academia.edu Email Scraper is not on that list. It is the fastest way to get your domain blocked by university mail filters.

For adjacent sources, the [ResearchGate Email Scraper](https://apify.com/neuro-scraper/researchgate-email-scraper) covers publication records and question threads, and the [Kaggle Email Scraper](https://apify.com/neuro-scraper/kaggle-email-scraper) covers applied data-science authors.

***

### Getting more from the Academia.edu Email Scraper

Discipline-plus-method keywords outperform job titles in the Academia.edu Email Scraper. `lecturer` is noise; `mixed methods qualitative interviews` finds real papers.

Widen `customDomains` before you widen keywords. On paper pages, the domain list is what decides whether an address survives the Academia.edu Email Scraper's filtering.

Keep `expandQueries` on. A single Google query tops out at roughly 300 results, and expansion is the only route past that.

Use `countryCode` when your outreach is regional — it changes the country the Academia.edu Email Scraper searches from, which shifts which papers surface.

***

### Limitations of the Academia.edu Email Scraper

- **Most indexed Academia.edu pages are papers rather than author profiles.** Emails often come from the paper text itself, with no profile URL, so many rows have `username: null` and `profileUrl: ""`.
- The Academia.edu Email Scraper only finds addresses that are **publicly visible in Google's index**. Anything behind an Academia.edu login is invisible.
- Google caps a single query at roughly **300 results** — the reason query expansion exists.
- `username` and `profileUrl` are populated only when Google's result exposes a handle. This is a Google limitation, not a bug.
- `possiblyTruncated: true` means the snippet ellipsis touched the address; verify before sending.
- Requires the **Apify GOOGLE_SERP proxy**. The Academia.edu 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.
- Compliance is yours. Author emails are personal data under **GDPR** and comparable laws, and institutions publish their own norms on unsolicited contact. Keep messages relevant to the recipient's published work, identify yourself, and act on opt-outs at once.

***

### Academia.edu Email Scraper FAQ

#### How many results should I expect from the Academia.edu Email Scraper?

No volume is guaranteed, and yield swings widely with the keyword. A tight disciplinary phrase plus two consumer domains may return a few dozen addresses; a broad discipline with several domains and expansion enabled returns considerably more. Treat `maxEmails` as a ceiling, not a forecast.

#### Why are `username` and `profileUrl` empty on most rows?

Because Google mostly indexes Academia.edu **paper** pages, not profile pages. A paper page exposes no handle, so the Academia.edu Email Scraper writes `null` and an empty string rather than guessing a profile URL.

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

The Academia.edu Email Scraper reads the snippet and title text of Google's results — in practice, corresponding-author footnotes, affiliation blocks and acknowledgements printed inside the paper.

#### Does it log into Academia.edu?

No. The Academia.edu Email Scraper does not log in, does not use an Academia.edu API, and does not open the site. It reads Google results only.

#### Can I target institutional domains?

Yes. Add `@ac.uk`, `@edu.au` or any specific university domain to the Academia.edu Email Scraper's `customDomains` list and only those addresses are kept.

#### What does `possiblyTruncated` mean?

The Academia.edu Email Scraper sets that flag when Google's ellipsis cut the snippet where the address sits, so the captured string may be incomplete. Keep those rows separate and verify them.

#### Do I need Apify proxy credentials?

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

#### Why leave `expandQueries` enabled?

One Google query returns about 300 results at most. Expansion adds quoted, `intitle:` and modifier variants so the Academia.edu Email Scraper covers far more of the index.

#### Does the run resume after a migration?

Yes. The Academia.edu Email Scraper keeps state in the key-value store keyed by a hash of the input, and saves fire on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

#### Is this legal to use?

The Academia.edu Email Scraper reads only publicly indexed pages, but the addresses remain personal data. Under GDPR and similar laws you need a lawful basis, clear identification and a working opt-out, and you should respect institutional contact policies.

#### What happens if Google changes its result markup?

The Academia.edu Email Scraper parses structurally rather than by CSS class, with a whole-page fallback. The run degrades to "emails without account details" instead of returning nothing.

#### Can I export the dataset?

Yes. The Academia.edu 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 |
|---|---|
| [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 |
| [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 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 |
| [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 |
| [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 |
| [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 |
| [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 |
| [Kajabi Phone Number Scraper](https://apify.com/neuro-scraper/kajabi-phone-number-scraper) | Public phone numbers from Kajabi |

### Leave a review

If the Academia.edu 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

Need help, found a bug, or want a custom build? Email **neurodata.apify@gmail.com** with your keywords, domain list and what you expected to see.

# Actor input Schema

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

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

## `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": [
    "researcher",
    "lecturer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "corresponding author",
    "department",
    "university"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Academia.edu 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": [
        "researcher",
        "lecturer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "corresponding author",
        "department",
        "university"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/academia-edu-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": [
        "researcher",
        "lecturer",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "corresponding author",
        "department",
        "university",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/academia-edu-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": [
    "researcher",
    "lecturer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "corresponding author",
    "department",
    "university"
  ]
}' |
apify call neuro-scraper/academia-edu-email-scraper --silent --output-dataset

```

## MCP server setup

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