Automate SoundCloud Public Specification

What HumDay can do in SoundCloud Public Specification

18 documented operations change something in SoundCloud Public Specification.

• POSTUploads a new track./tracks
• POSTCreates a playlist./playlists
• POSTReturns the newly created comment on success/tracks/{track_id}/comments
• DELETEDeletes a user who is followed by the authenticated user./me/followings/{user_id}
• PUTFollows a user./me/followings/{user_id}
• DELETERemoves a repost on a track as the authenticated user/reposts/tracks/{track_id}
• POSTReposts a track as the authenticated user/reposts/tracks/{track_id}
• DELETERemoves a repost on a playlist as the authenticated user/reposts/playlists/{playlist_id}
• POSTReposts a playlist as the authenticated user/reposts/playlists/{playlist_id}
• DELETEDeletes a track./tracks/{track_id}
• PUTUpdates a track's information./tracks/{track_id}
• DELETEDeletes a playlist./playlists/{playlist_id}
• PUTUpdates a playlist./playlists/{playlist_id}
• DELETEUnlikes a track./likes/tracks/{track_id}
• POSTLikes a track./likes/tracks/{track_id}
• DELETEUnlikes a playlist./likes/playlists/{playlist_id}
• POSTLikes a playlist./likes/playlists/{playlist_id}
• POSTThis endpoint accepts POST requests and is used to provision access tokens once a user has authorized your application./oauth2/token

What HumDay can read from SoundCloud Public Specification

These are the operations a schedule or a trigger can watch.

• GETPerforms a user search based on a query/users
• GETReturns a list of user's comments./users/{user_id}/comments
• GETReturns a list of users who are following the authenticated user./me/followers
• GETReturns a list of users who are followed by the authenticated user./me/followings
• GETReturns a list of recent tracks from users followed by the authenticated user./me/followings/tracks
• GETPerforms a track search based on a query/tracks
• GETPerforms a playlist search based on a query/playlists
• GETReturns a list of user's tracks./users/{user_id}/tracks
• GETReturns a list of user’s followers./users/{user_id}/followers
• GETReturns a list of user's playlists./users/{user_id}/playlists
• GETReturns a list of user’s followings./users/{user_id}/followings
• GETReturns list of user's links added to their profile (website, facebook, instagram)./users/{user_id}/web-profiles
• GETReturns a list of user's tracks./me/tracks
• GETReturns a list of the authenticated user's connected social accounts./me/connections
• GETReturns a list of user's liked tracks./users/{user_id}/likes/tracks
• GETReturns a user./users/{user_id}
• GETReturns a list of favorited or liked tracks of the authenticated user./me/likes/tracks
• GETReturns the authenticated user’s information./me
• GETReturns a list of users who have favorited or liked the track./tracks/{track_id}/favoriters
• GETReturns user’s playlists (sets)./me/playlists
• GETReturns the authenticated user's activities./me/activities
• GETReturns the authenticated user's recent track related activities./me/activities/tracks
• GETResolves soundcloud.com URLs to Resource URLs to use with the API./resolve
• GETRecent the authenticated user's activities./me/activities/all/own
• GETReturns the comments posted on the track(trackid)./tracks/{track_id}/comments
• GETReturns the authenticated user's connected social account./me/connections/{connection_id}
• GETReturns a track./tracks/{track_id}
• GETReturns a playlist./playlists/{playlist_id}
• GETReturns all related tracks of track on SoundCloud./tracks/{track_id}/related
• GETReturns a track's streamable URLs/tracks/{track_id}/streams
• GETReturns a collection of track's reposters./tracks/{track_id}/reposters
• GETReturns tracks under a playlist./playlists/{playlist_id}/tracks
• GETReturns a collection of playlist's reposters./playlists/{playlist_id}/reposters
• GETThe OAuth2 authorization endpoint./connect

How automating SoundCloud Public Specification works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live SoundCloud Public Specification account.
4. Grant access, then go live. You approve the specific SoundCloud Public Specification operations it may use — and only those.

Popular SoundCloud Public Specification integrations

Connect SoundCloud Public Specification to the tools people pair it with most.

• SoundCloud Public Specification and OData for namespace microsoft.graphintegration
• SoundCloud Public Specification and Cloudflareintegration
• SoundCloud Public Specification and NetBoxintegration
• SoundCloud Public Specification and GitHubintegration
• SoundCloud Public Specification and Mistintegration
• SoundCloud Public Specification and Loket.nlintegration
• SoundCloud Public Specification and Atlassian The Jira Cloud platformintegration
• SoundCloud Public Specification and Magento B2Bintegration
• SoundCloud Public Specification and Stripeintegration
• SoundCloud Public Specification and Zuora Reference Billingintegration
• SoundCloud Public Specification and bunqintegration
• SoundCloud Public Specification and DocuSignintegration

Automate SoundCloud Public Specification with these

• Google Compute Engine694 operations
• Jellyfin379 operations
• OpenAI273 operations
• Evetech EVE Swagger Interface206 operations
• Google Campaign Manager 360205 operations
• Google Content for Shopping175 operations
• Google Display & Video 360151 operations
• Bungie.Net134 operations
• VocaDbWeb127 operations
• Google Admin SDK122 operations
• Google Apigee109 operations
• Shutterstock Explorer109 operations

Categories

• Media

Questions about SoundCloud Public Specification automation

Can HumDay connect to SoundCloud Public Specification?

Yes. HumDay reads SoundCloud Public Specification's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 52 operations are documented.

Do I need to write code to automate SoundCloud Public Specification?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your SoundCloud Public Specification account.

What can HumDay do in SoundCloud Public Specification?

18 of the 52 documented operations change something in SoundCloud Public Specification, and 34 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my SoundCloud Public Specification account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to SoundCloud Public Specification is held behind that approval.

Where this came from

The operations above are read from a published API description for SoundCloud Public Specification at gist.githubusercontent.com/MikeRalphson/a9eb3040cb611121b568844958564849/raw/d0996b827b9eb. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.