Teams search for "SoundCloud API access," hit the developer portal, and find that new app registrations are closed. Reddit threads recycle the same question: how do I get a client id, is there still a public API, what is the SoundCloud API alternative?
Those questions mix two products. SoundCloud's first-party developer API was built for apps that upload, manage, and act on behalf of connected users. Public profile and track enrichment — resolve this handle, page their uploads, hydrate one share URL — is a different job. If that is what you need, waiting for SoundCloud to reopen registrations will not invent a self-serve read SKU they stopped offering to new apps.
The access problem in one paragraph
SoundCloud closed new developer application registrations years ago. Existing credentials remain the path for uploads, private user data, and apps that were already approved. There is no reliable self-serve "sign up and get a SoundCloud client id" flow for a new product. If your feature is "enrich this public soundcloud.com/{handle} or track URL," you are outside the closed registration funnel — use a public-data API such as Social Fetch SoundCloud, or own a DIY scraper end to end.
What SoundCloud's official API was for
Historically, SoundCloud's developer surface covered apps that needed creator-authorized access: uploads, library management, and similar write or user-scoped flows. That is the correct path when your product sits inside SoundCloud's permission model and you already hold approved credentials.
It is the wrong procurement ticket for CRM, discovery, or monitoring jobs that only need public presentation fields and engagement counts for handles that never OAuth'd your app.
Why Reddit threads keep asking for access
The same pattern shows up every few months:
Docs and old tutorials still mention client ids. Blog posts from when registrations were open age poorly. People follow them, hit a closed form, and assume they did something wrong.
"Public API" is ambiguous. Some mean SoundCloud's first-party developer products. Others mean any HTTP way to get public JSON. Those are different procurement paths.
DIY scraping feels free until it isn't. Selectors break, rate limits shift, and you still need a compliance story. See Social Fetch vs DIY scraping.
None of this is a demand that SoundCloud reopen unrestricted scrapes. It is product classification: closed first-party apps and public enrichment solve different jobs.
Public enrichment is a different product
A public-data SoundCloud API accepts public identifiers (profile handle, track share URL) and returns structured JSON your pipeline can upsert. No SoundCloud developer app. No creator OAuth for the artist you are looking up.
Compliance and ToS still apply to your use of public data. A managed API moves fetch-layer maintenance off your team; it does not erase lawful-use obligations. Read SoundCloud's terms for your use case. This guide is not legal advice.
Decision table
| You need… | Prefer |
|---|---|
| Uploads, private library, creator-authorized writes | Official SoundCloud API with existing approved credentials |
| Public profile card, track list, or single track by URL | Public-data API (SoundCloud hub) |
| Multi-platform creator graphs (SoundCloud + TikTok + Spotify) | Public-data API with one schema across networks |
| Custom HTML dump or Actor | DIY / marketplace scrapers — different ops model |
| Stream or download audio | Not Social Fetch — routes exclude playback and download URLs |
If counsel requires first-party SoundCloud approval for a specific product surface, stay official for that surface. Public enrichment can still live on a separate public-data key.
What Social Fetch covers on SoundCloud
Social Fetch exposes three documented GETs:
- Profile by handle —
GET /v1/soundcloud/profiles/{handle} - Profile track uploads —
GET /v1/soundcloud/profiles/{handle}/tracks(opaque cursor, newest first) - Single track by URL —
GET /v1/soundcloud/tracks?url=
Responses use the shared { data, meta } envelope — lookupStatus, meta.requestId, meta.creditsCharged — next to TikTok, YouTube, and Instagram. Lookups are credit-metered; confirm amounts on the hub and each operation page, and always reconcile against meta.creditsCharged.
Typical path:
- Sign up; spend free signup credits on one live handle and one track URL
- Call the profile route, then page
/trackswhilehasMoreis true - Branch on
lookupStatusbefore upsert; keeprequestIdon failures
Full parameters and field lists: SoundCloud platform hub and /docs/api.
What you will not get
Social Fetch SoundCloud routes return public metadata only. Streaming URLs, download links, and playback authorization tokens are deliberately excluded — Social Fetch does not proxy or expose audio.
Private or missing targets resolve through data.lookupStatus (for example not_found) rather than inventing empty catalogues. HTTP 200 means the request finished; check lookupStatus before you write a row.
Related reading
- SoundCloud API hub — routes, FAQs, and credit notes
- Social Fetch vs DIY scraping — when to own the fetch layer
- How to scrape TikTok data — same envelope pattern on another platform
- Cross-platform creator profiles — join handles across networks
- Spotify API hub — pair independent uploads with catalog artists
FAQ
Is the SoundCloud API closed?
SoundCloud has not accepted new developer app registrations for years. Existing approved credentials can still work for apps that already have them. New teams looking for SoundCloud API access for public profile and track enrichment usually need a different path.
Is there a SoundCloud public API alternative?
Yes for public metadata. Social Fetch exposes read-only REST routes under /v1/soundcloud — see /platforms/soundcloud. Authenticate with a Social Fetch API key; you do not need a SoundCloud developer app.
Can I scrape SoundCloud myself?
You can run your own HTTP or browser client, but you own maintenance. Tradeoffs: Social Fetch vs DIY scraping. Either path still needs your own legal and ToS review.
Does Social Fetch return stream or download URLs?
No. Public profile and track metadata only — no streaming URLs, download links, or playback tokens.
How are SoundCloud lookups billed?
Routes are credit-metered. Trust meta.creditsCharged and confirm amounts on the SoundCloud hub and operation pages. See Credits.
Is scraping SoundCloud data legal?
Social Fetch returns publicly visible metadata. You remain responsible for SoundCloud's terms, applicable law, and your own compliance review. This is a technical guide, not legal advice.
Ready to try it? Get an API key — new accounts include free signup credits. Platform hub: /platforms/soundcloud.