SoundCloud Tracks Search Scraper

Scrape public SoundCloud track search results and public profile tracks for music research, creator discovery, and campaign monitoring.

What does SoundCloud Tracks Search Scraper do?

This actor collects public track metadata from SoundCloud.

It can run keyword searches such as lofi beats, indie pop, or techno remix.

It can also collect tracks from public SoundCloud profile URLs.

The output is a clean dataset with track, artist, engagement, and source-context fields.

Who is it for?

Music marketers use it to discover tracks and artists around target genres.

Creator agencies use it to monitor public creator catalogs.

Playlist researchers use it to find songs and artists with engagement signals.

Trend analysts use it to compare public search results over time.

Content teams use it to build research lists for outreach and editorial planning.

Why use this actor?

• 🎧 Collect track metadata without manual copy-paste.
• 📈 Capture engagement metrics such as plays, likes, reposts, and comments.
• 👤 Include artist profile metadata in each row.
• 🔎 Combine search queries and profile URLs in one run.
• 📦 Export results as JSON, CSV, Excel, or via API.

What data can it extract?

Field group	Examples
Track identity	track ID, trackTitle, URL, permalink
Track metadata	description, created date, duration, genre, tags
Engagement	plays, likes, reposts, comments, downloads
Media	artwork URL, waveform URL
Publisher metadata	artist, album title, ISRC, release title
Artist profile	username, profile URL, avatar, country, followers
Run context	source type, query, profile URL, rank, scraped time

How much does it cost to scrape SoundCloud tracks?

The actor uses pay-per-event pricing.

There is a small run-start event and a per-track saved event.

The default target is about $0.50 per 1,000 track records before volume discounts.

Exact pricing is shown on the Apify actor page before you start a run.

Input overview

Use queries for SoundCloud search keywords.

Use profileUrls for public SoundCloud profile pages.

Use maxItems to cap the total number of track records.

Proxy settings are optional and normally not needed.

Example input

{
  "queries": ["lofi beats"],
  "profileUrls": [{ "url": "https://soundcloud.com/chillhopdotcom" }],
  "maxItems": 25,
  "proxyConfiguration": { "useApifyProxy": false }
}

Output example

{
  "trackId": 123456,
  "trackTitle": "Example Track",
  "url": "https://soundcloud.com/artist/example-track",
  "artistUsername": "artist",
  "playbackCount": 10000,
  "likesCount": 500,
  "sourceType": "search",
  "source": "lofi beats",
  "rank": 1,
  "scrapedAt": "2026-07-05T00:00:00.000Z"
}

How to run it

1. Open the actor on Apify.
2. Add one or more search queries.
3. Optionally add public SoundCloud profile URLs.
4. Set maxItems.
5. Click Start.
6. Download the dataset when the run finishes.

Search query tips

Use genre terms such as ambient, drum and bass, or house.

Use campaign terms such as brand names, moods, or event names.

Use artist names when you want search-result context rather than only profile tracks.

Run the same query regularly to monitor changes over time.

Profile URL tips

Use public SoundCloud profile URLs.

The actor returns public tracks from those profiles.

Private, deleted, or login-only tracks are not included.

For large profiles, increase maxItems.

Integrations

Send datasets to Google Sheets for review lists.

Export CSV files for CRM enrichment.

Use webhooks to trigger downstream workflows after each run.

Use the Apify API to schedule recurring searches.

Connect results to BI tools for trend dashboards.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/soundcloud-tracks-search-scraper').call({
  queries: ['lofi beats'],
  maxItems: 25
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('fetch_cat/soundcloud-tracks-search-scraper').call(run_input={
    'queries': ['lofi beats'],
    'maxItems': 25,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~soundcloud-tracks-search-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["lofi beats"],"maxItems":25}'

MCP usage

Use Apify MCP with this actor in Claude Code or Claude Desktop.

MCP tool URL:

https://mcp.apify.com/?tools=fetch_cat/soundcloud-tracks-search-scraper

Claude Code setup:

$claude mcp add apify https://mcp.apify.com/?tools=fetch_cat/soundcloud-tracks-search-scraper

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/soundcloud-tracks-search-scraper"
    }
  }
}

Example prompts:

• "Find 25 public SoundCloud tracks for lofi beats and summarize the top artists."
• "Scrape this SoundCloud profile and make a table of tracks by play count."
• "Run the SoundCloud scraper weekly and compare engagement trends."

Data quality notes

Counts come from public SoundCloud metadata at scrape time.

Some tracks may have missing descriptions, genre, or artwork.

Engagement numbers can change after the run finishes.

The actor keeps numeric counts as numbers where SoundCloud provides them.

Limits

The actor collects public metadata only.

It does not download audio.

It does not bypass private content.

It does not require user login.

Very large runs may take longer because SoundCloud results are paginated.

Legality

This actor is designed for public web data.

You are responsible for using the results lawfully and respecting applicable terms, privacy rules, and intellectual-property rights.

Do not use scraped data for spam, harassment, or unauthorized downloading.

FAQ

Can this actor download SoundCloud audio?

No. It extracts public track metadata only.

Can I combine searches and profiles?

Yes. Add both queries and profileUrls; maxItems is shared across all sources.

Troubleshooting

Why did my run return fewer tracks than requested?

SoundCloud may have fewer public tracks for the query or profile, or duplicate tracks may be removed across combined sources.

Why are some fields empty?

Some artists do not publish every metadata field. Empty optional fields are normal.

Should I use a proxy?

Usually no. Leave proxy settings disabled unless you have a specific network-routing need.

Related scrapers

• https://apify.com/fetch_cat/instagram-profile-posts-scraper
• https://apify.com/fetch_cat/tiktok-video-scraper
• https://apify.com/fetch_cat/youtube-community-posts-scraper

Changelog

Initial version: public track search and public profile track extraction.

Support

If a run fails, include the run ID and input when reporting the issue.

Field reference

trackId

trackTitle

url

permalink

apiUri

description

createdAt

displayDate

durationMs

genre

tags

artworkUrl

waveformUrl

playbackCount

likesCount

repostsCount

commentCount

downloadCount

downloadable

streamable

license

publisherArtist

publisherAlbumTitle

publisherIsrc

publisherReleaseTitle

artistId

artistUsername

artistFullName

artistProfileUrl

artistAvatarUrl

artistCity

artistCountry

artistFollowersCount

artistTrackCount

artistVerified

sourceType

source

query

profileUrl

rank

scrapedAt