You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just implemented the OAuth2 access token flow and now I'm getting the following error response on every API endpoint that tries to perform an action on behalf of the user, such as liking a track, creating a playlist, etc:
{
"error": "Access to this resource has been disallowed"
}
I've confirmed that the OAuth2 access token I received through the flow works on API endpoints that are just receiving information, such as getting information about a route, so I'm pretty sure I've implemented the OAuth2 flow correctly. However, I can't seem to find any documentation on this error, so I'm wondering if I'm doing something wrong after all or how to fix it.
The text was updated successfully, but these errors were encountered:
Hi @NurMarvin
It sounds like you are using the "Client Credentials" flow. You can not use those credentials to take actions on behalf of users.
You need to go through the "Authorization Code" flow which a proper user login.
I'm aware of the difference between the two flows and I did specify an authorization_code grant type when sending a request to https://secure.soundcloud.com/oauth/token.
Here's the entire code I've used for receiving the Access Token:
I just implemented the OAuth2 access token flow and now I'm getting the following error response on every API endpoint that tries to perform an action on behalf of the user, such as liking a track, creating a playlist, etc:
I've confirmed that the OAuth2 access token I received through the flow works on API endpoints that are just receiving information, such as getting information about a route, so I'm pretty sure I've implemented the OAuth2 flow correctly. However, I can't seem to find any documentation on this error, so I'm wondering if I'm doing something wrong after all or how to fix it.
The text was updated successfully, but these errors were encountered: