# Likee Email Scraper (`leads-scraper/likee-email-scraper`) Actor

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

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

### Likee Email Scraper — public short-video creator emails

The **Likee Email Scraper** is an Apify Actor that collects publicly indexed contact emails belonging to Likee creators and influencers. Keywords go in; a clean lead dataset comes out.

**Set expectations first.** Likee indexes fewer public profile pages than the major video platforms, so expect lower volume than a TikTok or YouTube run. This is a real ceiling, not a tuning problem.

What the Likee Email Scraper gives you instead is reach into audiences the big influencer databases barely cover — short-video creators across Southeast Asia, the Middle East, Russia and Latin America.

If you have ever hand-run `site:likee.video "gmail.com" collab` and pasted the hits into a sheet, the Likee Email Scraper is that workflow automated, deduplicated and exported as JSON or CSV.

The Likee Email Scraper never logs into Likee, never uses the Likee API and never opens likee.video. Every field comes from publicly available Google search results across `likee.video` and `likee.com`.

#### Who it is for

- Mobile app marketers running install campaigns in emerging markets
- Regional brands recruiting micro-influencers outside the TikTok mainstream
- Music labels seeding tracks with lip-sync and dance creators
- Talent agencies scouting short-video performers
- Localisation and regional agencies building a likee creator contact list
- Researchers studying short-video ecosystems beyond TikTok

***

### Key features

Everything in the Likee Email Scraper feature list below is implemented in code — nothing here is aspirational.

| Feature | What it does |
|---|---|
| Multi-domain `site:` search | Queries both `likee.video` and `likee.com` in a single run |
| Query expansion | Base, quoted and `intitle:` variants plus one query per modifier |
| Query modifiers | Defaults tuned for Likee: `email`, `contact`, `business inquiries`, `collab`, `booking`, `dm` |
| Domain filtering | Keeps only emails on the mailbox domains you list, e.g. `@gmail.com` |
| Global deduplication | One row per unique email across every query and every page |
| Email normalisation | Understands `name [at] domain [dot] com`, `(at)`, `name @ domain.com`, `＠` and zero-width characters |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Country targeting | `countryCode` points the search proxy at a specific Google locale — useful for ID, PH, AE, BR |
| Concurrency | An `asyncio` worker pool runs several queries in parallel |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Resumable state | Run state lives in the key-value store and survives migration |
| Fallback parser | If Google's markup changes, output degrades to emails-without-details, not zero rows |
| Streaming dataset | Each lead is pushed to the Apify dataset the moment it is found |

***

### How the Likee Email Scraper works

The Likee Email Scraper uses no browser, no JavaScript rendering, no authentication and no cookies. The pipeline is deliberately simple.

**1. Read the input.** Keywords, location, email domains and limits are loaded from the Actor input.

**2. Build the queries.** Each keyword is combined with each email domain and a `site:` operator per Likee domain, for example:

```
site:likee.video influencer "@gmail.com" "Jakarta" collab
```

**3. Expand the query set.** With `expandQueries` on, every keyword × domain pair also runs quoted, as `intitle:`, and once per modifier. Base queries run first, so the strongest search results arrive early.

**4. Fetch through the proxy.** Result pages are requested asynchronously with `aiohttp` through the Apify **GOOGLE\_SERP** proxy, paginating up to `maxPagesPerQuery`.

**5. Parse structurally.** The parser locates each `<h3>` title and walks up to the smallest surrounding block. It does **not** depend on Google's CSS class names, which change often.

**6. Extract and clean.** A domain-filtered regex pulls emails from the block text. Soft-wrap repair drops a hit that is only the tail of another address in the same block.

**7. Deduplicate and push.** Emails are deduplicated globally and written straight to the dataset. The run stops once `maxEmails` unique addresses exist.

Blocked or failed queries are re-queued once at the end of the run, so a temporary block does not quietly cost you leads — which matters more here, where every indexed page counts.

***

### What data does the Likee Email Scraper extract?

Every dataset item the Likee Email Scraper produces carries the same 14 fields — flat structured data, no nesting, ready for a CRM import or a spreadsheet.

`accountName` is the label Google prints, usually the creator's handle or display name. `fullName` is filled when the title parses as a profile-style name and is often empty for individual video pages.

The `description` field holds the bio or caption snippet, cleaned of labels and engagement counters — enough to tell a dance creator from a comedy account before you write.

Because the Likee Email Scraper stores the originating `keyword` and `query` on every row, you can see which searches actually produced leads and drop the ones that did not — essential when the indexed surface is thin.

