# Instagram Email Scraper (`leads-scraper/instagram-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/instagram-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Categories:**
- **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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Instagram Email Scraper

### Instagram Email Scraper - Extract Public Emails from Instagram Bios by Keyword

The **Instagram Email Scraper** is an Apify Actor that collects publicly indexed contact emails belonging to Instagram accounts. You supply keywords; it returns a structured dataset of leads.

The Instagram Email Scraper works by running `site:instagram.com` searches through the Apify GOOGLE\_SERP proxy and parsing email addresses out of the result blocks. That is the entire mechanism.

The Instagram Email Scraper does **not** log into Instagram, does **not** use Instagram's API and does **not** open instagram.com. No browser, no JavaScript rendering, no authentication, no cookies.

Everything the Instagram Email Scraper returns already exists in Google's public index: titles, snippets and site labels. If a coach wrote `bookings: me@gmail.com` in a bio that Google crawled, the Instagram Email Scraper can find it.

That makes this an **Instagram email extractor** built for keyword-driven contact discovery. You do not need a list of handles to begin - you begin with a niche, a job title or a city.

***

### Key Features

| Feature | What it does |
|---|---|
| Keyword-driven search | Start the Instagram Email Scraper from a niche or job title, not from a list of handles |
| Query expansion | Each keyword x domain pair runs as base, quoted, `intitle:` and one variant per modifier |
| Domain filtering | Only emails on the domains you list (`@gmail.com`, `@yahoo.com`, ...) are kept |
| Obfuscation handling | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width at sign |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` never matches inside `@gmail.company` or `@gmail.com.br` |
| Global deduplication | One row per unique email across every query and every page |
| Concurrency | An `asyncio` worker pool runs several queries in parallel with a shared stop signal |
| Retry logic | 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, never counted as empty |
| Resumable state | Progress lives in the key-value store, keyed by a hash of your input |
| Fallback parser | If Google's markup changes, a run degrades to "emails without account details", not "no emails" |
| Live dataset writes | Each lead is pushed to the Apify dataset the moment it is found |
| Location targeting | An optional location phrase is appended to every query |

The Instagram Email Scraper parser locates each `<h3>` title and then the smallest surrounding block. It does **not** rely on Google's CSS class names, which is why the Instagram Email Scraper survives most SERP layout changes.

***

### How the Instagram Email Scraper Works

The Instagram Email Scraper pipeline is short, deterministic and easy to audit.

1. **Read input.** Keywords, location, email domains and limits are validated.
2. **Build queries.** The Instagram Email Scraper composes `site:instagram.com` queries, e.g. `site:instagram.com fitness coach "@gmail.com" "New York"`.
3. **Expand queries.** Base queries run first, then quoted, `intitle:` and one variant per query modifier.
4. **Fetch search results.** Pages are retrieved asynchronously with `aiohttp` through the Apify GOOGLE\_SERP proxy.
5. **Parse structurally.** Each result block is isolated around its `<h3>` heading.
6. **Extract emails.** A domain-filtered regex pulls addresses from the block text after normalisation.
7. **Deduplicate and push.** Each new lead is written straight to the dataset as structured data.

Pagination per query is capped by `maxPagesPerQuery`. A query also stops early after several consecutive pages with no new email, so the crawler does not waste proxy calls on an exhausted result set.

Blocked or failed queries are re-queued once at the end of the run. The Instagram Email Scraper then logs a summary: pages fetched, blocked pages, retries and emails per page.

***

### What Data Does It Extract?

Every Instagram Email Scraper dataset item pairs an email with whatever account metadata Google exposed, plus full provenance so you can trace where the address came from.

The Instagram Email Scraper captures the handle and canonical profile URL whenever Google's result exposes an `instagram.com/handle` path. On explore, tag and reel pages Google often prints only a display name - in that case `username` is `null` and `profileUrl` is empty.

That is a Google limitation, not a defect. The email, the bio snippet and the account label are still returned.

***

### Input Schema for the Instagram Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["manager", "founder"]` | Search terms describing the accounts you want (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 leading `@` 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", "business inquiries", "collab", "booking", "dm"]` | 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 |

Those default modifiers are tuned for Instagram. `collab`, `booking`, `business inquiries` and `dm` are the exact phrases creators and small businesses type beside an address, which is why the Instagram Email Scraper ships with them.

#### JSON input example

```json
{
  "keywords": ["wedding photographer", "pilates studio", "nail salon"],
  "location": "Chicago",
  "customDomains": ["@gmail.com", "@icloud.com"],
  "maxEmails": 400,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["booking", "business inquiries", "email", "contact"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output Schema and Structured Data Fields

Every item the Instagram Email Scraper writes carries all 14 fields below, so your CSV, XLSX or JSON export always has identical columns.

| 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 post captions |
| `username` | URL-safe handle when Instagram 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 caption snippet, cleaned of labels and engagement 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": "Instagram",
    "keyword": "wedding photographer",
    "query": "site:instagram.com wedding photographer \"booking\" \"@gmail.com\" \"Chicago\"",
    "title": "Elena Marsh (@elenamarshphoto) • Instagram photos and videos",
    "accountName": "elenamarshphoto",
    "fullName": "Elena Marsh",
    "username": "elenamarshphoto",
    "profileUrl": "https://www.instagram.com/elenamarshphoto/",
    "url": "https://www.instagram.com/elenamarshphoto/",
    "description": "Chicago wedding + elopement photographer. Bookings 2026 open. elena.marsh.photo@gmail.com",
    "email": "elena.marsh.photo@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-06-03T11:41:07Z"
  },
  {
    "network": "Instagram",
    "keyword": "pilates studio",
    "query": "site:instagram.com pilates studio \"business inquiries\" \"@gmail.com\"",
    "title": "#pilatesstudio • Instagram photos and videos",
    "accountName": "Instagram",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.instagram.com/explore/tags/pilatesstudio/",
    "description": "business inquiries: hello.corepilates@gmail.com ...",
    "email": "hello.corepilates@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": true,
    "foundAt": "2026-06-03T11:41:52Z"
  }
]
```

The second row is the honest case. Google served a tag page rather than a profile, so no handle exists to build a `profileUrl` from, and the snippet ellipsis touched the address.

***

### How to Use the Instagram Email Scraper in Five Steps

1. **Open the Actor** and confirm your account has Apify proxy access. The GOOGLE\_SERP proxy is required.
2. **Enter 3-10 keywords.** Specific wins: `bridal makeup artist` beats `makeup`.
3. **Choose email domains.** Keep `@gmail.com` and `@yahoo.com`, or add `@icloud.com`, `@outlook.com`, `@hotmail.com`.
4. **Set `maxEmails`.** Start at 20 to check quality, then raise it once the leads look right.
5. **Run, then export.** Download the dataset as CSV, JSON or XLSX, or pull it through the Apify API into your CRM.

Add a `location` when you are prospecting a city with the Instagram Email Scraper. Local service businesses are the single richest vein on this platform.

***

### Instagram Email Scraper Use Cases

| Use case | Who it is for | How the Instagram Email Scraper helps |
|---|---|---|
| Influencer marketing | Brands and agencies | Build an Instagram influencer contact list per niche before outreach |
| Local service prospecting | SMMA and web agencies | Combine `salon`, `dentist` or `gym` with a `location` for citywide lists |
| UGC creator sourcing | DTC e-commerce | Find creators already advertising `collab` and `dm` addresses |
| Wedding and events sales | Venues, planners, rentals | Reach photographers, florists and MUAs who publish booking emails |
| Real estate outreach | Brokerages and proptech | Collect agent emails per metro area |
| Coach and consultant outreach | B2B SaaS founders | Target `business coach`, `nutritionist`, `career coach` bios |
| Talent scouting | Management agencies | Discover unsigned creators publishing contact details |
| CRM enrichment | RevOps teams | Feed structured data directly into an existing pipeline |

Cross-network campaigns are common here. Pair this Actor with the [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) and the [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) - most Instagram-first businesses maintain all three.

***

### Why Use This Actor for Instagram Contact Discovery

Most Instagram email extractor tools want a list of profiles as input. The Instagram Email Scraper inverts that: it starts from intent, expands a query set and returns whoever matches.

Because the Instagram Email Scraper never touches Instagram itself, there is no login, no API quota and no session to maintain. Its only dependency is Apify's search proxy.

The extraction layer is where the value sits. Normalisation, obfuscation handling, the junk filter, boundary-correct domain matching and soft-wrap repair strip out most of the noise naive regex email scraping produces.

Soft-wrap repair matters more on Instagram than elsewhere: bios wrap constantly, and the Instagram Email Scraper drops a hit that is only the tail of another address in the same block rather than emitting a broken duplicate.

***

### Limitations

Read this before planning a campaign around the Instagram Email Scraper.

- **Public index only.** It finds accounts whose email is publicly visible in Google's index. Addresses behind the Instagram contact button, inside link-in-bio pages or rendered in images are out of reach.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most. Query expansion exists precisely to work around that ceiling, so keep `expandQueries` on for volume.
- **`possiblyTruncated`.** When Google's snippet ellipsis touched an address, the row is flagged. Verify those rows before sending.
- **Handle availability.** `username` and `profileUrl` are populated only when Google's result exposes a handle. Display-name-only results still return `accountName` and `fullName`.
- **Apify proxy required.** The Instagram Email Scraper cannot run without Apify GOOGLE\_SERP proxy credentials.
- **Free-plan cap.** Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
- **No volume guarantee.** Results vary with keywords, domains, location and what Google has indexed. Nothing is guaranteed, verified or real-time.

The Instagram Email Scraper is not affiliated with, endorsed by or officially supported by Instagram or Meta. Use the output in line with GDPR, CAN-SPAM and local marketing law.

***

### Related Actors

The Instagram Email Scraper shares its engine and output schema with every Actor below, all part of the Social, Creator & Community family.

| Actor | What it collects |
|---|---|
| [Instagram Email and Phone Number Scraper](https://apify.com/leads-scraper/instagram-email-and-phone-number-scraper) | Emails and phone numbers from Instagram |
| [Instagram Phone Number Scraper](https://apify.com/leads-scraper/instagram-phone-number-scraper) | Public phone numbers from Instagram |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder |
| [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### Example: Building a Citywide Wedding Vendor List

Here is a realistic Instagram Email Scraper run. You want 250 wedding vendors in Chicago with a Gmail or iCloud address in the bio.

Set `keywords` to `["wedding photographer", "wedding florist", "bridal makeup artist"]`, `location` to `Chicago`, `customDomains` to `["@gmail.com", "@icloud.com"]` and `maxEmails` to `250`.

The Instagram Email Scraper builds base, quoted, `intitle:` and modifier variants per keyword, then paginates the search results with five parallel workers. Leads stream into the dataset live, so you can abort early if the niche is wrong.

Sort the Instagram Email Scraper dataset by `possiblyTruncated`, hand-verify the flagged rows, then load the rest into your sequencer. Re-run the same input on the [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) to catch vendors who publish contact details on a Page instead.

***

### Instagram Email Scraper FAQ

**Does the Instagram Email Scraper log into Instagram?**
No. It never authenticates, never opens instagram.com and never uses Instagram's API. Every field comes from Google's public search results.

**Where do the Instagram Email Scraper emails actually come from?**
From titles, snippets and site labels Google already publishes for indexed Instagram pages - typically bios and captions where the account owner wrote the address themselves.

**Can it read emails behind the Instagram contact button?**
No. If the address is not in Google's index, the Instagram Email Scraper cannot see it. That is the honest boundary of a SERP-based approach.

**Why do some rows have no `username` or `profileUrl`?**
Because Google's result exposed only a display name, usually on explore, tag or reel pages. Those rows still include `accountName`, `fullName`, the email and the snippet.

**What does `possiblyTruncated: true` mean?**
Google's snippet ellipsis touched the address, so it may be cut short. Treat those as leads to verify rather than send-ready contacts.

**How many emails can one Instagram Email Scraper run return?**
Free Apify plans stop at 100 emails per run. Paid plans are uncapped and bounded only by `maxEmails` and what Google has indexed.

**Why does a single query not return thousands of results?**
Google caps one query at roughly 300 results. Query expansion is the built-in workaround, multiplying keyword x domain x phrasing so the Instagram Email Scraper reaches past that ceiling.

**Do I need a proxy to run the Instagram Email Scraper?**
Yes. It requires the Apify GOOGLE\_SERP proxy and will not run without Apify proxy credentials.

**Can I target a city or country?**
Yes. Use `location` for a phrase appended to every query, and `countryCode` for the search proxy's country.

**Which email domains work best on Instagram?**
Personal domains dominate: `@gmail.com` first, then `@icloud.com`, `@outlook.com` and `@hotmail.com`. Add a business domain if you are chasing agencies.

**Can I resume an interrupted run?**
Yes. Progress is saved in the key-value store, keyed by a hash of your input, and persists on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

**Is scraping Instagram emails legal?**
The Actor collects only publicly indexed information, but how you use it is your responsibility. Follow GDPR, CAN-SPAM and local rules on unsolicited outreach.

**How do I get more leads from one niche?**
Add query modifiers, widen `customDomains`, raise `maxPagesPerQuery` and run neighbouring keywords instead of a single broad term.

***

### Support

Questions about the Instagram Email Scraper, bug reports or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Instagram 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": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/instagram-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": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/instagram-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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ]
}' |
apify call leads-scraper/instagram-email-scraper --silent --output-dataset

```

## MCP server setup

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