# Audiomack Email Scraper - Keyword Search & Domain Filter (`parse-point/audiomack-email-scraper-lightning-fast-and-accurate`) Actor

🎵 Audiomack Email Scraper extracts artist and label emails using keyword and location filters. 🎯 Limit results to specific domains, decode obfuscated addresses and drop duplicates. 🎤 Fast music promo lead generation.

- **URL**: https://apify.com/parse-point/audiomack-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.99 / 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.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

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

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

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

# README

### Audiomack Email Scraper

**Audiomack Email Scraper** helps you extract email addresses from Audiomack based on your chosen keywords—ideal for OSINT email discovery, bulk email list building, and lead generation automation. It’s a practical **audiomack email scraper** and **audiomack contact extraction** tool that turns publicly available contact data into an exportable dataset, faster than manual research or ad hoc web scraping.

***

### What Does Audiomack Email Scraper Do? 🤖

The **Audiomack Email Scraper** takes your keywords (plus optional location and email-domain filters) and runs an automated collection process to find and extract emails from Audiomack. During a run, it scrapes relevant Audiomack profile data, filters discovered email addresses to your selected domains, and exports structured results to your Apify dataset. You can **extract emails from Audiomack**, perform **audiomack contact scraper**-style discovery, and **automate audiomack email collection** without repeatedly checking profiles by hand. This is especially useful when you want consistent scale for marketing, outreach, or research workflows.

***

### What Can Audiomack Email Scraper Extract? 📊

This actor outputs a clean, structured dataset that focuses on contact-level results plus the context needed for outreach. It captures the keyword that surfaced a lead, the profile identity/details, and the exact profile URL alongside the extracted email.

| Data Type | Field Name | Description |
|---|---|---|
| Contact | `email` | Primary email address found in the Audiomack profile data |
| Identity | `title` | Profile name or business handle associated with the result |
| Context | `description` | Bio, summary, or profile tagline text used during extraction |
| Discovery | `keyword` | The keyword from your input that surfaced this profile |
| Navigation | `url` | Direct link to the relevant Audiomack profile page |

***

#### Key Features of Audiomack Email Scraper ⚡

- ✅ **Keyword-Driven Email Discovery**: Uses your keywords to surface Audiomack leads for email address extraction (great for audiomack email scraper workflows).
- 🌍 **Location Targeting**: Optionally filters results to a specific location to help you find the most relevant contacts.
- 📧 **Custom Domain Filtering**: Limits extracted emails to the domains you specify (for example `@gmail.com`), improving lead targeting and data consistency.
- 🔄 **Proxy-Ready & Reliable**: Built for reliable data collection with built-in proxy support for more stable scraping at scale.
- 📊 **Structured JSON Output**: Produces clean, labeled results for easy import into CRMs, spreadsheets, or analysis tools.
- 💾 **Real-Time Saving to Dataset**: Results are pushed incrementally during the run so you can review progress as it collects.
- ⚙️ **Configurable Result Limits**: Control run size and cost with `maxEmails`, supporting efficient bulk email list building.
- 🧹 **De-duplication by Email**: Avoids repeating emails that were already discovered in the same overall run.

***

### How to Use Audiomack Email Scraper 🚀

