Access_token generated from the new API URL - https://secure.soundcloud.com/oauth/token doesn't work

[kejul-vyas-mck]

Title: Cannot upload audio track using API

Issue found of: Nov 11th, 2024

Endpoint(s):

• POST https://api.soundcloud.com/tracks

Scope(s):

• None (application is not using authentication i.e., implicit flow)

Steps to reproduce:

1. I am generating access_token using the client credential workflow - https://secure.soundcloud.com/oauth/token
2. Access_token is generated successfully.
3. upload the track using below curl url and Authorization header.
   curl -X 'POST'
   'https://api.soundcloud.com/tracks'
   -H 'accept: application/json; charset=utf-8'
   -H 'Content-Type: multipart/form-data'
   -F 'track[sharing]=private'
   -F 'track[asset_data]=@A-hard-row-to-hoe—whats-in-store-for-agricultural-input-suppliers-this-year.mp3;type=audio/mpeg'
   -F 'track[title]=test'
   

Expected behaviour:

Track should be uploaded to this app - https://soundcloud.com/mckinsey

Actual behaviour:

Getting 401 Unauthorized error.

[mgoodfellow]

Hi @kejul-vyas-mck

As before: #339 (comment)

You cannot use the client credential flow to mutate data (such as POST/PUT etc) to a user context, or to view the /me endpoints. The client credential flow is an application authorization flow, it is not associated to a user.

You need to authorize a user to your app via the Authorization Code flow.

[kejul-vyas-mck]

is this true? @youssefhassan if so then why I don't see anywhere here to mention that we can not use client credential workflow for POST api - https://developers.soundcloud.com/docs/api/guide#authentication

[mgoodfellow]

[kejul-vyas-mck]

Currently with old upload track api - https://api.soundcloud.com/oauth2/token, the client credential workflow is working fine though