[API Regression] Stream URL Endpoint Returning 403 / Pro Subscription Error While Metadata and Search Endpoints Function Normally

[MadBossRaven]

In old account, API requests to track stream URLs (stream_url) have suddenly begun failing with an error stating that an "Artist Pro Subscription" (SoundCloud Next Pro) is required.

However, all other API endpoints—including track search, artist profiles, and general metadata retrieval—continue to function as expected. Because read access to track metadata remains operational, this localized failure on the streaming endpoint appears to be an unintended regression or access-control bug rather than a full API service deprecation.
If this is an intentional breaking change, it was deployed without prior notice, developer email communications, causing immediate service disruption across multiple active applications.

If this policy change is intentional, please notify registered developers via email or official developer announcements, providing clear migration details.

Implementation Timeline: Provide a grace period and reasonable transition window before enforcing tier changes so developers have adequate time to adjust their integration without experiencing sudden downtime.

[dpreussler]

Hi there,

We started paypwalling our API this year. For now only newer accounts, created by the self services options are affected. This allows us to keep the API open to everyone but in a safe way, not to harm the platform. The registration process is already behind paywall since early this year, this just makes sure these are kept active.

A proper communication with timeline for older accounts will follow.

If you feel like this is happening on an older account, please send the client id or the account that it's belonging to either here or via DM to https://x.com/SoundCloudDev or https://bsky.app/profile/soundcloud.dev or our chatbot in the help center and post the ticket number here! We can have a look as we don't want to interrupt

[MadBossRaven]

Thank you for the update and clarification.
Since the app was created prior to the new self-service paywall rules, it appears my client_id was affected by mistake. I have submitted my client_ids details DM on Bluesky.

[dpreussler]

@MadBossRaven
For now I've taken you out of the enforcement but please keep an eye out for comms. This will still hit your app at some point

I'm keeping this open for now for other's who might run into this

[MadBossRaven]

Thank you for resolving this. I appreciate the clarity regarding the ongoing API updates.

I will keep an eye out for official communications and guidelines regarding the upcoming timeline for legacy accounts so we can prepare our integration accordingly.