Track and playlist metadata collection
Mit SoundCloud-Endpunkten verwandelst du track and playlist metadata collection in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn SoundCloud's tracks, playlists, user profiles, and search results into structured JSON — plays, likes, comments, artwork, and uploader details — as normalized data. Credential-free.
Collect SoundCloud track, playlist, user profile, and search data through documented Crawlora API endpoints.
Endpunkt-Familien
5
Dokumentierte Parameter
12
Beispiele
5
Live-Katalog-Snapshot
Aktive Endpunkte
5
Methoden
GET
Pflichtparameter
10
Schema-Referenzen
5
{
"platform": "SoundCloud",
"endpoint": "soundcloud-search",
"method": "GET",
"path": "/soundcloud/search",
"auth": "apiKey"
}Use Cases
Collect SoundCloud track, playlist, user profile, and search data through documented Crawlora API endpoints.
Mit SoundCloud-Endpunkten verwandelst du track and playlist metadata collection in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit SoundCloud-Endpunkten verwandelst du artist and creator profile research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit SoundCloud-Endpunkten verwandelst du music discovery and search monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-SoundCloud-Endpunktkatalog — 5 Endpunkte, 12 dokumentierte Request-Parameter und 5 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
5 documented SoundCloud endpoints, grouped into 5 request families — Playlist, Profile and Search, plus 2 more.
12 request parameters are documented across those SoundCloud endpoints, 10 of them required — the full input contract is public before you write any integration code.
5 of the 5 SoundCloud endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
SoundCloud endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the SoundCloud endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/soundcloud/playlist
/soundcloud/profile
/soundcloud/search
/soundcloud/track
/soundcloud/user-tracks
Endpunktkatalog
/soundcloud/searchSearches SoundCloud tracks for `query`, in SoundCloud's default relevance order. `limit` defaults to 20 and is capped at 50. Each track has its title, artwork, genre, tags, `duration_ms`, play, like, comment and repost counts, and uploader details including follower count and verified status.
Hinweise zur Response
- `tracks` is ordered by SoundCloud's own default relevance sort. - `duration_ms` is the track's length in milliseconds. - A missing `query` returns `400` before any upstream request is made.
MCP-Tool soundcloud_search
/soundcloud/trackReturns one track's full metadata: title, artwork, description, genre, tags, playback/likes/comment/repost counts, and uploader. Public data sourced from SoundCloud's own JSON API.
Hinweise zur Response
- The `url` is resolved server-side against SoundCloud's own resolve endpoint — it must be a track URL. A URL that resolves to a different entity type (e.g. a playlist) returns `400`. - An unresolvable URL returns `404`. A missing `url` returns `400` before any upstream request is made.
MCP-Tool soundcloud_track
/soundcloud/playlistReturns one playlist or album's metadata plus its full track list: owner, likes/reposts counts, and every track's title, artwork, and playback/likes counts. Public data sourced from SoundCloud's own JSON API.
Hinweise zur Response
- `tracks` is the playlist's complete track list as SoundCloud itself returns it, in playlist order — large playlists can return hundreds of tracks in one response. - `is_album` distinguishes a formal album/EP release from a regular user-curated playlist. - The `url` is resolved server-side against SoundCloud's own resolve endpoint — it must be a playlist/album URL. A URL that resolves to a different entity type (e.g. a single track) returns `400`. - An unresolvable URL returns `404`. A missing `url` returns `400` before any upstream request is made.
MCP-Tool soundcloud_playlist
/soundcloud/profileReturns a SoundCloud user or artist profile for a full profile `url` such as `https://soundcloud.com/artist`. Fields are username, full name, bio, avatar, city, country, verified status, and counts of followers, followings, tracks, playlists and likes. A URL for a track or other entity returns 400; an unresolvable URL returns 404.
Hinweise zur Response
- `track_count`/`playlist_count` are the profile owner's own uploads, not likes or reposts. - The `url` is resolved server-side against SoundCloud's own resolve endpoint — it must be a user/artist profile URL. A URL that resolves to a different entity type (e.g. a track) returns `400`. - An unresolvable URL returns `404`. A missing `url` returns `400` before any upstream request is made.
MCP-Tool soundcloud_profile
/soundcloud/user-tracksReturns a user/artist's own uploaded tracks, most recent first: title, artwork, playback/likes/comment/repost counts. Public data sourced from SoundCloud's own JSON API.
Hinweise zur Response
- `tracks` is the user's own uploads only, most-recent-upload-first — distinct from [`/soundcloud/search`](soundcloud-search.md), which matches tracks across all of SoundCloud by relevance to a query. - The `url` is resolved server-side first to get the profile's internal id, then that id's uploads are fetched — two upstream calls per request. It must be a user/artist profile URL; a URL that resolves to a different entity type (e.g. a track) returns `400`. - An unresolvable URL returns `404`. A missing `url` returns `400` before any upstream request is made.
MCP-Tool soundcloud_user_tracks
Verwandte APIs
Audio & Podcast Platforms
Build audio intelligence workflows from Spotify catalog and public profile signals without maintaining Spotify scrapers.
Audio & Podcast Platforms
Turn Spotify podcast discovery, chart, show, and episode pages into structured data for research and agents.
Audio & Podcast Platforms
Extract Apple Podcasts chart rankings, related-show recommendations, curated New shelves, show metadata, episodes, and search results as structured JSON for podcast discovery, chart tracking, and catalog enrichment.
So scrapst du SoundCloud
Crawlora's SoundCloud endpoints return track, playlist, and profile data as structured JSON with one API key — no SoundCloud account, OAuth, or developer registration required. A pull on 2026-10-27 for lofi with limit 5 returned 5 tracks, the first with 293,413 plays and a duration in milliseconds.
Pass a free-text query to /soundcloud/search for matching track metadata, including play counts, likes, and uploader details.
Pass a SoundCloud track URL to /soundcloud/track for full metadata — plays, likes, comments, genre, artwork, and uploader.
Pass a SoundCloud playlist URL to /soundcloud/playlist for the full playlist with every embedded track.
Pass a SoundCloud profile URL to /soundcloud/profile for follower counts, bio, and account details.
Pass a SoundCloud profile URL to /soundcloud/user-tracks for that account's own uploaded tracks, separate from search results.
The first lofi track (Dâu Hào Môn Lofi, id 2408461857) had playback_count 293,413, likes_count 2,352, comment_count 17 and duration_ms 244,108 (about 4 minutes). Durations are milliseconds.
profile, track and playlist routes take a soundcloud.com URL, such as the permalink_url on each search row.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft SoundCloud-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken SoundCloud ab:
Researches music, artists, playlists, and podcasts via the Crawlora API — Spotify tracks/albums/artists/playlists/profiles, Spotify Podcasts, Apple…
npx skills add github.com/Crawlora-org/crawlora-skills --skill music-podcast-researchFAQ
Send a track URL to Crawlora's /soundcloud/track endpoint and get plays, likes, comments, genre, artwork, and uploader data as structured JSON — no SoundCloud account required.
Yes — /soundcloud/playlist returns full playlist metadata along with every embedded track's own metadata.
No SoundCloud login, OAuth, or developer key is required from the caller — only your Crawlora API key.
Yes — /soundcloud/user-tracks returns a user's own uploaded tracks, distinct from /soundcloud/search which returns site-wide search matches.
Collecting publicly accessible track, playlist, and profile data is generally permissible if you respect SoundCloud's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.
Milliseconds. A track with duration_ms 244,108 runs about four minutes.