Skip to the content

How to Get a SoundCloud API Key in 2026: What Self-Serve Credentials Actually Give You

A SoundCloud API key is a pair of strings: a Client ID and a Client Secret, issued to one registered application. How you get one has changed twice. SoundCloud's app registration portal was shut for years, then opened behind a review queue, and now a self-serve portal issues both values instantly to anyone holding an Artist Pro subscription. That is the short answer. The rest of this post covers what registration asks for, what the Client Secret may and may not touch, which playlist and library calls still need a listener's own OAuth grant, and what the terms rule out before you ship.

What a SoundCloud API key gets you

What you want to doToken you needListener consent
Search, playback, URL resolutionClient CredentialsNo
Read /me, read and write playlists, likes, follows, uploadsAuthorization CodeYes
Any call to the API at allRegistered app Client IDNot applicable

SoundCloud documents the split plainly: "Client Credentials: For applications accessing public resources only (search, playback, URL resolution). No user session required." The other half reads "Authorization Code: For applications that perform actions on a user's behalf (upload, access private content). Requires user consent."

Both flows run on OAuth 2.1, PKCE is required for the authorization code exchange, tokens are minted at https://secure.soundcloud.com, and every API request carries Authorization: OAuth ACCESS_TOKEN against the base URL https://api.soundcloud.com. The Client ID is not optional on either path: "Your client ID is required for all calls to the SoundCloud API".

Who can get credentials today

Three eras, in SoundCloud's own description. First the door was shut: "The app registration portal was closed, and getting a key was nearly impossible for new projects". Then came a review step, where creators "could finally request access by chatting with our chatbot Otto and submitting their ideas for review". Now the queue is gone. If you hold an Artist-Pro subscription you "can now instantly generate your own Client ID and Client Secret via our fully self-service portal".

The gate did not disappear, it moved. The documented prerequisite is explicit: "You need a SoundCloud Artist Pro subscription to register API applications and receive credentials".

That matters more for a company than for a solo builder. Your production credential now depends on a paid Artist Pro subscription under somebody's account, which SoundCloud requires to register applications and receive credentials, rather than on an approval thread you can hand to a compliance reviewer. Decide up front who owns that subscription, who can see the secret, and what happens when that person leaves. The same question shows up on every service that ties credentials to a personal account, which is why we wrote how to get a Qobuz App ID and Secret the same way.

How to register the app and print the key

The CLI is the documented recommendation, not the web form. "The CLI requires Node.js 18+. Run this one command from your terminal, cloud environment, or coding agent":

curl -fsSL https://raw.githubusercontent.com/soundcloud/api/master/scripts/sc-api-auth.mjs \
  | node --input-type=module - --remote \
    --name "My API App" \
    --description "What my integration does" \
    --website "https://example.com"

The --remote flag exists so the flow survives headless environments: "The --remote option prints a pairing URL (https://secure.soundcloud.com/activate/…). Open it on any device, sign in or create a SoundCloud account, and approve the pairing." The CLI then creates the app, or returns the credentials for an existing one, and prints the Client ID, the Client Secret and a credential JSON blob to the terminal.

There is a web path too: "If you prefer a browser workflow, visit Your Apps, create a new application, provide its name, description, and website, accept the terms, then copy the Client ID and Client Secret." Same page handles later edits, such as updating a redirect URI.

Registration asks for three things, and asks you to mean them: accurate App name, Description and Website. Then one storage rule that is worth reading twice, because coding agents have made it easy to break: "Store the Client Secret in environment variables or a secrets manager. Never commit it to source control, include it in a prompt, or expose it in client-side code."

What the Client Secret is allowed to touch

The secret buys you an application token, not a listener's library. Client Credentials gets you public resources only, and the exchange is Basic auth or nothing: "For the client_credentials grant type, only HTTP Basic authentication (Authorization: Basic...) is supported. Sending credentials in the request body is not supported."

curl -X POST "https://secure.soundcloud.com/oauth/token" \
  -H "accept: application/json; charset=utf-8" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -H "Authorization: Basic Base64(client_id:client_secret)" \
  --data-urlencode "grant_type=client_credentials"

One line in the guide decides your architecture: "Note: All clients are currently treated as confidential rather than public, meaning a secret is required to obtain a token." Put that next to the storage rule above and the conclusion is forced. Even a mobile or single page app has to do its token exchange on a server you control, because the secret cannot ship to the client and no token is issued without it.

Plan for churn in the token layer as well: "Access tokens expire after approximately 1 hour. Use the refresh_token to obtain a new access token. Each refresh token is single-use." Single-use refresh means your storage has to be transactional. Two workers refreshing the same listener at once will burn one token and leave the other holding a dead string. If you are building that logic for several providers at the same time, our notes on OAuth token refresh across multiple music streaming APIs cover the locking pattern.

Which operations still need a listener's grant

Everything that reads or writes a person's library. The authorization code flow sends the listener to https://secure.soundcloud.com/authorize with your client_id, a registered redirect_uri, a PKCE code_challenge and a state nonce, and returns a code you exchange for access_token, refresh_token, expires_in and scope.

With that token you reach /me for the profile, POST /playlists to create a playlist from a list of track IDs, PUT /playlists/:id to change its tracks, the /likes/tracks/:id and /likes/playlists/:id routes, and PUT /me/followings/:user_id for follows. Reads are paged: "Collection responses return up to 50 items by default (maximum 200). Pass linked_partitioning=true to enable pagination." Paginated responses carry a next_href, and its absence is your terminator.

