# Walmart Email Scraper (`leads-scraper/walmart-email-scraper`) Actor

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

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

### Walmart Email Scraper - public seller and brand emails from Walmart Marketplace

The **Walmart Email Scraper** builds a deduplicated list of business contact emails from publicly indexed Walmart pages.
It is aimed at wholesale buyers, marketplace agencies, brand-protection teams and dropshippers who need to reach the operator behind a Walmart Marketplace storefront.
Feed it keywords, optional email domains and a location, and it returns a structured dataset ready for CSV, JSON or Excel export.

Walmart is one of the strongest performers in this Actor family.
Because Walmart exposes sellers and brands on clean path handles - `/seller/` and `/brand/` - the Walmart Email Scraper resolves account identity and a canonical `profileUrl` on the large majority of rows.
In a recent live test, every row returned came back with both an account label and a usable profile URL.

The Walmart Email Scraper does not log in, does not use Walmart's API and never opens walmart.com itself.
Every lead comes from Google's public index - titles, snippets and site labels - fetched through the Apify GOOGLE\_SERP proxy.
There is no browser, no JavaScript rendering, no authentication and no cookies.

#### What the Walmart Email Scraper does

The Walmart Email Scraper composes Google queries with the `site:` operator against walmart.com, then reads the result blocks it gets back.
A generated query looks something like `site:walmart.com marketplace seller wholesale "@gmail.com" "Texas"`.
Each block is parsed structurally, emails are pulled with a domain-filtered regex, and every unique address is pushed straight to the Apify dataset.

Walmart Marketplace has grown fast as a third-party channel, and many of its sellers are the same operators you would find on other marketplaces.
That makes the Walmart Email Scraper a practical supplier-sourcing and seller-outreach instrument rather than a generic email harvester.
It is search-driven contact discovery, scoped to one retailer's public footprint.

#### Why sourcing teams use a Walmart Email Scraper

Locating the company behind a Walmart Marketplace listing is normally manual: open the item, click through to the seller page, hunt for a contact line.
The Walmart Email Scraper compresses that into one run that sweeps hundreds of Google result pages concurrently and deduplicates as it goes.
The output is attributable - each row records the keyword and the exact query that produced it.

Emails published on Walmart seller and brand pages are almost always **business addresses**: customer-service inboxes, wholesale desks, trade-enquiry aliases.
That is what makes them appropriate for B2B outreach, and it is also why the responsible-use section below matters.
The Walmart Email Scraper touches no private account data, no order data and nothing behind a login.

### Key features of the Walmart Email Scraper

| Feature | What it means in practice |
|---|---|
| Google-index sourcing | Reads publicly indexed Walmart results through the Apify GOOGLE\_SERP proxy - no login, no cookies, no browser |
| Strong handle resolution | Walmart's `/seller/` and `/brand/` paths mean `username` and `profileUrl` are filled on most rows |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per query modifier; base queries run first |
| Domain filtering | Only emails on the domains listed in `customDomains` are kept |
| Global deduplication | Each address is emitted once per run, across every query and every page |
| Obfuscation handling | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` never matches inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same result block |
| Async concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Retries and block detection | Up to 3 attempts per page with exponential backoff, a fresh proxy session per request, and CAPTCHA / "unusual traffic" / consent pages detected and retried rather than counted as empty |
| Blocked-query requeue | Blocked or failed queries are re-queued once at the end of the run |
| Resumable state | Key-value-store progress keyed by a hash of the input, with throttled saves plus saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Layout fallback | A whole-page fallback parser means a Google markup change degrades to "emails without account details", not "no emails" |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

### How the Walmart Email Scraper works

1. It reads your input - keywords, location, email domains and limits.
2. It builds Google queries with the `site:` operator against walmart.com.
3. It fetches result pages asynchronously through the Apify GOOGLE\_SERP proxy using `aiohttp`.
4. It finds each result's `<h3>` title and the smallest surrounding block, so it never relies on Google's CSS class names.
5. It extracts emails from that block text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead to the dataset immediately.

That immediate push is deliberate: leads appear while the Walmart Email Scraper is still working, so you can abort early and keep everything collected so far.
State is resumable and keyed by a hash of your input, so a migrated or restarted run picks up where it left off.
Nothing is buffered to the end of the run.

### Walmart Email Scraper input reference

Field names, types and defaults below are exactly what the Actor accepts.

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["seller", "marketplace"]` | Search terms describing the Walmart 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","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 |

#### Tuning the Walmart Email Scraper

