# Flipkart Email Scraper (`leads-scraper/flipkart-email-scraper`) Actor

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

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

### Flipkart Email Scraper - public seller and supplier emails from India's biggest marketplace

The Flipkart Email Scraper collects publicly indexed contact emails from Flipkart pages using Google search,
filtered by keyword, location and email domain.
It is built for wholesale sourcing and marketplace-seller outreach in India.

One thing to understand before your first run: Flipkart indexes product pages rather than seller profiles, so
most rows carry an email without a seller handle.

That is a property of Flipkart's own indexing, not a defect in the Flipkart Email Scraper, and it shapes what
the output looks like.

In practice you get a strong email column and a weaker identity column.
If your workflow needs a storefront URL for every lead, plan to enrich afterwards or use a sibling Actor that
indexes profiles more generously.

#### What the Flipkart Email Scraper actually does

The Flipkart Email Scraper never logs into Flipkart, never uses a Flipkart API and never opens the Flipkart
website.
It builds Google queries with the `site:flipkart.com` operator and reads publicly indexed search results.

There is no browser, no JavaScript rendering, no authentication and no cookies.
Every address the Flipkart Email Scraper returns was already visible in Google's public index.

### Why use the Flipkart Email Scraper for India-focused prospecting

Flipkart is the anchor marketplace for Indian e-commerce, which makes a Flipkart seller email list valuable to
anyone selling into that market.
Logistics providers, payment processors, cataloguing agencies and packaging suppliers all prospect here.

Because the platform is India-focused, two input fields do real work.
Set `countryCode` to `IN` to point the search proxy at the Indian index, and add Hindi or Hinglish keywords
alongside the English defaults.

Terms such as `vikreta`, `thok vikreta`, `distributor` or `manufacturer` reach listing text that plain
`seller` never matches.

Running the Flipkart Email Scraper several times with different keyword sets is far more productive than one
large run.

### Features of the Flipkart Email Scraper

| Feature | What it means in practice |
|---|---|
| Google `site:` targeting | All queries are scoped to `flipkart.com` |
| Query expansion | Base, quoted and `intitle:` variants, plus one query per modifier |
| Country targeting | `countryCode` points the search proxy at a specific market such as `IN` |
| Domain filtering | Only emails on the domains you list are kept |
| Global deduplication | Each email address appears once across every query and page |
| Obfuscated email recovery | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com` and the full-width `＠` |
| Junk filtering | 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 email in the same block |
| Async concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries with backoff | Up to three attempts per page, each with a fresh proxy session |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are retried rather than counted as empty |
| Failed-query requeue | Blocked or failed queries are retried once at the end of the run |
| Resumable state | Progress is kept in the key-value store and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Structural parsing | Result blocks are found via `<h3>` and the smallest surrounding block, not Google CSS class names |
| Whole-page fallback | A Google layout change degrades to emails without account details rather than to zero results |
| Truncation flag | `possiblyTruncated` marks emails the snippet ellipsis may have clipped |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

Everything above is on by default, so the Flipkart Email Scraper produces usable output without configuration.

### How the Flipkart Email Scraper works

First it reads your keywords, location, email domains and limits.
Then it builds Google queries such as `site:flipkart.com supplier "@gmail.com" "Mumbai"`.

Next it fetches result pages through the Apify GOOGLE\_SERP proxy using `aiohttp`.
It parses each result block structurally, locating the `<h3>` title and then the smallest surrounding block.

A domain-filtered regex extracts emails from the block text.
The Flipkart Email Scraper then deduplicates globally and pushes each lead straight to the dataset, so you can
work the list while the run continues.

Base queries run before expanded ones.
That ordering means the highest-signal Flipkart supplier contacts arrive early even if you set a small
`maxEmails`.

### Flipkart Email Scraper input fields

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["seller", "supplier"]` | Search terms describing the Flipkart accounts you want |
| `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, e.g. `IN` |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email","contact","wholesale","customer service","inquiries"]` | 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 Flipkart Email Scraper input

```json
{
  "keywords": ["seller", "supplier", "distributor", "manufacturer"],
  "location": "Delhi",
  "customDomains": ["@gmail.com", "@yahoo.com", "@rediffmail.com"],
  "maxEmails": 250,
  "countryCode": "IN",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "wholesale", "customer service", "inquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Adding `@rediffmail.com` matters in India, where that domain is still common among small traders.
Run the Flipkart Email Scraper with the defaults alone and you will leave Flipkart supplier contacts on the table.

### Flipkart Email Scraper output fields

Every dataset item the Flipkart Email Scraper writes 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 |
| `fullName` | Display name parsed from a profile-style title; empty for product-page titles |
| `username` | URL-safe handle when Flipkart exposes one; otherwise `null` |
| `profileUrl` | Canonical seller URL when a handle is known; otherwise empty |
| `url` | Direct Flipkart link when exposed, else the profile URL |
| `description` | Snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example Flipkart Email Scraper output

The second row below is the common shape for this platform, because Flipkart indexes product pages rather than
seller profiles.

```json
[
  {
    "network": "Flipkart",
    "keyword": "supplier",
    "query": "site:flipkart.com supplier \"@gmail.com\" \"Delhi\"",
    "title": "ShreeTradersIndia - Flipkart",
    "accountName": "ShreeTradersIndia",
    "fullName": "Shree Traders India",
    "username": "shreetradersindia",
    "profileUrl": "https://www.flipkart.com/shreetradersindia",
    "url": "https://www.flipkart.com/shreetradersindia",
    "description": "Bulk supplier of kitchenware and home essentials. Wholesale: shreetraders.blk@gmail.com",
    "email": "shreetraders.blk@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:02:41.902Z"
  },
  {
    "network": "Flipkart",
    "keyword": "seller",
    "query": "site:flipkart.com seller contact \"@gmail.com\"",
    "title": "Stainless Steel Water Bottle 1L - Buy Online at Best Price | Flipkart",
    "accountName": "Flipkart",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.flipkart.com/stainless-steel-water-bottle-1l/p/itm9f2c1a",
    "description": "Seller queries and bulk orders: metroware.sales@yahoo.com",
    "email": "metroware.sales@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T10:03:12.554Z"
  }
]
```

### Use cases for the Flipkart Email Scraper

| Use case | How the Flipkart Email Scraper helps |
|---|---|
| Wholesale sourcing in India | Find Flipkart supplier contacts by product category |
| Marketplace-seller outreach | Build a Flipkart seller contact list for a SaaS or logistics offer |
| Distributor recruitment | Spot traders already active in your category |
| Cataloguing and photography services | Reach sellers whose listings need better assets |
| Packaging and 3PL sales | Contact merchants shipping physical goods at volume |
| Payments and lending | Reach small merchants who publish business contact details |
| Market research | Understand how Indian sellers present themselves and where they publish contacts |
| CRM enrichment | Export Flipkart seller leads to CSV, JSON or Excel and import them into your pipeline |

Note that some of these workflows need a seller identity, and the Flipkart Email Scraper often cannot supply one.
Plan for that rather than being surprised by it, and lean on the `description` and `url` fields for context.

### Tips to get more from the Flipkart Email Scraper

Set `countryCode` to `IN`.
It is a genuine lever on this platform, because Flipkart's audience and index are concentrated in one country.

Mix languages in `keywords`.
Hindi and Hinglish trade vocabulary reaches listing text that English business terms never touch, and this is
the single cheapest way to widen a Flipkart Email Scraper run.

Widen `customDomains`.
Beyond the defaults, `@rediffmail.com`, `@hotmail.com` and `@outlook.com` are all worth adding for Indian
merchants.

Keep `expandQueries` on.
Google caps a single query at roughly 300 results, and expansion is what gets the Flipkart Email Scraper past
that ceiling.

Use `location` for city-level targeting.
Adding `Mumbai`, `Surat`, `Jaipur` or `Ludhiana` produces tighter, more actionable India marketplace leads.

### Limitations of the Flipkart Email Scraper

Flipkart indexes product pages rather than seller profiles, so most rows carry an email without a seller handle.
This is the defining limitation of the Flipkart Email Scraper, and it means `username` is frequently `null`
and `profileUrl` frequently empty.

The Flipkart Email Scraper only finds accounts whose email is publicly visible in Google's index.
Contact details kept inside Flipkart's internal messaging will never appear.

Google caps a single query at roughly 300 results, which is exactly why query expansion exists.
No run is exhaustive and no volume is guaranteed.

`username` and `profileUrl` are only populated when Google's result exposes a handle.
On Flipkart that happens on a minority of rows, and it is a Google indexing limitation rather than a bug.

`possiblyTruncated: true` means Google's snippet ellipsis touched the email, so verify before sending.
Treat those rows as candidates.

The Flipkart Email Scraper requires the Apify GOOGLE\_SERP proxy and 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.
Two runs on different days can legitimately return different Flipkart seller contacts.

### Responsible use, GDPR and marketplace terms for the Flipkart Email Scraper

Published business addresses are not the same thing as consent to be marketed to.
Under GDPR, India's data protection rules and similar regimes you need a lawful basis, honest identification
and a working opt-out in every message.

Marketplace terms of service also restrict unsolicited commercial contact.
Respect Flipkart's rules, keep suppression lists and do not resell scraped personal data.

The Flipkart Email Scraper is not affiliated with, endorsed by or officially supported by Flipkart.
It reads public Google results and nothing else.

### Flipkart Email Scraper FAQ

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

No. It never logs in, never uses a Flipkart API and never opens the Flipkart website. All data comes from
publicly indexed Google search results.

#### Why do so many rows have no seller name or profile URL?

Because Flipkart indexes product pages rather than seller profiles, so most rows carry an email without a
seller handle. The email, snippet and direct link are still there.

#### How many emails should I expect from the Flipkart Email Scraper?

It varies with keywords, domains and country. Flipkart yields fewer complete seller identities than
profile-heavy platforms, so judge a run by usable emails rather than by filled `username` fields.

#### Is the Flipkart Email Scraper affiliated with Flipkart?

No. It is an independent Actor reading public Google results, and it is not endorsed or officially supported
by Flipkart.

#### Can I schedule the Flipkart Email Scraper?

Yes. Apify schedules, webhooks and the API all work normally, so you can refresh a Flipkart seller email list
on a recurring basis.

#### Does `countryCode` matter here?

Yes. Setting it to `IN` is a real lever, and pairing it with Hindi or Hinglish keywords is the most effective
way to expand a Flipkart Email Scraper run.

#### Which email domains should I use?

Start with the defaults, then add `@rediffmail.com`, `@hotmail.com` and `@outlook.com`, which are common
among Indian traders.

#### What does `possiblyTruncated` mean?

Google's snippet ellipsis may have clipped the address, so verify those emails before you send anything.

#### Do I need a proxy?

Yes. The Flipkart Email Scraper requires the Apify GOOGLE\_SERP proxy and will not run without Apify proxy
credentials.

#### Is there a free-plan cap?

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

#### Can I resume an interrupted run?

Yes. State lives in the key-value store keyed by a hash of your input and is saved on `PERSIST_STATE`,
`MIGRATING` and `ABORTING`.

#### How do I export the results?

The Apify dataset exports to CSV, JSON, Excel and more, and it is reachable over the API for direct CRM import.

#### Which sibling Actors should I run alongside the Flipkart Email Scraper?

[Amazon Email Scraper](https://apify.com/leads-scraper/amazon-email-scraper) covers the other half of Indian
marketplace retail, while [Lazada Email Scraper](https://apify.com/neuro-scraper/lazada-email-scraper) and
[Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) extend the workflow into SEA.

For upstream suppliers, try [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) or
[AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper).

### Related Actors

Forty sibling Actors cover the rest of the E-commerce & Marketplaces category.
They run the same engine as the Flipkart Email Scraper with a platform-specific configuration.

| Actor | What it collects |
|---|---|
| [Flipkart Email and Phone Number Scraper](https://apify.com/leads-scraper/flipkart-email-and-phone-number-scraper) | Emails and phone numbers from Flipkart |
| [Flipkart Phone Number Scraper](https://apify.com/leads-scraper/flipkart-phone-number-scraper) | Public phone numbers from Flipkart |
| [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper) | Public contact emails from AliExpress |
| [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) | Public contact emails from Allegro |
| [Amazon Email Scraper](https://apify.com/leads-scraper/amazon-email-scraper) | Public contact emails from Amazon |
| [Best Buy Seller Email Scraper](https://apify.com/leads-scraper/best-buy-seller-email-scraper) | Public contact emails from Best Buy |
| [BigCommerce Store Email Scraper](https://apify.com/neuro-scraper/bigcommerce-store-email-scraper) | Public contact emails from BigCommerce Store |
| [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) | Public contact emails from Cdiscount |
| [Coupang Email Scraper](https://apify.com/neuro-scraper/coupang-email-scraper) | Public contact emails from Coupang |
| [Depop Email Scraper](https://apify.com/leads-scraper/depop-email-scraper) | Public contact emails from Depop |
| [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) | Public contact emails from DHgate |
| [eBay Email Scraper](https://apify.com/leads-scraper/ebay-email-scraper) | Public contact emails from eBay |
| [Ecwid Store Email Scraper](https://apify.com/neuro-scraper/ecwid-store-email-scraper) | Public contact emails from Ecwid Store |
| [Etsy Email Scraper](https://apify.com/leads-scraper/etsy-email-scraper) | Public contact emails from Etsy |
| [Faire Email Scraper](https://apify.com/leads-scraper/faire-email-scraper) | Public contact emails from Faire |
| [Home Depot Seller Email Scraper](https://apify.com/leads-scraper/home-depot-seller-email-scraper) | Public contact emails from Home Depot |
| [JD.com Email Scraper](https://apify.com/leads-scraper/jd-com-email-scraper) | Public contact emails from JD.com |
| [Lazada Email Scraper](https://apify.com/neuro-scraper/lazada-email-scraper) | Public contact emails from Lazada |
| [Lowe's Seller Email Scraper](https://apify.com/leads-scraper/lowes-seller-email-scraper) | Public contact emails from Lowe's |
| [MercadoLibre Email Scraper](https://apify.com/neuro-scraper/mercadolibre-email-scraper) | Public contact emails from MercadoLibre |
| [Mercari Email Scraper](https://apify.com/neuro-scraper/mercari-email-scraper) | Public contact emails from Mercari |
| [Newegg Email Scraper](https://apify.com/leads-scraper/newegg-email-scraper) | Public contact emails from Newegg |
| [Otto Email Scraper](https://apify.com/leads-scraper/otto-email-scraper) | Public contact emails from Otto |
| [Overstock Email Scraper](https://apify.com/leads-scraper/overstock-email-scraper) | Public contact emails from Overstock |
| [Poshmark Email Scraper](https://apify.com/leads-scraper/poshmark-email-scraper) | Public contact emails from Poshmark |
| [Rakuten Email Scraper](https://apify.com/neuro-scraper/rakuten-email-scraper) | Public contact emails from Rakuten |
| [Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) | Public contact emails from Shopee |
| [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper) | Public contact emails from Shopify Store |
| [Taobao Email Scraper](https://apify.com/leads-scraper/taobao-email-scraper) | Public contact emails from Taobao |
| [Target Seller Email Scraper](https://apify.com/neuro-scraper/target-seller-email-scraper) | Public contact emails from Target |
| [Temu Email Scraper](https://apify.com/leads-scraper/temu-email-scraper) | Public contact emails from Temu |
| [Tmall Email Scraper](https://apify.com/leads-scraper/tmall-email-scraper) | Public contact emails from Tmall |
| [Vinted Email Scraper](https://apify.com/leads-scraper/vinted-email-scraper) | Public contact emails from Vinted |
| [Walmart Email Scraper](https://apify.com/leads-scraper/walmart-email-scraper) | Public contact emails from Walmart |
| [Wayfair Email Scraper](https://apify.com/neuro-scraper/wayfair-email-scraper) | Public contact emails from Wayfair |
| [Wish Email Scraper](https://apify.com/leads-scraper/wish-email-scraper) | Public contact emails from Wish |
| [Wix Stores Email Scraper](https://apify.com/leads-scraper/wix-stores-email-scraper) | Public contact emails from Wix Stores |
| [WooCommerce Email Scraper](https://apify.com/neuro-scraper/woocommerce-email-scraper) | Public contact emails from WooCommerce |
| [Zalando Email Scraper](https://apify.com/leads-scraper/zalando-email-scraper) | Public contact emails from Zalando |
| [AliExpress Email and Phone Number Scraper](https://apify.com/neuro-scraper/aliexpress-email-and-phone-number-scraper) | Emails and phone numbers from AliExpress |
| [Allegro Email and Phone Number Scraper](https://apify.com/neuro-scraper/allegro-email-and-phone-number-scraper) | Emails and phone numbers from Allegro |
| [Amazon Email and Phone Number Scraper](https://apify.com/leads-scraper/amazon-email-and-phone-number-scraper) | Emails and phone numbers from Amazon |

### Leave a review

If the Flipkart 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 of the Flipkart Email Scraper: **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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": [
    "seller",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Flipkart 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": [
        "seller",
        "supplier"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "wholesale",
        "customer service",
        "inquiries"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/flipkart-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": [
        "seller",
        "supplier",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "wholesale",
        "customer service",
        "inquiries",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/flipkart-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": [
    "seller",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ]
}' |
apify call leads-scraper/flipkart-email-scraper --silent --output-dataset

```

## MCP server setup

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