All you need to work with their API is your client_id. You have to go to SoundCloud, sign in, open a track/playlist, hit F12, and go to the Networking tab, then start the song and use the search box to look out for requests containing a client_id. There you can also find other parameters like track_id, playlist_id, etc.
Then go to developers.soundcloud.com/docs/api... to see all the available API routes and use that client_id for authorization at the end of each query you want to fetch.
For example, to return a track, you would use https://api-v2.soundcloud.com/tracks/{track_id}?client_id={client_id}.
Or, to return a playlist: https://api-v2.soundcloud.com/playlists/{playlist_id}?client_id={client_id}.
I'm a dev with a strong *NIX sysadmin background. I've been programming for 20+ years, started with IRC scripts, C, Python, PHP, Ruby/Rails, Node/JS, Go and Elxir. Full time on Ruby,Elixir and Rust.
All you need to work with their API is your client_id. You have to go to SoundCloud, sign in, open a track/playlist, hit F12, and go to the Networking tab, then start the song and use the search box to look out for requests containing a client_id. There you can also find other parameters like track_id, playlist_id, etc.
Then go to developers.soundcloud.com/docs/api... to see all the available API routes and use that client_id for authorization at the end of each query you want to fetch.
For example, to return a track, you would use
https://api-v2.soundcloud.com/tracks/{track_id}?client_id={client_id}.Or, to return a playlist:
https://api-v2.soundcloud.com/playlists/{playlist_id}?client_id={client_id}.Thank you! I’ve been stuck on the API for some day, until I’ve re-read your comment mentioning the API v2.
Still working progress, and I took a slightly different path, but it’s online and I’m enjoying it ;-)
radio.pavonz.com
thank you again for your help and hints!
My pleasure to help 👍😉