SoundCloud API. Open to new developers.
SoundCloud stopped accepting new API apps years ago. Get public profiles, uploads and tracks by handle or URL as JSON, with one API key.
- No SoundCloud app
- Profiles and tracks
- Failed lookups aren't charged
Teams running monitoring, research, and enrichment pipelines
Why Social Fetch
We run the SoundCloud scrapers. You build the product.
Live SoundCloud data as JSON — proxies, platform changes and consistent output handled for you.
SoundCloud, plus every other network
One key and one response envelope for SoundCloud and 24 more platforms — profiles, posts, search, comments and transcripts.
Pricing you can reason about
One request, one credit. Know how far your balance will go before you run your next batch.
Live data on every request
Fetch public data when you ask for it — not from a shared cache.
No scraper maintenance
We handle proxies, browser changes, and platform breakages.
Built for production jobs
Run concurrent workloads with explicit statuses and request IDs.
Regular jobs. Better rates.
Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.
What SoundCloud data can you get?
3 endpoints, one API key. Every response comes back as live JSON in the same envelope.
Profiles & channels
Look up a SoundCloud account by handle or URL — bio, counts and metadata.
Content
Fetch a single post or video by URL, with metrics and media.
Browse all 3 SoundCloud endpoints
What teams build with SoundCloud data
Monitoring, enrichment, research and content workflows on SoundCloud data — the same API as every other platform.
How it works
Your first request in three steps.
Use TypeScript or your automation tool of choice.
Sources
+ 19 more platforms
One request
GET/v1/tiktok/profiles/
x-api-key: sk_live_••••••••
Same JSON shape
{
"data": {
"lookupStatus": "found",
"profile": {
"platform": "tiktok",
"handle": "charlidamelio",
"displayName": "charli d’amelio",
"verified": true
},
"metrics": {
"followers": 160263648
}
}
}Step 1
Create your free account
Get an API key with 100 requests included.
Step 2
Choose an endpoint
Pass a username, URL, keyword, or post ID.
Step 3
Get clean JSON
Use the response immediately or send it into your pipeline.
Works with your stack
Code, automate, or connect your AI.
TypeScript
n8n
- Make
- Apify
- MCP
- AI clients
Pricing
Social data, priced simply.
Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.
Starter
18,000credits
$1.61 per 1k · $0.00161 per request
- Top up from $1.61 / 1k if you run out
- Up to 25 monitors
Growth
50,000credits
$1.58 per 1k · $0.00158 per request
- Top up from $1.58 / 1k if you run out
- 5 team seats
- Up to 100 monitors
Scale
150,000credits
$1.50 per 1k · $0.00150 per request
- Top up from $1.50 / 1k if you run out
- 25 team seats
- Up to 250 monitors
- Cancel anytime
- 30-day money-back guarantee
- Price locked while you stay
Need 1M+ credits, invoicing, or volume rates? Talk to us
Trust signals
DevHunt
Product Hunt
Uneed
Customers
Teams building on Social Fetch.
“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”
“Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”
“Live profile data on every request. We never flag accounts from a stale cache.”
“Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”
SoundCloud API: common questions
Is there a SoundCloud scraper API / SoundCloud data API?
Yes. Social Fetch provides REST routes for public SoundCloud profiles, their track uploads, and single tracks. Authenticate with a Social Fetch API key (x-api-key); you do not need SoundCloud developer credentials for these public lookups.
What SoundCloud data does Social Fetch cover?
Three operations under the SoundCloud tag: GET /v1/soundcloud/profiles/{handle}, GET /v1/soundcloud/profiles/{handle}/tracks, and GET /v1/soundcloud/tracks. Profile responses include display name, bio, avatar and banner, location, verification, and counts for followers, tracks, playlists, and likes. Track responses include title, description, genre, tags, artwork, duration, release metadata, a creator snapshot, and engagement metrics. Exact fields are on each endpoint page and in /docs/api.
Do I need a SoundCloud developer app or OAuth?
No. You only need a Social Fetch API key. This matters more on SoundCloud than most platforms, because new SoundCloud API application registrations have been closed for an extended period — public lookups through Social Fetch do not depend on getting approved.
How does pagination work on profile tracks?
GET /v1/soundcloud/profiles/{handle}/tracks returns a page of tracks plus data.page.nextCursor and data.page.hasMore. Pass nextCursor back as the cursor query param to fetch the next page, and stop when hasMore is false. Treat the cursor as opaque — do not construct or parse it yourself.
Can I download tracks or get stream URLs?
No. These routes return public metadata only. Streaming URLs, download links, and playback authorization tokens are deliberately excluded from the response — Social Fetch does not proxy or expose audio.
Why are label, ISRC, and release date sometimes null?
Because much of SoundCloud is independent uploads that carry no release metadata at all. Those fields are nullable on every track and are always present as keys, so a bedroom-producer upload and a label release parse against the same schema. Do not treat a null label as a parsing failure.
What identifiers do SoundCloud routes accept?
Profile routes take the handle as a path segment — the slug from soundcloud.com/{handle} — with or without a leading @. The track route takes a full public track URL in the url query param. If you pass a profile URL to the track route it returns 400 and points you at the profile endpoint.
How much does the SoundCloud API cost on Social Fetch?
You buy credit packs (or use the 100 free signup credits). Profile, profile-tracks, and track requests cost 1 credit each on a successful completed request, and each page of a track listing is its own request. There is no required monthly subscription for pay-as-you-go packs. Always check meta.creditsCharged.
Does HTTP 200 always mean the profile or track was found?
No. HTTP 200 means the request finished. Check data.lookupStatus: found means you got data; not_found means the handle or URL did not resolve. Persist meta.requestId when you need to debug a miss.
Can I use SoundCloud routes from agents or MCP?
Yes. The same operations appear as typed MCP tools and can be reached via Ask (POST /v1/ask) for plain-English exploration. For production jobs, pin the typed GET paths so routing stays explicit.
Is scraping SoundCloud data legal?
Social Fetch returns publicly visible profile and track metadata. You are responsible for how you use it under SoundCloud's terms, applicable law, and your own compliance review. We do not give legal advice.
The SoundCloud API in detailHow the SoundCloud routes work, what they cost, and how they differ from the official API.
Why teams use Social Fetch for SoundCloud
SoundCloud surfaces independent music that often has no ISRC or label catalog entry. Social Fetch exposes three GETs: profile by handle, cursor-paginated track uploads, and single track by URL. Every response uses { data, meta } with data.lookupStatus, meta.requestId, and meta.creditsCharged.
How to call the SoundCloud API
1. Create an API key
Sign up at Social Fetch and copy a key (
sfk_…). New accounts get 100 free credits — enough to smoke-test profile, track-listing, and single-track GETs against live data.2. Call a SoundCloud route
Send
GET /v1/soundcloud/profiles/{handle}withx-api-key, then/trackson the same handle to page uploads, orGET /v1/soundcloud/tracks?url=…for one track. Use the TypeScript SDK or curl in production jobs; keep the playground for one-off checks in the app.3. Page and persist
Branch on
data.lookupStatusbefore writing. For listings, passdata.page.nextCursorback ascursoruntilhasMoreis false. Logmeta.requestIdfor support; bill frommeta.creditsCharged.
What each SoundCloud route returns
- Profile lookups by handle — display name, bio, avatar and banner, city and country, verification, plus follower, track, playlist, and like counts.
- Profile track listings with an opaque cursor, newest first, for paging a full back catalogue.
- Single track lookups by share URL — title, description, genre, tags, artwork, duration, and a creator snapshot.
- Release metadata when the upload has it: label, ISRC, album, credited artist, and explicit flag — all nullable, so independent uploads parse the same way as label releases.
- Engagement metrics on every track: plays, likes, reposts, comments, and downloads.
- Same Social Fetch API key and response envelope as TikTok, YouTube, Instagram, and the rest of the marketplace.
How much does the SoundCloud API cost?
SoundCloud profile, profile-tracks, and track routes charge 1 credit per successful completed request. A tracks page costs 1 credit whether it returns one row or twenty, so paging a long back catalogue costs 1 credit per page. Credits never expire on pay-as-you-go packs. Confirm every response with meta.creditsCharged — that field is the billing source of truth.
Social Fetch vs the official SoundCloud API
SoundCloud's developer API has been closed to new applications for years. Existing credentials remain the path for uploads and private user data. Social Fetch routes are public read-only enrichment with a Social Fetch API key — no SoundCloud app, no creator OAuth.
Pull your first SoundCloud data.
Run a live SoundCloud request in the playground. 100 free credits, no card, JSON back in seconds.
No credit cardSign up in 30 seconds withGoogleGitHub