This config targets a single domain, walmart.com, so `countryCode` is a lighter lever here than on the multi-domain marketplaces.
It still shifts which regional results the search proxy favours, which is worth testing if you are targeting sellers in one state or trading region - but the bigger wins come from `keywords` and `customDomains`.
On the multi-domain siblings such as the [Amazon Email Scraper](https://apify.com/leads-scraper/amazon-email-scraper) and the [eBay Email Scraper](https://apify.com/leads-scraper/ebay-email-scraper), `countryCode` does much heavier lifting.

The default `queryModifiers` - `email`, `contact`, `wholesale`, `customer service`, `inquiries` - are tuned for marketplace trade language.
Swap in `distributor`, `bulk pricing` or `reseller program` when your goal is sourcing rather than brand outreach.
Keep `expandQueries` on: Google caps a single query at roughly 300 results, and expansion is how the Walmart Email Scraper gets past that ceiling.

#### Example input for the Walmart Email Scraper

```json
{
  "keywords": ["home decor brand", "outdoor furniture seller"],
  "location": "United States",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "wholesale", "customer service", "inquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

### Walmart Email Scraper output fields

Every dataset item carries all fourteen fields below - no more, no fewer.

| 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 listing captions |
| `username` | URL-safe handle when Walmart exposes one; otherwise `null` |
| `profileUrl` | Canonical seller URL when a handle is known; otherwise empty |
| `url` | Direct Walmart link when exposed, else the profile URL |
| `description` | Bio or listing 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 |

#### Example output from the Walmart Email Scraper

Walmart's path handles resolve cleanly, so rows from the Walmart Email Scraper usually look like this - identity and profile URL both present.

```json
[
  {
    "network": "Walmart",
    "keyword": "home decor brand",
    "query": "site:walmart.com home decor brand wholesale \"@gmail.com\" \"United States\"",
    "title": "Havenmoor Home - Seller Profile - Walmart.com",
    "accountName": "havenmoor-home",
    "fullName": "Havenmoor Home",
    "username": "havenmoor-home",
    "profileUrl": "https://www.walmart.com/seller/havenmoor-home",
    "url": "https://www.walmart.com/seller/havenmoor-home",
    "description": "Wholesale and trade enquiries: havenmoor.trade@gmail.com. Rugs, wall art and seasonal decor.",
    "email": "havenmoor.trade@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:04:18Z"
  },
  {
    "network": "Walmart",
    "keyword": "outdoor furniture seller",
    "query": "site:walmart.com outdoor furniture seller customer service \"@outlook.com\"",
    "title": "Redpine Outdoor - Walmart Marketplace",
    "accountName": "redpine-outdoor",
    "fullName": "Redpine Outdoor",
    "username": "redpine-outdoor",
    "profileUrl": "https://www.walmart.com/seller/redpine-outdoor",
    "url": "https://www.walmart.com/seller/redpine-outdoor",
    "description": "Customer service: care@redpineoutdoor.outlook.com. Patio sets, gazebos and outdoor storage.",
    "email": "care@redpineoutdoor.outlook.com",
    "emailDomain": "@outlook.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T10:05:47Z"
  }
]
```

### Use cases for the Walmart Email Scraper

| Who | How they use the Walmart Email Scraper |
|---|---|
| Wholesale buyers | Shortlist Walmart Marketplace sellers in a category and send trade-account enquiries |
| Private-label brands | Find established sellers and manufacturers in an adjacent niche |
| Marketplace agencies | Prospect for listing-optimisation, advertising and account-management clients |
| Brand-protection teams | Collect published contact points for sellers listing against a protected brand |
| Dropshippers | Identify suppliers advertising a wholesale or inquiries inbox |
| B2B sales teams | Reach Walmart sellers with logistics, packaging, insurance or software offers |
| Market researchers | Map which Walmart categories publish trade contacts and which stay silent |
| Recruiters | Find marketplace operators and brand managers who are hiring |

A productive pattern is to run the Walmart Email Scraper narrowly, one category at a time, then merge datasets.
Narrow runs keep keyword attribution clean, because `keyword` and `query` tell you which phrasing produced each lead.
That turns your search language into something you can A/B test rather than guess at.

If Walmart is only one channel in your sourcing plan, the same engine covers the rest - the [eBay Email Scraper](https://apify.com/leads-scraper/ebay-email-scraper) is the other top performer in this family.
For handmade and craft suppliers, use the [Etsy Email Scraper](https://apify.com/leads-scraper/etsy-email-scraper); for overseas manufacturing, the [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper).
Independent storefronts are covered by the [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper).

### Walmart Email Scraper limitations - stated honestly

- **Publicly indexed emails only.** If an address is not visible in Google's index, the Walmart Email Scraper cannot find it. It does not crawl walmart.com.
- **Google's result ceiling.** A single query returns roughly 300 results at most, which is exactly why `expandQueries` and `queryModifiers` exist.
- **`possiblyTruncated`.** Rows where Google's snippet ellipsis touched the address are flagged `true`. Verify those before sending.
- **Apify GOOGLE\_SERP proxy required.** The Walmart Email Scraper cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
- **`username` and `profileUrl` are conditional.** They are filled only when Google's result exposes a handle. Walmart resolves well, but a row without one still carries `accountName` and `fullName`. This is a Google indexing limitation, not a bug.
- **No volume guarantee.** Results vary with keywords, domains, country and location. No count is promised.

### Responsible use

Emails published on Walmart Marketplace listings and seller pages are usually business or customer-service addresses posted for trade enquiries.
Treat them as B2B contact points, keep outreach relevant, honour opt-outs, and record a lawful basis if you operate under GDPR, PECR or similar rules.
Review Walmart's terms and your local marketing law before you send - the Walmart Email Scraper collects public data, but what you do with it is your responsibility.

This Actor is not affiliated with, endorsed by or officially supported by Walmart.

### FAQ about the Walmart Email Scraper

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

No. It never logs in, never uses Walmart's API and never opens walmart.com. Everything comes from publicly indexed Google search results.

#### How reliable is `profileUrl` on Walmart?

Very - Walmart exposes sellers and brands on `/seller/` and `/brand/` path handles, so most rows resolve to a canonical URL. In a recent live test all returned rows carried both identity and a profile URL.

#### Which domain does it search?

walmart.com. This platform config targets that single domain.

#### Is `countryCode` useful here?

It shifts which regional results the search proxy favours, but with one domain in scope it is a lighter lever than on the multi-domain marketplaces. Keywords and domains move the needle more.

#### Can the Walmart Email Scraper find emails on any domain?

Only the domains in `customDomains`. The default is `@gmail.com` and `@yahoo.com`; add corporate domains to widen the net.

#### How many emails can one run return?

Up to `maxEmails`, which accepts 1 to 10000. Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

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

Google's snippet ellipsis touched that address, so it may be cut off. Verify before adding it to a send list.

#### Does it need proxies?

Yes - the Apify GOOGLE\_SERP proxy. The Walmart Email Scraper cannot run without Apify proxy credentials.

#### Can I resume an interrupted run?

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

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

Parsing is structural - the `<h3>` title plus its smallest surrounding block - with a whole-page fallback parser behind it. A layout change degrades to "emails without account details", not "no emails".

#### How do I get more leads?

Use specific category keywords, keep `expandQueries` on, widen `customDomains`, raise `maxPagesPerQuery` and increase `maxConcurrency` within the 1-20 range.

#### Are the emails verified?

No. The Walmart Email Scraper extracts what is published in the index. Run your own verification before a campaign.

### Getting started with the Walmart Email Scraper

1. Open the Walmart Email Scraper on Apify and press **Try for free**.
2. Replace the default `keywords` (`seller`, `marketplace`) with your own category terms.
3. Add the email domains you care about to `customDomains`.
4. Raise `maxEmails`, optionally set a `location` phrase, and run it.
5. Export the dataset from the **Storage** tab when the Walmart Email Scraper finishes.

Start small - a `maxEmails` of 20 to 50 - to confirm your keywords and domains are pulling the right kind of seller.
Once a keyword set is producing useful rows, re-run the Walmart Email Scraper with a higher cap and more pages per query.

#### Exporting Walmart Email Scraper results

Every Walmart Email Scraper run writes to a standard Apify dataset, so you can download CSV, JSON, XML or Excel, or pull the rows through the Apify API and the JavaScript or Python clients.
The default dataset view surfaces the fields most people need first: email, account, name, username, profile, keyword, bio snippet and the truncation flag.
Deduplication is per run, so keep your own master list when you merge several Walmart Email Scraper datasets together.

### Related Actors

The Walmart Email Scraper belongs to a 41-Actor E-commerce & Marketplaces family sharing this engine.

| Actor | What it collects |
|---|---|
| [Walmart Email and Phone Number Scraper](https://apify.com/neuro-scraper/walmart-email-and-phone-number-scraper) | Emails and phone numbers from Walmart |
| [Walmart Phone Number Scraper](https://apify.com/neuro-scraper/walmart-phone-number-scraper) | Public phone numbers from Walmart |
| [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 |
| [Flipkart Email Scraper](https://apify.com/leads-scraper/flipkart-email-scraper) | Public contact emails from Flipkart |
| [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 |
| [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 Walmart 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? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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",
    "marketplace"
  ],
  "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 Walmart 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",
        "marketplace"
    ],
    "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/walmart-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",
        "marketplace",
    ],
    "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/walmart-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",
    "marketplace"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ]
}' |
apify call leads-scraper/walmart-email-scraper --silent --output-dataset

```

## MCP server setup

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