# Behance Email Scraper (`leads-scraper/behance-email-scraper`) Actor

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

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

### Behance Email Scraper

### Behance Email Scraper — extract public designer contact emails from Behance

The **Behance Email Scraper** finds publicly indexed contact emails belonging to Behance designers, illustrators, art directors and studios, and turns them into a clean, structured dataset.

You give it keywords, an optional location and a list of email domains. The Behance Email Scraper builds targeted Google queries against `behance.net`, parses the search results and extracts every matching email it finds.

There is no login, no Behance API, no browser and no cookies. This Behance email extractor reads only what Google has already published in its public index.

Creative recruiters, design agencies, product studios and freelance marketplaces use the Behance Email Scraper for contact discovery — building designer email lists without opening hundreds of portfolio pages by hand.

***

### Features of the Behance Email Scraper

Everything listed here is implemented in the Behance Email Scraper today, with no roadmap items and no aspirational claims.

| Feature | What it means in practice |
|---|---|
| Google `site:` search automation | Every query is scoped to `behance.net`, so results stay on-platform |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per query modifier |
| Domain-filtered extraction | Only emails on your `customDomains` list are kept |
| Global deduplication | Each unique email is pushed to the dataset once, across all queries and pages |
| Obfuscation-aware parser | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com` |
| Unicode normalisation | Handles zero-width characters and the full-width `＠` sign |
| Junk filter | 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 result block |
| Concurrency control | An `asyncio` worker pool runs several queries in parallel with a shared stop signal |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, never counted as empty |
| Resumable state | Progress is saved to the key-value store, keyed by a hash of your input |
| Structural parsing | Result blocks are located via the `<h3>` title, not by fragile CSS class names |
| Fallback parser | If Google's markup changes, the run degrades to "emails without account details", not "no emails" |
| Streaming dataset writes | Leads land in the dataset immediately, so you can export mid-run |

***

### How the Behance Email Scraper works

The Behance Email Scraper is a search-results crawler, not a portfolio crawler. It never touches behance.net itself.

**1. Read input.** Keywords, location, email domains, limits and concurrency settings are validated.

**2. Build queries.** The scraper composes Google queries with the `site:` operator, for example:
`site:behance.net illustrator "@gmail.com" "Berlin"`.

**3. Expand queries.** With `expandQueries` on, each keyword × domain pair is issued in several phrasings: the base query, a quoted variant, an `intitle:` variant, and one variant per entry in `queryModifiers`. Base queries always run first.

**4. Fetch pages.** The Behance Email Scraper fetches result pages asynchronously with `aiohttp` through the Apify GOOGLE\_SERP proxy, using proxy rotation and pagination up to `maxPagesPerQuery`.

**5. Parse blocks.** For each result, the parser locates the `<h3>` title and then the smallest surrounding block, so titles, snippets and site labels stay attached to the right record.

**6. Extract and filter emails.** A domain-filtered regex pulls candidate addresses out of the block text, normalises them, and drops junk and boundary mismatches.

**7. Deduplicate and store.** The Behance Email Scraper deduplicates every new email globally and pushes it straight into the Apify dataset as structured data.

The Behance Email Scraper re-queues blocked or failed queries once at the end of the run, and the run summary logs pages fetched, blocked pages, retries and emails per page.

***

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

Every row the Behance Email Scraper writes is a single email paired with the account metadata Google exposed alongside it.

You get the email itself, the matched domain, the account label, a parsed display name, a handle and profile URL where Behance exposes one, a cleaned bio snippet, and full provenance — the keyword and the exact query that produced the lead.

The provenance fields matter for lead generation: they tell you which niche and phrasing actually produce designers worth contacting, so you can refine the next run.

***

### Input schema

Every Behance Email Scraper input field is listed below with the exact name, type and default taken from the Actor input schema.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["designer", "illustrator"]` | Search terms describing the Behance accounts you want (niche, job title, industry) |
| `location` | string | `""` | Optional location phrase added to every query, e.g. `"New York"` |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails ending with one of these domains are collected; the leading `@` is optional |
| `maxEmails` | integer 1–10000 | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (US, GB, DE…). Empty for any |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair with several phrasings |
| `queryModifiers` | array | `["email", "contact", "inquiries", "hire", "work with me"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1–50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1–20 | `5` | How many queries run in parallel |

#### Input example for the Behance Email Scraper

```json
{
  "keywords": ["ui ux designer", "motion designer", "brand identity designer"],
  "location": "Berlin",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 250,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "inquiries", "hire", "work with me"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output schema

Every dataset item produced by the Behance Email Scraper has all fourteen fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints (handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for project captions |
| `username` | URL-safe handle when Behance exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct Behance link when exposed, else the profile URL |
| `description` | Bio or project 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 |

#### Output example

```json
{
  "network": "Behance",
  "keyword": "ui ux designer",
  "query": "site:behance.net ui ux designer \"@gmail.com\" \"Berlin\"",
  "title": "Lena Hoffmann on Behance",
  "accountName": "lenahoffmann",
  "fullName": "Lena Hoffmann",
  "username": "lenahoffmann",
  "profileUrl": "https://www.behance.net/lenahoffmann",
  "url": "https://www.behance.net/lenahoffmann",
  "description": "Product & UI designer in Berlin. Available for freelance work. Contact: lena.hoffmann.design@gmail.com",
  "email": "lena.hoffmann.design@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:14:22.117Z"
}
```

The Behance Email Scraper dataset exports as JSON, CSV, Excel or XML from the Apify console, or streams through the Apify API into your CRM, ATS or outreach tool.

***

### How to use the Behance Email Scraper

**Step 1 — pick narrow keywords.** `packaging designer` beats `designer`. Niche terms match the language designers actually write in their Behance bios.

**Step 2 — choose realistic email domains.** Freelance designers overwhelmingly publish `@gmail.com` addresses. Add studio-style domains only if you are targeting agencies.

**Step 3 — set `maxEmails` deliberately.** Start at 20–50 to sanity-check relevance, then raise it once the keyword set is proven.

**Step 4 — use `location` and `countryCode` together.** A location phrase narrows the snippet text; the country code steers the search proxy.

**Step 5 — leave `expandQueries` on.** It is the main defence against Google's per-query result ceiling.

**Step 6 - clean before you send.** Filter out rows where `possiblyTruncated` is `true`, then put the remaining Behance Email Scraper results through your normal email-verification step before any outreach.

***

### Use cases for the Behance Email Scraper

| Use case | Who runs it | Typical keywords |
|---|---|---|
| Creative recruiting pipelines | Design recruiters, talent partners | `product designer`, `motion designer`, `art director` |
| Freelance subcontracting bench | Agencies needing overflow capacity | `freelance illustrator`, `3d artist`, `packaging designer` |
| Marketplace and platform seeding | Design marketplaces, portfolio tools | `ui designer`, `webflow designer`, `brand designer` |
| Design tool go-to-market | SaaS founders selling to creatives | `figma designer`, `motion graphics`, `ux researcher` |
| Studio partnership outreach | Studio principals, BD leads | `design studio`, `branding agency`, `art direction` |
| Print and licensing acquisition | Publishers, licensing houses | `illustrator`, `pattern designer`, `editorial illustration` |
| Localised talent sourcing | Regional agencies and in-house teams | any keyword + `location` |
| Market and competitor research | Analysts studying creative talent supply | `ui ux designer` per city or country |

Because Behance skews toward polished portfolio work, the Behance Email Scraper is strongest for **sourcing senior and mid-level creative talent** — exactly the cohort that publishes a working-inquiry email in the bio.

If your outreach also needs interaction-design shots and micro-portfolios, pair this Actor with the [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper). For illustration and fan-art communities, the [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) covers a very different creative population.

Designers who monetise directly through memberships are easier to reach with the [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper), while in-house design leadership and agency decision-makers sit better in the [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper).

***

### Why use this Behance Email Scraper

Manual contact discovery on Behance is slow: search, open a profile, read the bio, copy the address, repeat. The Behance Email Scraper automates that loop and returns a deduplicated dataset instead of a browser-tab graveyard.

It is also honest about provenance. Every row carries the `query` and `keyword` that produced it, so a lead is auditable rather than anonymous.

The parser is built to survive layout churn. Because block detection is structural rather than class-name based, a Google redesign degrades results gracefully instead of breaking the crawler outright.

Long Behance Email Scraper runs also survive interruption: state persists in the key-value store, and saves fire on Apify PERSIST\_STATE, MIGRATING and ABORTING events.

***

### Limitations you should know before running

The Behance Email Scraper is deliberately transparent about its boundaries. Read these before planning a large data collection run.

**Only publicly indexed emails.** The Behance Email Scraper finds addresses that already appear in Google's index. A designer who keeps their email behind Behance's message form will not appear.

**Google's per-query ceiling.** A single query returns roughly 300 results at most. Query expansion exists precisely to work around this, which is why it is on by default.

**`possiblyTruncated`.** When Google's snippet ellipsis touches an email, the field is set to `true` and the address may be cut off. Verify those rows before sending anything.

**Apify GOOGLE\_SERP proxy required.** The Behance Email Scraper cannot run without Apify proxy credentials with access to the GOOGLE\_SERP group.

**Free-plan cap.** Running the Behance Email Scraper on a free Apify plan means results are capped at 100 emails per run. Paid plans are uncapped.

**Handle availability.** `username` and `profileUrl` are only populated when Behance exposes a handle in the Google result. Some rows will carry `accountName` and `fullName` with an empty `username` and `profileUrl`. That is a Google indexing limitation, not a bug.

**No guaranteed volume.** Results vary with keywords, domains and location. Nothing here is a promised yield.

The Behance Email Scraper is not affiliated with, endorsed by or officially supported by Behance or Adobe.

***

### Related Actors

Every Actor below runs the same engine as the Behance Email Scraper, with identical input fields and an identical output schema; only the target platform differs.

| Actor | What it collects |
|---|---|
| [Behance Email and Phone Number Scraper](https://apify.com/leads-scraper/behance-email-and-phone-number-scraper) | Emails and phone numbers from Behance |
| [Behance Phone Number Scraper](https://apify.com/leads-scraper/behance-phone-number-scraper) | Public phone numbers 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 |
| [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 |

### Worked example: building a motion-design shortlist

You need 200 freelance motion designers in the UK for a rolling production roster.

Set `keywords` to `["motion designer", "motion graphics artist", "3d animator"]`, `location` to `"United Kingdom"`, `countryCode` to `"GB"`, `customDomains` to `["@gmail.com"]` and `maxEmails` to `200`.

With expansion on, the Behance Email Scraper issues base, quoted and `intitle:` variants plus one per modifier — roughly a dozen distinct queries per keyword × domain pair, each paginated separately.

Export the Behance Email Scraper dataset to CSV, drop rows where `possiblyTruncated` is `true`, sort by `keyword` to see which niche term converted best, and hand the shortlist to your recruiter.

***

### FAQ

#### What is the Behance Email Scraper?

It is an Apify Actor that extracts publicly indexed contact emails for Behance accounts by running domain-scoped Google searches and parsing the result blocks.

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

No. The Behance Email Scraper never logs in, never calls the Behance API and never opens a browser, so there are no cookies and no authentication anywhere in the pipeline.

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

The Behance Email Scraper reads publicly indexed titles, snippets and site labels, typically bios where the account owner published a contact address themselves.

#### Can it find private or hidden emails?

No. If an address is not publicly visible in Google's index, the Behance Email Scraper will not return it.

#### Why is `username` sometimes empty?

Google does not always expose a handle in the result. When it does not, you still get `accountName` and `fullName`, but `username` is `null` and `profileUrl` is empty.

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

Google's snippet ellipsis touched the email, so it may be cut off. Treat those rows as unverified and check them before sending.

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

The Behance Email Scraper accepts a `maxEmails` value between 1 and 10000, but free Apify plans are capped at 100 emails per run and paid plans are uncapped. Real volume depends on your keywords, domains and location.

#### Do I need a proxy?

Yes. The Behance Email Scraper requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

#### Should I leave query expansion on?

Usually yes. Google caps a single query at roughly 300 results, and expansion multiplies your reachable surface using the base, quoted, `intitle:` and modifier variants.

#### Can I restrict results to a country?

Yes — set `countryCode` for the search proxy and add a `location` phrase to bias the snippet text toward that region.

#### What happens if the run is interrupted?

The Behance Email Scraper persists state in the key-value store keyed by a hash of your input, with throttled saves plus saves on PERSIST\_STATE, MIGRATING and ABORTING, so an interrupted run resumes instead of restarting.

#### Is the data ready to email immediately?

Treat the Behance Email Scraper output as raw lead data. Deduplication is automatic, but verification, consent and compliance with GDPR, CAN-SPAM and Behance terms of service remain your responsibility.

***

### Leave a review

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

# Actor input Schema

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

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

## `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": [
    "designer",
    "illustrator"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "inquiries",
    "hire",
    "work with me"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Behance 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": [
        "designer",
        "illustrator"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "inquiries",
        "hire",
        "work with me"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/behance-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": [
        "designer",
        "illustrator",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "inquiries",
        "hire",
        "work with me",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/behance-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": [
    "designer",
    "illustrator"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "inquiries",
    "hire",
    "work with me"
  ]
}' |
apify call leads-scraper/behance-email-scraper --silent --output-dataset

```

## MCP server setup

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