SoundCloud data API
Look up public SoundCloud profiles by handle, page through their uploads, and resolve single tracks by URL. Structured JSON you can store next to TikTok and YouTube creator rows — no SoundCloud developer app required for read-only lookups.
3 endpointsWhy teams use Social Fetch for SoundCloud
SoundCloud is where a lot of independent music surfaces first — bedroom producers, remixes, and unsigned artists who never appear in a label catalog. That makes it useful for A&R and creator-discovery work, and awkward to query: the interesting accounts are exactly the ones with no ISRC, no label, and no release date attached.
SoundCloud's own API has been effectively closed to new applications for years, so teams end up scraping the web player themselves and maintaining brittle selectors, pagination quirks, and a second auth stack beside the scrapers they already run for TikTok and Instagram.
Social Fetch exposes three SoundCloud GETs under one marketplace key: a profile by handle, that profile's track uploads as a cursor-paginated list, and a single track by URL. Every response uses the same `{ data, meta }` envelope as the rest of the catalog — `data.lookupStatus`, `meta.requestId`, `meta.creditsCharged` — so SoundCloud rows normalize beside your existing social data instead of needing their own pipeline.
What SoundCloud data can you get?
- 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.
SoundCloud API endpoints
Routes from the live API catalog. Open an endpoint for parameters and examples — credit notes come from OpenAPI pricing extensions.
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}` with `x-api-key`, then `/tracks` on the same handle to page uploads, or `GET /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.lookupStatus` before writing. For listings, pass `data.page.nextCursor` back as `cursor` until `hasMore` is false. Log `meta.requestId` for support; bill from `meta.creditsCharged`.
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 has a developer API, but new application registrations have been closed for an extended period, so most teams cannot obtain credentials for it at all. Where you do hold existing SoundCloud API credentials, that remains the right tool for authorized and write operations — uploading, managing your own tracks, or reading private user data. Social Fetch SoundCloud routes are public read-only enrichment: handle or share URL in, structured JSON out, no SoundCloud app and no creator OAuth. Choose official for write and private-user cases; choose Social Fetch when SoundCloud is one enrichment source beside social networks on a shared marketplace key.
SoundCloud API FAQ
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.
Start with SoundCloud data
Create an account, spend the 100 free credits on live SoundCloud routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.