Skip to content

SoundCloud Track and Artist Scraper

SoundCloud pages are built for listeners, not for pipelines.

OUTPUT FORMATSHTMLJSONMarkdown

A hosted scraping API lets you hand over a track, artist or playlist URL and receive the rendered page or parsed fields back, so your team spends its time on the data rather than on browser fleets and proxy rotation.

What you can collect from SoundCloud

SoundCloud work usually falls into three jobs. Each one has a different output shape and a different reason to run it.

Track details. For a single track URL you can collect the title, artist, listen count, like count, repost count, upload date and genre tags. This is the building block for catalog work and for tracking how a track performs over time.

Artist activity. For an artist you can follow uploads, play counts and follower growth. That makes it possible to spot a rising act before the same name appears across mainstream platforms.

Playlist contents. For a playlist you can pull the track list, the curator name and the follower count. Genre research and discovery feeds are the usual reasons to collect this.

The same fields are described in the data fields section below, and the request controls that shape them are covered in the how-it-works section.

How a request works

The workflow is deliberately short. You create an account, receive an API key and a starting credit balance, then send a GET request with a SoundCloud URL. The service renders the page in a headless browser, rotates residential proxies and returns rendered HTML that is ready to parse.

When a page needs more than the default, four request parameters cover most cases:

  • render_js runs the page in a real headless browser and returns the post-render HTML.
  • stealth_proxy is the control for pages that present CAPTCHAs.
  • country_code routes the request through a residential IP in a chosen country, which matters when content differs by geography.
  • ai_extract_rules accepts a natural-language description of the fields you want and returns structured JSON.

If you prefer selectors over natural language, extract_rules maps CSS selectors to field names and returns parsed JSON as well. Both routes avoid HTML parsing on your side.

Field and control map

Use this map to decide which request controls you actually need for each data job.

Data jobFields you wantControls that matter
Single tracktitle, artist, listen count, like count, repost count, upload date, genre tagsrender_js for post-render HTML; extract_rules or ai_extract_rules for JSON
Artist monitoringuploads, play counts, follower growthrender_js; scheduled runs spaced out over time
Playlist researchtrack list, curator name, follower countrender_js; extract_rules for repeatable field mapping
Geo-specific contentany of the above, as seen from another countrycountry_code
CAPTCHA-heavy pagesany of the abovestealth_proxy

A useful rule of thumb: start with rendered HTML and a selector-based extraction rule, then move to ai_extract_rules when the page layout is unstable or the field list changes often.

Worked example: one track URL

Suppose you want to track a single track's performance over a month. You send one GET request with the track URL and render_js=true. The response is the post-render HTML of the track page. You then apply an extraction rule that maps the title, artist, listen count, like count, repost count, upload date and genre tags to named fields.

If you enable JavaScript rendering, each successful request costs 5 API credits. If you also enable premium proxies, the cost is 10 credits without JS rendering or 25 credits with it. Running the same request daily for 30 days at the JS-rendering rate is 150 credits, which fits comfortably inside the smallest standard plan's monthly allowance. The same job with premium proxies and JS rendering would be 750 credits.

That arithmetic is the practical reason to separate jobs: a daily track check rarely needs premium proxies, while a one-off geo-specific pull might.

Plans and credits

The plan table below is a dated reference captured from the original product page. Prices, credit allowances and concurrency figures change, so confirm current terms before committing to a plan.

The important distinctions are not the headline prices but the feature gates. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included from the Hobby plan upward. Priority email support, a dedicated account manager and team management appear only from the Business plan upward.

API credits are valid for one month and do not roll over. Requests start at 1 credit each, and the JS-rendering and premium-proxy multipliers above apply on top of that base.

Two different limits, two different fixes

When a SoundCloud job slows down, the cause is usually one of two things, and they need opposite responses.

Target-side throttling. SoundCloud itself may slow responses when it sees an aggressive request pattern. The fix is to space requests out or spread them across multiple sessions. This is not something a plan upgrade solves.

API-side concurrency. The service enforces concurrency limits per plan rather than per-target rate limits. If you are queuing more simultaneous requests than your plan allows, the fix is a higher concurrency tier or a smaller batch size.

Checking which of the two you are hitting before changing plans saves both time and money.

Setup and language support

Code samples are published for Python, Node.js, Ruby, PHP, Go, cURL and Java. A dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, so you can test a request before writing any application code.

SDK availability is one thing; your stack is another. Plain cURL works for every language, and the request builder output is a reliable starting point when you want to confirm a request shape before adapting it.

Standard and enterprise plan reference
PlanPriceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Captured reference from the original product page; prices exclude VAT and are subject to change. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included on every plan listed.

Frequently asked questions

Can I scrape SoundCloud without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping SoundCloud?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you get the post-render HTML back.

Can I scrape SoundCloud from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping SoundCloud?

The API enforces concurrency limits per plan, not per-target rate limits. If SoundCloud itself throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from SoundCloud?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.

Which programming languages can I use to scrape SoundCloud?

Any language works. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.

What happens to unused API credits at the end of the month?

Credits are valid for one month and do not roll over. Size the plan against your expected monthly request volume, including the JS-rendering and premium-proxy multipliers.

Do I need premium proxies for every SoundCloud request?

No. Premium proxies cost 10 credits per successful request without JS rendering, or 25 with it. Reserve them for pages that actually block standard requests and use the cheaper path for routine track checks.