Track and playlist metadata collection
SoundCloudエンドポイントを使えば、「Track and playlist metadata collection」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
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.
エンドポイントファミリー
5
ドキュメント化されたパラメータ
12
サンプル数
5
ライブカタログスナップショット
稼働エンドポイント
5
メソッド
GET
必須パラメータ
10
スキーマ参照
5
{
"platform": "SoundCloud",
"endpoint": "soundcloud-search",
"method": "GET",
"path": "/soundcloud/search",
"auth": "apiKey"
}ユースケース
Collect SoundCloud track, playlist, user profile, and search data through documented Crawlora API endpoints.
SoundCloudエンドポイントを使えば、「Track and playlist metadata collection」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
SoundCloudエンドポイントを使えば、「Artist and creator profile research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
SoundCloudエンドポイントを使えば、「Music discovery and search monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のSoundCloudエンドポイントカタログから取得しています（エンドポイント5件、ドキュメント化されたリクエストパラメータ12個、公開レスポンススキーマ5件）。DocsとPlaygroundが参照しているカタログと同じものです。
SoundCloudのエンドポイントは5件、5つのリクエストファミリーに分類されています（Playlist、Profile、Searchほか2件）。
これらのSoundCloudエンドポイントには12個のリクエストパラメータがドキュメント化されており、うち10個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
5件のSoundCloudエンドポイントのうち5件が実際のサンプルレスポンスを、5件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
SoundCloudのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
SoundCloudのエンドポイントは5個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/soundcloud/playlist
/soundcloud/profile
/soundcloud/search
/soundcloud/track
/soundcloud/user-tracks
エンドポイントカタログ
/soundcloud/searchReturns tracks matching a query: title, artwork, playback/likes/comment/repost counts, and uploader. Public data sourced from SoundCloud's own JSON API.
レスポンスに関する注記
- `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. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "lofi hip hop", "count": 20, "tracks": [ { "id": 417474360, "title": "Chill Study Beats - Lofi Hip Hop Mix [2018]", "permalink_url": "https://soundcloud.com/nigeldelviero/chill-study-beats-lofi-hip-hop-mix-2018", "artwork_url": "https://i1.sndcdn.com/artworks-000321524016-jw118f-large.jpg", "genre": "Hip-hop & Rap", "tag_list": "Lo-Fi Relax Chill", "duration_ms": 7200255, "playback_count": 4810593, "likes_count": 93943, "comment_count": 4835, "reposts_count": 2218, "created_at": "2018-03-22T08:35:48Z", "public": true, "streamable": true, "uploader": { "id": 154582242, "username": "nigeldelviero", "permalink": "nigeldelviero", "permalink_url": "https://soundcloud.com/nigeldelviero", "city": "Jakarta", "followers_count": 4113, "track_count": 2 } } ] } } ```
MCPツール 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.
レスポンスに関する注記
- 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. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": 417474360, "title": "Chill Study Beats - Lofi Hip Hop Mix [2018]", "permalink_url": "https://soundcloud.com/nigeldelviero/chill-study-beats-lofi-hip-hop-mix-2018", "artwork_url": "https://i1.sndcdn.com/artworks-000321524016-jw118f-large.jpg", "description": "Enjoy 🔊\nFull tracklist...", "genre": "Hip-hop & Rap", "tag_list": "Lo-Fi Relax Chill", "duration_ms": 7200255, "playback_count": 4810593, "likes_count": 93943, "comment_count": 4835, "reposts_count": 2218, "created_at": "2018-03-22T08:35:48Z", "public": true, "streamable": true, "uploader": { "id": 154582242, "username": "nigeldelviero", "permalink": "nigeldelviero", "permalink_url": "https://soundcloud.com/nigeldelviero", "city": "Jakarta", "followers_count": 4113, "track_count": 2 } } } ```
MCPツール 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.
レスポンスに関する注記
- `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. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": 123456789, "title": "Lofi Chill", "permalink_url": "https://soundcloud.com/lofi_chill/sets/lofi-chill", "track_count": 416, "likes_count": 1024, "public": true, "owner": { "id": 987654321, "username": "lofi_chill", "permalink_url": "https://soundcloud.com/lofi_chill", "followers_count": 50000 }, "tracks": [ { "id": 1004445667, "title": "My Love", "permalink_url": "https://soundcloud.com/david_sanya/my-love", "playback_count": 12000, "uploader": { "id": 171315858, "username": "David Sanya", "permalink_url": "https://soundcloud.com/david_sanya" } } ] } } ```
MCPツール soundcloud_playlist
/soundcloud/profileReturns one user/artist's profile: bio, avatar, followers/followings/track/playlist/likes counts, and verified status. Public data sourced from SoundCloud's own JSON API.
レスポンスに関する注記
- `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. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": 144868900, "username": "Lofi Girl", "permalink": "lofi_girl", "permalink_url": "https://soundcloud.com/lofi_girl", "avatar_url": "https://i1.sndcdn.com/avatars-8D5zoj5ySzRF0jHc-oPZwDg-large.jpg", "description": "study, chill, sleep, repeat.", "followers_count": 255531, "followings_count": 634, "track_count": 712, "playlist_count": 27, "likes_count": 1032, "verified": true } } ```
MCPツール 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.
レスポンスに関する注記
- `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. Example response: ```json { "code": 200, "msg": "OK", "data": { "profile_url": "https://soundcloud.com/lofi_girl", "count": 20, "tracks": [ { "id": 2380857462, "title": "sunken relics", "permalink_url": "https://soundcloud.com/lofi_girl/sunken-relics", "genre": "Lo-Fi", "playback_count": 282, "likes_count": 12, "created_at": "2026-08-13T10:53:01Z", "public": true, "streamable": true, "uploader": { "id": 144868900, "username": "Lofi Girl", "permalink_url": "https://soundcloud.com/lofi_girl", "verified": true } } ] } } ```
MCPツール soundcloud_user_tracks
関連API
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.
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.
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.
FAQ
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.