1. **Find the Actor** — Open **Audiomack Email Scraper** on the [Apify Store](https://apify.com/store).
2. **Open Input Tab** — Go to the Input tab in the Apify Console.
3. **Add Keywords** — Enter job titles, roles, or business-related terms you want to use for finding audiomack profiles.
4. **Configure Filters** *(optional)* — Add a location and choose `customDomains` to narrow which email types you want.
5. **Set Result Limit** — Choose a `maxEmails` value to cap how many emails you collect.
6. **Click Start** — Run the actor and monitor logs as it scrapes data.
7. **Download Results** — Export your dataset in the Apify Dataset tab for downstream outreach and CRM enrichment.

***

### Audiomack Email Scraper Output Format 📦

The actor saves results to your Apify dataset as structured JSON records. Each record includes the lead context (keyword, title, description, url) and the extracted `email`.

#### ⬇️ Input Example

```json
{
  "keywords": ["manager", "founder"],
  "location": "",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 20
}
```

#### ⬆️ Output Example

```json
[
  {
    "keyword": "manager",
    "title": "Jordan Rivers",
    "description": "Artist management & bookings. For collaborations and business inquiries: jordan.rivers@gmail.com",
    "url": "https://audiomack.com/jordanrivers",
    "email": "jordan.rivers@gmail.com"
  },
  {
    "keyword": "founder",
    "title": "Maya Chen",
    "description": "Founder • Music production and distribution. Contact: maya.chen@yahoo.com",
    "url": "https://audiomack.com/mayacheno",
    "email": "maya.chen@yahoo.com"
  }
]
```

***

### 🎯 Use Cases of Audiomack Email Scraper

**B2B Lead Generation:** Build targeted email lists by using role-based keywords to find relevant Audiomack profiles, then filter by email domains for tighter outbound lists.

**Email Marketing Campaigns:** Quickly gather audiomack contact extraction results for newsletters, promotional outreach, and drip sequences—without manual profile checks.

**Talent Recruitment:** Identify creators and professionals and enrich your pipeline with email address extraction from publicly available Audiomack profile information.

**Market Research:** Map niche communities by running OSINT email discovery using different keywords, then analyze which segments produce the most contactable leads.

**CRM Enrichment:** Add scraped audiomack profiles with emails into your CRM to power contact personalization and improved lead management automation.

***

### How Much Will Audiomack Email Scraper Cost You? 💰

This **audiomack email scraper** is charged using Apify’s pay-per-result model. You typically think of it as **pay-per email result**, so the most important lever is `maxEmails`: set it to control how many results you want per run. Apify also includes a free tier with compute credits for new users. For best cost control, start small (e.g., the default `20`) and increase only after you see yield quality.

***

### Is It Legal to Scrape Audiomack? ⚖️

The **Audiomack Email Scraper** works with **publicly available data** and does not access private profiles or password-protected content. Scraping public web data is often considered lawful, but legality can depend on your jurisdiction and the website’s Terms of Service. Always comply with applicable privacy and anti-spam requirements (such as GDPR/CCPA where relevant) and use extracted data responsibly for legitimate purposes like research, recruitment, or outreach. If you have concerns or questions about data handling, contact <helloparsepoint@gmail.com>.

***

### Audiomack Email Scraper Input Parameters 📋

See the actor input form for the exact schema, or use the example below. Required and defaults are taken directly from the actor specification.

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | `["manager","founder"]` | A list of keywords or queries used to find relevant Audiomack profiles to extract emails from. |
| `location` | String | No | `""` | Optional location filter to help narrow results (e.g., targeting a specific city or region). |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | Email domains to allow. Use this to focus on specific providers and improve outreach list quality. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect. The scraper stops once it reaches this limit (higher values can take longer). |

***

### During the Actor Run ⏱️

You’ll see live progress in the Apify Console as it processes your keyword and domain combinations. Results are saved incrementally, so you can check the Dataset tab while the run is still executing. Total time depends on how many results are found and your `maxEmails` limit, plus overall network conditions. If you get few results, broaden keywords, add related terms, or adjust `customDomains` and/or `location`.

***

### Final Note ✉️

Start extracting Audiomack emails today—fast, structured, and ready for outreach automation. Try **Audiomack Email Scraper** in Apify, then export your dataset for CRM enrichment or email list building. Questions or special requests? Email <helloparsepoint@gmail.com>.

***

### FAQ — Audiomack Email Scraper ❓

#### How does the Audiomack Email Scraper find emails?

It uses the keywords you provide to locate relevant Audiomack leads, then extracts email addresses from publicly available Audiomack profile information. It applies your `customDomains` filter so returned emails match the domains you allow.

#### What types of Audiomack profiles can I scrape?

The actor is designed to work with public Audiomack profiles that contain contact information in the publicly accessible content. If a profile doesn’t include an email address that matches your domain filters, it won’t produce an email result.

#### What did your tests show about the Audiomack Email Scraper?

Result volume depends on how many Audiomack profiles in your keyword set include public email contact information, and how restrictive your domain and location filters are. Using targeted role keywords and domain filters generally improves yield for audiomack contact extraction and lead generation automation.

#### Why scrape Audiomack for emails?

Audiomack is a high-signal source for niche creator and business contacts. Instead of spending hours on manual lookup, this audiomack email scraper automates OSINT email discovery and produces a structured dataset you can use for outreach, CRM enrichment, or analysis.

#### How much does it cost to use the Audiomack Email Scraper?

It follows Apify’s pay-per-result pricing—typically meaning you’re charged per email result collected. Use `maxEmails` to cap spending per run. For budget planning, consider starting with the default `20`, then scaling up only when you’re satisfied with result quality and volume.

#### How does the Audiomack Email Scraper help my business?

It reduces the time needed to build email lists from audiomack profiles. The output includes the extracted `email` plus context fields like `keyword`, `title`, `description`, and `url`, so you can quickly enrich leads, segment outreach, and automate follow-up workflows.

#### What are the challenges of using an Audiomack scraper?

Not every Audiomack profile includes a public email address, so results can vary widely by niche and keyword selection. If you see low yield, try broader keywords, include related terms, and review your `customDomains` and optional `location` filter to ensure they aren’t overly restrictive.

#### How do I choose the right Audiomack Email Scraper settings?

Start with focused keywords (for example role-based terms like “manager” or “founder”), keep `customDomains` aligned with your preferred outreach domains (such as `@gmail.com`), and set `maxEmails` to a value that matches your budget and desired run duration. Then iterate: broaden keywords or adjust domain filters if results are below expectations.

***

### 🆘 Support & Feedback

Need help configuring your run or want a tailored improvement for this **audiomack email scraper**?

Email us at <helloparsepoint@gmail.com>. We’re happy to help with workflows, optimization tips, and feature requests for audiomack contact extraction and bulk email list building.

### Run Memory

**Skip keywords already scraped in a previous run** - the actor keeps a
persistent record of every keyword it finishes, in a named key-value store that
survives between runs. Turn this on and a repeat run silently drops the keywords
it has already covered, so a scheduled job over a fixed list only pays for new
ground.

A keyword is identified by the keyword *plus* the set of email domains it was
searched against, so re-running `fitness` against a new domain list is correctly
treated as new work rather than a duplicate.

**Reset keyword history** - wipe that record before the run starts, so
everything counts as new again.

**Max emails per keyword** - cap how many results any single keyword may
produce before the actor moves on to the next one. Stops one broad term from
consuming the entire run budget. `0` means no per-keyword limit.

These sit alongside the existing address-level deduplication: *Skip previous
runs* prevents re-pushing an individual mailbox, while *Skip duplicate keywords*
prevents re-running the search at all.

# Actor input Schema

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

A list of keywords or queries to search for.

## `location` (type: `string`):

Location to filter search results.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `decodeProtectedEmails` (type: `boolean`):

Read addresses the page hides behind Cloudflare protection or HTML entities. These are invisible to a plain text scan.

## `decodeWrittenEmails` (type: `boolean`):

Read addresses written to defeat scrapers, such as 'name \[at] example \[dot] com'.

## `decodeEncodedEmails` (type: `boolean`):

Read addresses stored base64-encoded in the page markup.

## `mergeAliasDuplicates` (type: `boolean`):

Collapse different spellings that reach the same inbox (e.g. j.o.h.n+news@gmail.com and john@gmail.com) into a single result, so you are not billed twice for one lead.

## `skipPreviousRuns` (type: `boolean`):

Do not return leads that an earlier run of this Actor already returned. Skipped leads are never charged.

## `duplicateHandling` (type: `string`):

What to do when several spellings reach the same inbox: merge them into one result, keep them apart but flag them, or keep everything as found.

## `skipDuplicateKeywords` (type: `boolean`):

Remember every keyword this actor completes and skip it next time. Ideal for a scheduled run over a fixed keyword list - you only pay for ground you have not covered. A keyword searched against a different set of email domains counts as new work, not a duplicate.

## `resetKeywordHistory` (type: `boolean`):

Clear the remembered keywords before this run starts, so everything is treated as new again. Use after changing your target list.

## `maxEmailsPerKeyword` (type: `integer`):

Stop collecting for a keyword once it has produced this many results, then move on to the next one. Keeps one broad term from consuming the whole run. Leave at 0 for no per-keyword limit.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "decodeProtectedEmails": true,
  "decodeWrittenEmails": true,
  "decodeEncodedEmails": true,
  "mergeAliasDuplicates": true,
  "skipPreviousRuns": false,
  "duplicateHandling": "merge",
  "skipDuplicateKeywords": false,
  "resetKeywordHistory": false,
  "maxEmailsPerKeyword": 0
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("parse-point/audiomack-email-scraper-lightning-fast-and-accurate").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("parse-point/audiomack-email-scraper-lightning-fast-and-accurate").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call parse-point/audiomack-email-scraper-lightning-fast-and-accurate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parse-point/audiomack-email-scraper-lightning-fast-and-accurate"
        }
    }
}

```

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/oY4sidJuxRZqHkjKV/builds/7prb2idJc8W5H2aZY/openapi.json