Impossible to fetch user reposts using public API v1

[ErikAGriffin]

Title: Cannot retrieve reposted tracks / playlists for a user

Issue found of: September 27th, 2016

Based on SoundCloud's structure, many Artists don't actually upload all of their tracks. They may, for example, repost one of their tracks that has been uploaded by their label, or a content curator account. Therefore it is critical that the public API be able to access a user's reposts, otherwise the end-users of our application cannot access all of the tracks an artist has public on their profile.

Presently API v2 returns track and track-reposts when fetching a user's content. This is the only API v2 endpoint we are using for this very reason.

Endpoint(s):

• GET /users/{id}/tracks

Scope(s):

• None, (this request requires only a client id)

Steps to reproduce:

curl --request GET \
  --url 'https://api.soundcloud.com/users/147824/tracks?limit=200&linked_partitioning=t1&client_id=xxclient_id'

Expected behaviour:

A list of all a users tracks and track reposts, or a separate endpoint to fetch reposts of tracks / playlists.

Actual behaviour:

Only uploaded tracks are returned.

[rahul-sc]

Hi. I see multiple inquiries here. Would recommend to file these separately so that we can better triage and answer these.

I recall that this endpoint returned incomplete track collections for some users, whereas the API v2 seemed to always return complete track collections This is fully controlled by rightsholders in their track settings i.e., to allow their content to accessed off-platform via the API or not. api.soundcloud.com is the API to use with the up-to-date functionality.

I think this issue is better tracked as a feature request for an endpoint serving "track reposts", yeah?

[ErikAGriffin]

It appears the other issue created is centered around the incomplete track responses for artists using the public API.

I will center this one around there being no way to fetch reposts using the public API

[ErikAGriffin]

Hi @rahul-sc ,

As a potential workaround, is it possible to leave this one specific route in API v2 until the public API has a published route for user track-reposts?

[rahul-sc]

Hi @rahul-sc ,

As a potential workaround, is it possible to leave this one specific route in API v2 until the public API has a published route for user track-reposts?

Yes

[owensco]

Hey @rahul-sc -- any chance of this making it to the public API?

I am essentially looking for a GET /users/{user_id}/reposts endpoint for exactly the reasons @ErikAGriffin described in the OP.

Thanks!

cc-ing @MariaVWSoundCloud on this request as well!

[MariaVWSoundCloud]

Hi @owensco ,

we don't have an endpoint (and also none in planning) for reposts of a user. However, if it anyhow helps, you can see all reposts of a track: /tracks/{track_id}/reposters

Best regards, Maria

[owensco]

Thanks for the reply @MariaVWSoundCloud. Please consider adding this in the future 🙏