SoundCloud Player URL Compatibility Issue with New URN Format

[amrutadotorg]

SoundCloud Player URL Compatibility Issue with New URN Format

Description

There appears to be an incompatibility between the SoundCloud embedded player URL format and the new URN identifiers that SoundCloud is rolling out.

According to SoundCloud's April 29th, 2025 developer announcement, all resource identifiers are transitioning from numeric IDs to string-based URN identifiers (e.g., from 2011642545 to soundcloud:playlists:2011642545).

However, when attempting to use the new URN format in the embedded player URL, the player fails to load.

Steps to Reproduce

1. Using a playlist with ID 2011642545
2. The old URL format works correctly:

   https://w.soundcloud.com/player/?url=http://api.soundcloud.com/playlists/2011642545
   

3. Using the new URN format as advised in the announcement fails:

   https://w.soundcloud.com/player/?url=http://api.soundcloud.com/playlists/soundcloud:playlists:2011642545
   

Expected Behavior

The embedded player should work with the new URN format, as SoundCloud has stated that "All the endpoints are ready to take either id or urn" in their announcement.

Actual Behavior

The embedded player fails to load when using the URN format in the URL.

Additional Context

SoundCloud's announcement explicitly states:

• "Before: https://api.soundcloud.com/tracks/12345678"
• "After: https://api.soundcloud.com/tracks/soundcloud:tracks:12345678"

They also mention: "We recommend to move always URN going forward. Accessing via id is deprecated immediately!"

However, it appears that the embedded player widget has not been updated to support this new URN format.

Environment

• Browser: Version 135.0.7049.115 (Official Build) (arm64)
• SoundCloud API version: Latest as of April 29, 2025
• Reference: SoundCloud Backstage Blog announcement "Action required: Upcoming Update to SoundCloud API id fields" (April 29, 2025)

Proposed Solution

The SoundCloud embedded player should be updated to properly handle the new URN format in its URL parameter, maintaining consistency with the rest of the API.

[dpreussler]

@amrutadotorg thanks for flagging this. 🙏
As temporary workaround please take the numeric part of the urn (split by : and use the third part)

[omaximchuk]

@dpreussler will your workaround work after you introduce full support for urn in the embedded player? It seems that this will be broken again.

[dpreussler]

@omaximchuk we're airming to have support for both id and urn for a while in the endpoints. Just id will be deprecated

[omaximchuk]

Sure, @dpreussler , I understand this. Will I be able to generate the widget code using the numerical part of the urn? How would the widget code would look like when the id field is completely removed?