***

### Input fields

The input schema is small on purpose. These nine fields are the entire configuration surface of the Likee Email Scraper.

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["creator", "influencer"]` | Search terms: niche, content type or role |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional |
| `maxEmails` | integer 1–10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (ID, PH, AE, BR…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain 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` | Pagination cap per query |
| `maxConcurrency` | integer 1–20 | `5` | Parallel queries |

Given the smaller indexed surface, keyword *breadth* pays here. Give the Likee Email Scraper six or eight keyword variants rather than betting on one.

***

### Output fields and dataset structure

The output schema of the Likee Email Scraper is fixed. Every row carries all 14 fields below, so downstream parsing never has to guess.

| 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 video captions |
| `username` | URL-safe handle when Likee exposes one; otherwise `null` |
| `profileUrl` | Canonical Likee profile URL when a handle is known; otherwise empty |
| `url` | Direct Likee 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 |
| `foundAt` | ISO 8601 UTC timestamp |

Export the Likee Email Scraper dataset as JSON, CSV, Excel or XML from the Apify console, or read it through the API.

***

### How to use the Likee Email Scraper

Running the Likee Email Scraper takes about a minute of setup.

1. Open the **Likee Email Scraper** on Apify and click **Try for free**.
2. Replace the default keywords with your niche — `dance creator`, `comedy`, `beauty`, `lip sync`.
3. Set `customDomains`. `@gmail.com` alone is the highest-yield single choice; add regional providers if you target a specific market.
4. Set `location` and `countryCode` to your target market — `ID`, `PH`, `AE`, `RU` or `BR` are the usual candidates.
5. Raise `maxEmails`, then press **Start**.
6. Watch the log — it reports pages fetched, blocked pages, retries and emails per page.
7. Export the dataset, or schedule the Actor to re-run and append fresh leads as more pages get indexed.

**Tip:** because Likee's indexed surface is small, treat this as a *supplement*. Run it alongside the [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) and [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) to cover the same short-video and live audiences from three angles.

***

### Use cases and lead generation workflows

Teams use the Likee Email Scraper when contact discovery in emerging short-video markets is the bottleneck. It works as a one-off list build or a scheduled data collection job.

| Use case | How the Likee Email Scraper helps |
|---|---|
| Emerging-market influencer marketing | Reach creators outside the saturated TikTok and Instagram pools |
| App install campaigns | Find regional creators for UA and referral partnerships |
| Music seeding | Contact discovery among lip-sync and dance creators for track promotion |
| Talent scouting | Surface short-video performers advertising a booking address |
| Regional brand campaigns | Build market-specific creator lists by country and language |
| Agency prospecting | Assemble a roster of unsigned creators to pitch representation |
| Market research | Collect structured data on how creators in a niche present themselves |
| CRM enrichment | Attach Likee handles and profile URLs to existing creator records |

***

### Why choose this Actor

**It is honest about its ceiling.** The yield limitation is stated at the top of this page, not buried. You know what you are buying before you run the Likee Email Scraper.

**It reaches an underserved pool.** Likee creators rarely appear in mainstream influencer databases, so the contacts you get are less likely to be over-emailed.

**It covers both Likee domains.** The Likee Email Scraper searches `likee.video` and `likee.com` together, which matters when every indexed page counts.

**It is built for volume without waste.** Global deduplication, a shared stop signal on `maxEmails` and streaming dataset writes mean the Likee Email Scraper collects what you asked for and then stops.

**It survives Google layout changes.** Structural parsing plus a whole-page fallback means a markup change degrades quality rather than breaking the run.

**One schema across 40+ platforms.** Learn the Likee Email Scraper once and every sibling Actor behaves identically — including the [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) for the same creators' larger accounts.

***

### Limitations

Read this before running the Likee Email Scraper. These are real constraints, not boilerplate.

- **Lower yield by design.** Likee indexes fewer public profile pages than the major video platforms, so the Likee Email Scraper returns less volume than a TikTok, YouTube or Instagram run. Plan around it.
- **Public index only.** Only creators whose email is visible in Google's index can be found. Anything shown only inside the Likee app is invisible to this Actor.
- **~300 results per query.** Google caps a single query at roughly 300 results, which is exactly why `expandQueries` exists — leave it on.
- **Truncated emails.** `possiblyTruncated: true` means Google's snippet ellipsis touched the address. Verify those rows before sending.
- **Handle availability.** `username` and `profileUrl` are only populated when Likee's handle appears in the result. Where Google shows only a display name, you still get `accountName` and `fullName` but an empty handle. This is a Google limitation, not a bug.
- **Proxy requirement.** The Actor requires the Apify **GOOGLE\_SERP** proxy and cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
- **No volume guarantee.** Results from the Likee Email Scraper vary with keywords, domains and location.

