Music catalog enrichment
Use Spotify endpoints to turn music catalog enrichment into repeatable API requests with documented inputs and JSON responses.
Build audio intelligence workflows from Spotify catalog and public profile signals without maintaining Spotify scrapers.
Collect Spotify catalog, artist, album, playlist, track, profile, chart, genre, audiobook, and search data through documented Crawlora endpoints.
Endpoint families
6
Documented params
172
Examples
30
Live catalog snapshot
Active endpoints
30
Methods
GET
Required params
39
Schema refs
30
{
"platform": "Spotify",
"endpoint": "spotify-album",
"method": "GET",
"path": "/spotify/album",
"auth": "apiKey"
}Related use cases
Use cases
Collect Spotify catalog, artist, album, playlist, track, profile, chart, genre, audiobook, and search data through documented Crawlora endpoints.
Use Spotify endpoints to turn music catalog enrichment into repeatable API requests with documented inputs and JSON responses.
Use Spotify endpoints to turn artist and playlist research into repeatable API requests with documented inputs and JSON responses.
Use Spotify endpoints to turn audio trend monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Spotify endpoint catalog — 30 endpoints, 172 documented request parameters, and 30 published response schemas — the same catalog Docs and Playground run against.
30 documented Spotify endpoints, grouped into 21 request families — Artist, Profile and Track, plus 18 more.
172 request parameters are documented across those Spotify endpoints, 39 of them required — the full input contract is public before you write any integration code.
30 of the 30 Spotify endpoints ship a recorded example response, and 30 carry a documented response schema — you can code against the real JSON before the first request.
Spotify endpoints document their error responses (400, 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.
30 hosted MCP tools back the Spotify endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/spotify/artist
/spotify/profile
/spotify/track
/spotify/album
/spotify/audiobook
/spotify/albums/search
Featured endpoints
/spotify/albumReturns a Spotify album from `uri` (a Spotify URI or open.spotify.com URL) or `id`: name, album type, artists, release date, copyrights, cover images, total tracks and duration. The `tracks` page is set by `offset` (default 0) and `limit` (1 to 50, default 50). A missing or invalid identifier returns 400.
Response notes
The response includes album fields, artists, images, and track summaries. Missing or invalid album identifiers return `400`; upstream failures return `503`.
MCP tool spotify_album
/spotify/album/tracksLists the tracks of a Spotify album, identified by `uri` (a Spotify URI or open.spotify.com URL) or `id`. `offset` defaults to 0 and `limit` runs 1 to 50, default 50. Each track has its title, URI, subtitle, image and URL. The album's name, artists and track total come back alongside. An invalid identifier returns 400.
Response notes
The response shape matches `/spotify/album`, with the `tracks` array populated. Invalid identifiers return `400`; upstream failures return `503`.
MCP tool spotify_album_tracks
/spotify/albums/searchReturns Spotify album search results for a search term. Caller-supplied Spotify bearer or client tokens are not required.
Response notes
- Upstream failures return `503`. - Album results are available in `data.albums`; a de-duplicated cross-entity view is also returned in `data.results`. - `meta.operationName` is `searchAlbums`.
MCP tool spotify_albums_search
/spotify/artistReturns a Spotify artist's profile by artist URI, `open.spotify.com` URL or id: name, verified flag, follower count, monthly listeners (`monthlyUsers`), biography and images, plus top tracks, selected discography, related artists and artist playlists when Spotify returns them.
Response notes
The response includes artist profile data, image assets, top tracks, selected discography, related artists, and artist playlists when Spotify returns them. Invalid identifiers return `400`; upstream failures return `503`.
MCP tool spotify_artist
/spotify/artist/albumsReturns an artist's Spotify discography by artist URI, `open.spotify.com` URL or id. Choose `type` (`album`, `single`, `compilation`, `appears_on` or `all`; default `album`) and `order` (default `date_desc`), and page with `offset` and `limit` (1-50, default 50). Each item has a type, title, subtitle, Spotify URI, external URL and images; `total` gives the full count.
Response notes
The endpoint selects the matching private discography operation for the requested `type`. Unsupported `type` or `order` values return `400`; upstream private API failures return `503`.
MCP tool spotify_artist_albums
/spotify/artist/playlistsReturns the Spotify playlists associated with an artist, by artist URI, `open.spotify.com` URL or id. Each playlist has a title, subtitle, description, Spotify URI, external URL and images. Some artists have no playlists, in which case `items` is empty.
Response notes
Some artists may legitimately return an empty `items` array. Invalid identifiers return `400`; upstream private API failures return `503`.
MCP tool spotify_artist_playlists
Related APIs
Audio & Podcast Platforms
Turn Spotify podcast discovery, chart, show, and episode pages into structured data for research and agents.
Audio & Podcast Platforms
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.
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.
How to scrape Spotify
Spotify's official Web API requires OAuth app registration and gates some catalog, chart, and profile data. Crawlora's Spotify endpoints return catalog, artist, album, track, playlist, profile, chart, and search data as structured JSON with just your Crawlora key.
Search tracks, artists, albums, or playlists, or target a specific track, artist, album, playlist, or public profile by ID.
Pass a query or Spotify ID to Crawlora's Spotify endpoint (e.g. /spotify/search, /spotify/track, /spotify/artist).
Receive track, artist, album, and playlist metadata, country charts and popularity, related artists, and public profile data as clean JSON.
Feed music-catalog and audio-intelligence workflows, or re-run to track chart movement, new releases, and playlist changes over time.
客户端库
为你的语言安装 Spotify 专用客户端。每个包都覆盖本页的 Spotify 端点，并使用你的 API 密钥调用 Crawlora 托管 API。
npm install @crawlora-org/spotifynpmgo get github.com/Crawlora-org/crawlora-spotifypkg.go.devgem install crawlora-spotifyRubyGemsnet.crawlora:crawlora-spotifyMaven Centralcomposer require crawlora/spotifyPackagistcargo add crawlora-spotifycrates.ioFAQ
Send a search query or Spotify ID to Crawlora's Spotify endpoints and get catalog, artist, album, track, playlist, chart, and public profile data as structured JSON — no OAuth app to register. Collect public data and respect Spotify's terms.
Spotify's Web API requires OAuth app registration, gates some catalog and chart data, and rate-limits per app. Crawlora returns catalog, artist, album, track, playlist, country charts, popularity, and public profile data in one normalized JSON shape with just your Crawlora key, plus hosted MCP tools for AI agents.
Collecting publicly accessible catalog, chart, and profile data is generally permissible if you respect Spotify's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.
Not for most developers. Spotify deprecated its Recommendations, Related Artists, Audio Features, and Audio Analysis endpoints for any app not already in extended quota mode as of November 2024, and it doesn't onboard new extended-mode apps below a 250,000 monthly-active-user threshold. Crawlora's Spotify endpoints return related-artist and track-recommendation data directly, with no MAU gate.