Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easiest way for non-coder to upload tracks to own account using API? #288

Open
cloudgreen opened this issue Mar 19, 2024 · 2 comments
Open

Comments

@cloudgreen
Copy link

cloudgreen commented Mar 19, 2024

Hi all!

I'm interested in automating track uploading to my own SoundCloud account, as I frequently upload the same or updated tracks (demos and versions) to record labels and collaborators.

My aim is to use Curl on Windows and I have regged an "app" via helpdesk so I have the Client ID and Client Secret.

I realized I have to use the Authorization Code Flow to access my user data. But I think I got in over my head with this... :( I don't understand how to accomplish the required PKCE, Redirect URI and Code Challenge parts in the Authorization Code Flow.

It all seems very geared towards public app building, user authentication and integration, and not for local automation tasks for a single user.

Do you experienced coders think it's feasible for a non-coder to pull this off? Or does anyone know of any pre-fabricated script that might help with this (others have asked before me)? (There was apparently an old Python script that's now deprecated.)

@fabianbernhart
Copy link

Did you register a app here?

I checked creating a new App is not available currently.
grafik

If you have an ACCESS TOKEN

  1. Go to:
  1. Add your API Token there.
    grafik

  2. Go to

  1. Execute
    Excute the API Endpoint

  2. Next Upload Tracks:

@cloudgreen
Copy link
Author

Thanks for helping, @fabianbernhart!

Yes, I recently got API access via SoundCloud support. SoundCloud wrote recently in the API Access thread, that one can file a support ticket to get API access.

I think I run into problems right at the start, getting the correct type of access token:

Using Curl, I have only managed to get a token with "grant_type=client_credentials". But if I understand correctly, I need to get a token of type "grant_type=authorization_code" to manage my private tracks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants