# SoundCloud Email Scraper (`leads-scraper/soundcloud-email-scraper`) Actor

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

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

### SoundCloud Email Scraper

### SoundCloud Email Scraper — extract public artist booking emails from SoundCloud

The **SoundCloud Email Scraper** collects publicly indexed booking, management and demo-submission emails belonging to SoundCloud artists — producers, rappers, DJs, beatmakers, electronic acts, singers and independent labels.

You supply keywords, an optional location and a list of email domains. The SoundCloud Email Scraper builds domain-scoped Google queries against `soundcloud.com`, parses the search results and extracts every matching address into a structured dataset.

No login, no SoundCloud API, no headless browser, no cookies. This SoundCloud email extractor works purely from what Google has already indexed publicly.

A\&R scouts, label managers, promoters, sync agencies and music-tech companies use the SoundCloud Email Scraper for contact discovery at a scale that manual profile browsing cannot reach.

***

### Features of the SoundCloud Email Scraper

Everything listed here is implemented in the SoundCloud 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 `soundcloud.com`, keeping results on-platform |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per query modifier |
| Music-tuned modifiers | Defaults include `booking`, `email`, `contact`, `management`, `demos` |
| Domain-filtered extraction | Only addresses on your `customDomains` list are collected |
| Global deduplication | Each unique email is written to the dataset once, across all queries and pages |
| Obfuscation-aware parser | Reads `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 `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 | Discards a hit that is only the tail of another email in the same block |
| Concurrency control | An `asyncio` worker pool runs queries in parallel with a shared stop signal |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are retried, not scored as empty |
| Resumable state | Progress is persisted in the key-value store, keyed by a hash of your input |
| Structural parsing | Blocks are found from the `<h3>` title, never from Google's CSS class names |
| Fallback parser | A markup change degrades to "emails without account details", not "no emails" |
| Streaming dataset writes | Leads reach the dataset immediately, so exports can start mid-run |

***

### How the SoundCloud Email Scraper works

The SoundCloud Email Scraper is a search-results crawler, not an audio crawler. It never opens soundcloud.com and never downloads a track.

**1. Read input.** Keywords, location, email domains, page caps and concurrency are validated.

**2. Build queries.** Queries use the `site:` operator, for example:
`site:soundcloud.com hip hop producer "@gmail.com" booking`.

**3. Expand queries.** With `expandQueries` on, each keyword × domain pair runs as a base query, a quoted variant, an `intitle:` variant and one variant per entry in `queryModifiers`. Base queries always go first.

**4. Fetch pages.** The SoundCloud 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.** The parser locates the `<h3>` title and then the smallest surrounding block, so titles, snippets and site labels stay bound to the right artist.

**6. Extract and normalise.** A domain-filtered regex pulls candidates from the block text, normalises them and drops junk, tails and boundary mismatches.

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

The SoundCloud 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 SoundCloud Email Scraper extract?

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

You receive the address, the matched domain, the account label, a parsed artist name, the handle and profile URL where SoundCloud exposes one, a cleaned bio or track snippet, and full provenance.

In music outreach the `description` snippet earns its keep: artist bios routinely spell out whether an address is for **booking**, **management**, **demos** or press, which tells you how to open the message.

***

### Input schema