curl -X GET "https://api.soundcloud.com/me/playlists?show_tracks=false&linked_partitioning=true&limit=25" \
  -H "accept: application/json; charset=utf-8" \
  -H "Authorization: OAuth ACCESS_TOKEN"

Two details bite import flows specifically. First, not every track behaves like every other: "Restricted tracks have no stream_url and their access field is set to blocked." Your per item results need a reason code for that case instead of a silent drop. Second, you owe users an exit. "Use POST /disconnect on the API base URL when your app should stop acting on behalf of a user: it revokes OAuth access for your application and invalidates access tokens your app issued for that user." It answers 204 on success, 401 on a missing or invalid token.

Rate limits are per application, not per user

"SoundCloud enforces API rate limits per registered application (client_id). Exceeding a limit returns HTTP 429 Too Many Requests." The general budget is modest: "The default budget is on the order of 100 requests per minute unless a stricter rule below applies." On top of that, "A general per-application request budget applies to most of https://api.soundcloud.com, plus additional, stricter caps on selected endpoints to reduce abuse."

Read that as a shared pool. Every listener importing a library at once draws from the same per application budget, so one enthusiastic user can starve the rest. Size the queue, not the request. Headroom exists but is granted, not configured: "Some applications that SoundCloud has approved for higher production access may receive up to 10× these limits on the same endpoint groups (including the general per-minute budget)."

Instrument against the response, not against a constant. "API responses include rate-limit headers for the limit that applied to that request", so read X-Ratelimit-Limit, X-Ratelimit-Remaining and X-Ratelimit-Reset per route and back off on Retry-After when a 429 arrives. The general shape of that work across providers is in our guide to handling rate limits across streaming APIs.

What the terms rule out before you design

The API Terms of Use constrain product decisions, not just legal boilerplate. Four clauses change architecture.

Auth has one approved path: "All requests for authenticated access to a user's SoundCloud account (other than your own account) must be made via the "Connect with SoundCloud" webview OAuth process, unless we've made a separate arrangement with you." No credential collection of your own.

Accounts stay separate: "Apps are not permitted to store Personal Data or User Content from multiple users in a single account. Each user must be able to authenticate and upload User Content from his/her own account."

Persistence is limited: "Your app must not include file-save functionality, or otherwise designed to cache, download or persistently store any User Content." And on revocation, "you shall discontinue accessing the applicable SoundCloud Personal Data and delete the applicable SoundCloud Personal Data in your possession or control without undue delay, but in any case within 7 days". Build the deletion job in week one, because retrofitting it into a warehouse is the expensive version.

If your roadmap includes model training, read the clause first. The terms forbid you to "Copy or reproduce any User Content for the purposes of informing, training, developing (or as input to) artificial intelligence or machine intelligence technologies or services".

One key, one service, then ten more

The SoundCloud credential story is now short. The problem is that it is one of eleven. Spotify, Apple Music, YouTube Music, Tidal, Amazon Music, Deezer, SoundCloud, Audiomack, Audius, Boomplay and Qobuz each have their own registration gate, their own token lifetime, their own paging contract and their own 429 semantics. A transfer or onboarding import needs all of them working on the same day.

That is the work MusicAPI removes: the per provider OAuth clients and refresh loops, one normalized playlist and track shape, ISRC first matching where the destination supports it with a fuzzy fallback, and per service rate limit handling behind one interface. On the SoundCloud side specifically, "No SoundCloud developer account, no OAuth client, no token storage on your side: we hold the SoundCloud credentials and use them only to move a listener's own library on their behalf". You send the listener through one hosted redirect and get back an integrationUserUUID; "Public catalogue routes need no listener auth; user routes are addressed by the userUUID returned from the auth callback".

GET https://api.musicapi.com/api/{userUUID}/playlists
Authorization: Basic <clientId:clientSecret>

The same addressing covers reading a listener's SoundCloud playlists and reading the tracks inside one, and POST /api/{userUUID}/playlists writes one back: that endpoint "creates a new playlist in the authenticated user's music library". Swap the service value and the call shape does not change. For the endpoint by endpoint view of working against SoundCloud directly, see our walkthrough of the SoundCloud API for developers.

FAQ

My Client Secret leaked. Can I rotate it without downtime?

SoundCloud documents a rotation path rather than a delete and re-register cycle: "To replace a compromised secret or rotate keys without downtime, see Credential rotation." Treat a leaked secret as an incident anyway, since you are responsible for keeping it private and for how your app uses the API.

Does the same key work in a mobile or desktop app?

Yes, with a different redirect. "Mobile and desktop applications use the same authorization code flow as web applications. Use a custom protocol scheme for the redirect_uri (e.g., my-app://soundcloud/callback)." Adding display=popup to the authorization URL gives the mobile optimized connect screen. The token exchange still belongs on your server, because all clients are treated as confidential.

What happens if SoundCloud revokes my access?

The terms are direct: "we will revoke your access to the SoundCloud API by invalidating your client ID and Security Code. Any attempt to circumvent this and obtain a new client ID and Security Code is strictly prohibited." Registering a second app to route around a revocation is not a recovery plan.

Get a key, then get the other ten

Skip months of OAuth and per provider SDK work. "Sandbox keys are free and instant. Authenticate a real SoundCloud account and make your first live call within the hour." One API moves libraries between 11 streaming services, and SoundCloud is a single string value in the request. Start at the SoundCloud API page.