Use the output responsibly and in line with GDPR, CAN-SPAM and the local rules on unsolicited email in whichever market you are targeting.

***

### Related Actors

The Likee Email Scraper shares its crawler, parser and output schema with every Actor below. Swap the platform, keep the workflow.

| Actor | What it collects |
|---|---|
| [Likee Email and Phone Number Scraper](https://apify.com/leads-scraper/likee-email-and-phone-number-scraper) | Emails and phone numbers from Likee |
| [Likee Phone Number Scraper](https://apify.com/leads-scraper/likee-phone-number-scraper) | Public phone numbers from Likee |
| [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 |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [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 |
| [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: JSON input and dataset output

A realistic Likee Email Scraper input targeting dance and beauty creators in Indonesia:

```json
{
  "keywords": ["dance creator", "beauty influencer"],
  "location": "Indonesia",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 120,
  "countryCode": "ID",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business inquiries", "collab", "booking", "dm"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

And a single dataset item the Likee Email Scraper returns:

```json
{
  "network": "Likee",
  "keyword": "dance creator",
  "query": "site:likee.video dance creator \"@gmail.com\" \"Indonesia\" collab",
  "title": "ranidance_id - Likee",
  "accountName": "ranidance_id",
  "fullName": "Rani Putri",
  "username": "ranidance_id",
  "profileUrl": "https://likee.video/@ranidance_id",
  "url": "https://likee.video/@ranidance_id",
  "description": "Dance and lip sync creator, Jakarta. Collab & endorse: rani.putri.collab@gmail.com",
  "email": "rani.putri.collab@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T13:07:52Z"
}
```

***

### FAQ about the Likee Email Scraper

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

No. The Likee Email Scraper never logs in, never uses the Likee API and never opens likee.video. All data comes from publicly indexed Google search results.

#### Why does the Likee Email Scraper return fewer results than a TikTok run?

Because Likee indexes fewer public profile pages than the major video platforms. That is a property of the platform, not a setting you can tune around.

#### How is this different from a Likee API tool?

The Likee Email Scraper works entirely from search results, so it needs no API key, no token and no account permissions.

#### Where do the emails come from?

From the titles, snippets and site labels Google prints for `likee.video` and `likee.com` pages — typically bios and captions where creators publish a collab or booking address.

#### Can the Likee Email Scraper find private or in-app emails?

No. If an address is not in Google's public index, this likee email extractor cannot find it.

#### Why do some rows have an empty `username` and `profileUrl`?

Because Google showed only a display name for that result. You still get `accountName`, `fullName` and the email. It is a Google limitation, not a bug.

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

Google's snippet ellipsis touched the email, so it may be cut off. Verify those addresses before sending.

#### Do I need a proxy to run the Likee Email Scraper?

Yes. It requires the Apify **GOOGLE\_SERP** proxy and cannot run without Apify proxy credentials.

#### How many emails can I get on a free plan?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.

#### Should I leave `expandQueries` on?

Yes — more so here than anywhere else. Google caps one query at roughly 300 results, and expansion is how the Likee Email Scraper squeezes value out of a small indexed surface.

#### How do I improve yield on a likee influencer email search?

Run more keyword variants, add regional mailbox domains, raise `maxPagesPerQuery`, set a market-specific `countryCode`, and re-run on a schedule as more pages get indexed.

#### Can I schedule it?

Yes. Schedule the Likee Email Scraper on Apify and it appends new leads on each run. Run state is resumable and survives platform migrations.

#### Is the output ready for a CRM?

Yes. The Likee Email Scraper writes flat structured data with 14 fixed fields, exportable as JSON, CSV, Excel or XML.

#### Is this affiliated with Likee?

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

***

### Leave a review

If the Likee 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, a bug, or need a custom build of the Likee Email Scraper? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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": [
    "creator",
    "influencer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.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 Likee 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": [
        "creator",
        "influencer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.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/likee-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": [
        "creator",
        "influencer",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/likee-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": [
    "creator",
    "influencer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ]
}' |
apify call leads-scraper/likee-email-scraper --silent --output-dataset

```

## MCP server setup

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