Every SoundCloud 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) | `["artist", "producer"]` | Search terms describing the SoundCloud accounts you want (genre, role, scene) |
| `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; leading `@` 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 | `["booking", "email", "contact", "management", "demos"]` | 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 SoundCloud Email Scraper

```json
{
  "keywords": ["techno producer", "afrobeats artist", "lofi beatmaker"],
  "location": "London",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 400,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["booking", "email", "contact", "management", "demos"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output schema

Every item produced by the SoundCloud Email Scraper 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 (handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for track captions |
| `username` | URL-safe handle when SoundCloud exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct SoundCloud link when exposed, else the profile URL |
| `description` | Bio or track 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": "SoundCloud",
  "keyword": "techno producer",
  "query": "site:soundcloud.com techno producer \"@gmail.com\" booking",
  "title": "NOVA GRID | Free Listening on SoundCloud",
  "accountName": "novagrid",
  "fullName": "Nova Grid",
  "username": "novagrid",
  "profileUrl": "https://soundcloud.com/novagrid",
  "url": "https://soundcloud.com/novagrid",
  "description": "London techno producer and live act. Bookings & demos: novagrid.bookings@gmail.com",
  "email": "novagrid.bookings@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T13:47:11.706Z"
}
```

The SoundCloud 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 SoundCloud Email Scraper

**Step 1 — search by genre and role together.** `drum and bass producer`, `amapiano dj`, `trap beatmaker` and `indie vocalist` match how artists actually describe themselves.

**Step 2 — keep the music modifiers.** `booking`, `management` and `demos` are the exact words that precede a contact address in most artist bios.

**Step 3 — set `location` and `countryCode` for scene-specific outreach.** Promoters booking a local room care about city, not global reach.

**Step 4 — start at 20–50 emails.** Check that the results are the right tier — unsigned, mid-level or label-backed — before committing to a big run.

**Step 5 — separate booking from demo outreach.** Filter the export on `description` for the word `demos` when you are pitching a label, and `booking` when you are pitching a show.

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

***

### Use cases for the SoundCloud Email Scraper

| Use case | Who runs it | Typical keywords |
|---|---|---|
| A\&R and label scouting | Independent labels, A\&R teams | `techno producer`, `rnb singer`, `drill artist` |
| Show and festival booking | Promoters and venue bookers | `live act`, `dj`, `band` + `location` |
| Sync and licensing sourcing | Music supervisors, ad agencies | `instrumental`, `ambient`, `cinematic` |
| Beat and sample marketplaces | Producer platforms and plugin brands | `beatmaker`, `producer`, `sound designer` |
| Music PR and playlist pitching | PR firms and playlist curators | `indie pop`, `lofi`, `house` |
| Artist management scouting | Managers building a roster | `unsigned artist`, `rapper`, `vocalist` |
| Collaboration and feature outreach | Other artists and producers | `vocalist`, `topline`, `remix` |
| Scene and market research | Analysts mapping regional music scenes | any genre keyword by `location` |

SoundCloud remains where **unsigned and early-career artists publish first**, which makes the SoundCloud Email Scraper especially useful for discovery-stage outreach rather than established-roster work.

For DJ mixes and radio-style shows, pair it with the [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper). Artists who monetise through memberships are reachable via the [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper), while music video channels are better covered by the [YouTube Email Scraper](https://apify.com/leads-scraper/youtube-email-scraper) and live performers by the [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper).

***

### Why use this SoundCloud Email Scraper

Manual A\&R means opening profile after profile, reading bios and copying addresses. The SoundCloud Email Scraper compresses that into a single run producing a deduplicated dataset.

Every lead is traceable. The `query` and `keyword` fields show precisely which genre phrasing surfaced an artist, so you can double down on what works.

Extraction is conservative by design. Junk filtering, boundary-correct matching and soft-wrap repair mean fewer malformed addresses to clean before import.

Long SoundCloud 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 SoundCloud Email Scraper is deliberately transparent about its boundaries. Read these before planning a large data collection run.

**Only publicly indexed emails.** The SoundCloud Email Scraper returns addresses already visible in Google's index. Artists who route contact solely through SoundCloud messages will not appear.

**Google's per-query ceiling.** A single query returns roughly 300 results at most, which is exactly why query expansion is on by default.

**`possiblyTruncated`.** When Google's snippet ellipsis clips an address, this field is `true` and the email may be incomplete. Verify before sending.

**Apify GOOGLE\_SERP proxy required.** The SoundCloud Email Scraper cannot run without Apify proxy credentials that include the GOOGLE\_SERP group.

**Free-plan cap.** Running the SoundCloud 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 populated only when Google's result exposes a SoundCloud handle. Some rows will have `accountName` and `fullName` with an empty `username` and `profileUrl` — a Google limitation, not a bug.

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

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

***

### Related Actors

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

| Actor | What it collects |
|---|---|
| [SoundCloud Email and Phone Number Scraper](https://apify.com/leads-scraper/soundcloud-email-and-phone-number-scraper) | Emails and phone numbers from SoundCloud |
| [SoundCloud Phone Number Scraper](https://apify.com/leads-scraper/soundcloud-phone-number-scraper) | Public phone numbers from SoundCloud |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [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 |
| [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: booking a regional club tour

You are booking a six-city European techno tour and need 300 artist or management contacts.

Set `keywords` to `["techno producer", "live techno", "techno dj"]`, `location` to `"Berlin"`, `countryCode` to `"DE"`, `customDomains` to `["@gmail.com"]` and `maxEmails` to `300`.

The SoundCloud Email Scraper issues base, quoted and `intitle:` variants plus one query per modifier, paginating each independently and streaming deduplicated leads into the dataset.

Export the SoundCloud Email Scraper dataset to CSV, drop `possiblyTruncated` rows, split the list on whether `description` mentions `booking` or `management`, and route each half to the right pitch template. Repeat with a new `location` for the next city.

***

### FAQ

#### What is the SoundCloud Email Scraper?

An Apify Actor that extracts publicly indexed booking and contact emails for SoundCloud artists by running domain-scoped Google searches and parsing the search results.

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

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

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

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

#### Can it get emails from private or unlisted tracks?

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

#### Why do some rows have `username: null`?

Google does not always print a handle in the result. Those rows still carry `accountName` and `fullName`, but `username` is `null` and `profileUrl` is empty.

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

Google's snippet ellipsis touched the address, so it may be cut off. Verify before sending a booking request.

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

The SoundCloud 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 the Apify proxy?

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

#### Should I keep query expansion on?

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

#### How do I target one city's scene?

Set `location` to the city and `countryCode` to its two-letter code, then repeat the run per city rather than trying to cover a whole region in one pass.

#### Is the run resumable after a migration?

The SoundCloud 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.

#### Can I send demos or booking requests immediately?

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

***

### Leave a review

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

# Actor input Schema

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

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

## `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": [
    "artist",
    "producer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "booking",
    "email",
    "contact",
    "management",
    "demos"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by SoundCloud 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": [
        "artist",
        "producer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "booking",
        "email",
        "contact",
        "management",
        "demos"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/soundcloud-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": [
        "artist",
        "producer",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "booking",
        "email",
        "contact",
        "management",
        "demos",
    ],
}

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

```

## MCP server setup

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