Inconsistent HTTP status codes

[Xartrick]

Inconsistent HTTP status codes

Issue found of: September 7th, 2021

Endpoint(s):

• GET /users/{id}/playlists
• GET /users/{id}/followers
• GET /playlists/{id}/tracks

Scope(s):

• User OAuth token

Steps to reproduce:

Get a not found user

$ curl -i --request GET \
--url https://api.soundcloud.com/users/3 \
-H "Authorization: OAuth USER_TOKEN"

HTTP/1.1 404 Not Found
Content-Type: application/json; charset=utf-8
[...]

{"code":404,"message":"404 - Not Found","link":"https://developers.soundcloud.com/docs/api/explorer/open-api","status":"404 - Not Found","errors":[{"error_message":"404 - Not Found"}],"error":null}

Get a not found user followers

$ curl -i --request GET \
--url https://api.soundcloud.com/users/3/followers \
-H "Authorization: OAuth USER_TOKEN"

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
[...]

{"collection":[],"next_href":null}

Expected behaviour:

404 Not Found

Actual behaviour:

200 OK

[dasha-kobzeva]

Hello @Xartrick,

thank you for filing the issue. We are aware of inconsistencies and it's in our roadmap.

We are limited in capacities, so it cannot be prioritized at the moment.
I hope you understand, we are trying to improve the API as fast as we can.