Retrieve track metadata from SoundCloud via the API
domain: developers.soundcloud.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an application on the SoundCloud developer portal to obtain a client_id, or use an OAuth user token if accessing private tracks.
To resolve a track by its public URL, send a GET request to the resolve endpoint with the track's public URL as the url query parameter and your client_id.
The resolve endpoint returns a redirect to the canonical resource URL; follow the redirect or use the returned id to call the tracks endpoint directly (/tracks/{id}).
Send a GET request to /tracks/{id} with your client_id to retrieve full track metadata including title, description, duration, genre, tag_list, and stream URL.
Parse the response fields you need; the permalink_url gives the public SoundCloud page and waveform_url provides the waveform image asset.
Known gotchas
SoundCloud's public API access has been restricted in recent years; new application registrations may be subject to approval delays or access limitations — verify current developer portal status before building.
Stream URLs returned by the API may require OAuth user authentication or a valid client_id token to be usable, depending on the track's license and the user's plan.
Private or permission-restricted tracks are not accessible via client_id alone; a user OAuth token with the appropriate scope is required.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?