[API Regression] Stream URL Endpoint Returning 403 / Pro Subscription Error While Metadata and Search Endpoints Function Normally
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing requests to the stream_url endpoint and compare their responses with track search, artist profile, and metadata requests. Determine whether the 403 and Artist Pro Subscription error is an unintended regression or an intentional tier change; done means either restored stream URL access or clear migration and developer notification details.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100