Podcast discovery
Use Spotify Podcasts endpoints to turn podcast discovery into repeatable API requests with documented inputs and JSON responses.
Turn Spotify podcast discovery, chart, show, and episode pages into structured data for research and agents.
Collect Spotify Podcasts home, category, chart, show, episode, recommendation, and search data through structured API endpoints.
Endpoint families
6
Documented params
42
Examples
8
Live catalog snapshot
Active endpoints
8
Methods
GET
Required params
9
Schema refs
8
{
"platform": "Spotify Podcasts",
"endpoint": "spotify-podcasts-categories",
"method": "GET",
"path": "/spotify-podcasts/categories",
"auth": "apiKey"
}Related use cases
Use cases
Collect Spotify Podcasts home, category, chart, show, episode, recommendation, and search data through structured API endpoints.
Use Spotify Podcasts endpoints to turn podcast discovery into repeatable API requests with documented inputs and JSON responses.
Use Spotify Podcasts endpoints to turn show and episode research into repeatable API requests with documented inputs and JSON responses.
Use Spotify Podcasts endpoints to turn podcast chart monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Spotify Podcasts endpoint catalog — 8 endpoints, 42 documented request parameters, and 8 published response schemas — the same catalog Docs and Playground run against.
8 documented Spotify Podcasts endpoints, grouped into 6 request families — Show, Categories and Charts, plus 3 more.
42 request parameters are documented across those Spotify Podcasts endpoints, 9 of them required — the full input contract is public before you write any integration code.
8 of the 8 Spotify Podcasts endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Spotify Podcasts 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.
8 hosted MCP tools back the Spotify Podcasts endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/spotify-podcasts/show
/spotify-podcasts/categories
/spotify-podcasts/charts
/spotify-podcasts/episode
/spotify-podcasts/home
/spotify-podcasts/search
Endpoint catalog
/spotify-podcasts/categoriesReturns normalized Spotify podcast category sections and items from Spotify's all-categories browsePage Pathfinder response.
Response notes
- Upstream token, app config, client token, or Pathfinder failures return `503`. - The response uses the same normalized section and item shape as `/api/v1/spotify-podcasts/home`. Example response: ```json { "code": 200, "msg": "OK", "data": { "uri": "spotify:page:0JQ5DArNBzkmxXHCqFLx2U", "title": "All podcast categories", "sections": [ { "uri": "spotify:section:example", "title": "Categories", "items": [ { "uri": "spotify:page:example", "title": "Arts" } ] } ], "meta": { "operationName": "browsePage", "sectionCount": 1, "fetchedAt": "2026-05-13T15:22:41Z" } } } ```
MCP tool spotify_podcasts_categories
/spotify-podcasts/chartsReturns normalized Spotify podcast chart rankings from podcastcharts.byspotify.com. The chart and region parameters are validated against Spotify's supported podcast chart slugs and countries. Category charts are available only in au, br, de, gb, mx, se, and us.
Response notes
- Invalid `chart` or `region` values return `400`. - `top-podcasts`, `top-episodes`, and `trending` support all listed regions. Category charts support `au`, `br`, `de`, `gb`, `mx`, `se`, and `us`. - `top-episodes` items include episode fields plus the parent show fields when Spotify returns them. - Upstream chart failures return `503`. - `items[].rank` is assigned from the upstream array order. Example response: ```json { "code": 200, "msg": "OK", "data": { "chart": "religion-spirituality", "chartName": "Religion & Spirituality", "chartType": "category", "region": "us", "regionName": "United States", "limit": 100, "items": [ { "rank": 1, "uri": "spotify:show:4Pppt42NPK2XzKwNIoW7BR", "rankMove": "UNCHANGED", "name": "The Bible in a Year (with Fr. Mike Schmitz)", "publisher": "Ascension", "imageUrl": "https://i.scdn.co/image/example", "description": "A podcast description.", "externalUrl": "https://open.spotify.com/show/4Pppt42NPK2XzKwNIoW7BR" } ], "meta": { "sourceUrl": "https://podcastcharts.byspotify.com/api/charts/religion-spirituality?limit=100®ion=us", "count": 1, "fetchedAt": "2026-05-13T15:22:41Z" } } } ```
MCP tool spotify_podcasts_charts
/spotify-podcasts/episodeReturns normalized public episode metadata from Spotify's getEpisodeOrChapter Pathfinder response, with episode page, embed page, and anonymous oEmbed fallbacks when Pathfinder is unavailable. Provide either uri or id; defaults to a known public episode when omitted.
Response notes
- Invalid Spotify episode IDs or URLs return `400`. - Pathfinder, upstream page, embed, and oEmbed failures, or parser drift across all sources, return `503`. - The response includes episode metadata, HTML descriptions, release precision, playability and paywall hints, audio preview URLs, video thumbnails, transcript counts, share links, and parent show metadata when available. Example response: ```json { "code": 200, "msg": "OK", "data": { "uri": "spotify:episode:2C2Y5kNq7qCVOVhbA0G3os", "id": "2C2Y5kNq7qCVOVhbA0G3os", "type": "Episode", "name": "#2496 - Julia Mossbridge", "releaseDate": "2026-05-08T17:00:00Z", "durationMs": 9761982, "isExplicit": true, "isPlayable": true, "playabilityReason": "PLAYABLE", "mediaTypes": ["AUDIO", "VIDEO"], "imageUrl": "https://i.scdn.co/image/example", "videoThumbnailUrl": "https://i.scdn.co/image/video-example", "externalUrl": "https://open.spotify.com/episode/2C2Y5kNq7qCVOVhbA0G3os", "shareUrl": "https://open.spotify.com/episode/2C2Y5kNq7qCVOVhbA0G3os", "previewAudioUrl": "https://audio-preview.spotifycdn.com/example.mp3", "previewAudioUrls": ["https://audio-preview.spotifycdn.com/example.mp3"], "transcriptCount": 1, "show": { "uri": "spotify:show:4rOoJ6Egrf8K2IrywzwOMk", "name": "The Joe Rogan Experience", "externalUrl": "https://open.spotify.com/show/4rOoJ6Egrf8K2IrywzwOMk" }, "meta": { "operationName": "getEpisodeOrChapter", "appVersion": "1.2.90.373.g86862e17", "sourceUrl": "https://api-partner.spotify.com/pathfinder/v2/query", "fetchedAt": "2026-05-13T15:22:41Z" } } } ```
MCP tool spotify_podcasts_episode
/spotify-podcasts/homeReturns normalized sections and items from Spotify's podcast home browsePage Pathfinder response.
Response notes
- Upstream token, app config, client token, or Pathfinder failures return `503`. - The response includes normalized section titles, item metadata, image assets, external Spotify URLs, and fetch metadata. Example response: ```json { "code": 200, "msg": "OK", "data": { "uri": "spotify:genre:podcasts-web", "title": "Podcasts", "sections": [ { "uri": "spotify:section:example", "title": "Featured", "items": [ { "uri": "spotify:show:1QQJ7FElLE0K6CIfZNCxU4", "type": "Podcast", "title": "Example Show", "externalUrl": "https://open.spotify.com/show/1QQJ7FElLE0K6CIfZNCxU4" } ] } ], "meta": { "operationName": "browsePage", "sectionCount": 1, "fetchedAt": "2026-05-13T15:22:41Z" } } } ```
MCP tool spotify_podcasts_home
/spotify-podcasts/searchReturns normalized Spotify podcast shows, episodes, and top results for a search term.
MCP tool spotify_podcasts_search
/spotify-podcasts/showReturns normalized podcast show metadata from Spotify Pathfinder.
MCP tool spotify_podcasts_show
/spotify-podcasts/show/episodesReturns normalized podcast episodes for a Spotify show URI.
MCP tool spotify_podcasts_show_episodes
/spotify-podcasts/show/recommendationsReturns normalized related Spotify shows and episodes from Spotify's show recommendations response.
MCP tool spotify_podcasts_show_recommendations
Related APIs
Audio & Podcast Platforms
Build audio intelligence workflows from Spotify catalog and public profile signals without maintaining Spotify scrapers.
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 Podcasts
Spotify's official Web API covers shows and episodes you already have ids for, but not the podcast charts or the browse surfaces its own apps render. Crawlora's 8 Spotify Podcasts endpoints return search, categories, home and chart rows, show metadata, episodes, and recommendations as normalized JSON.
Search podcasts by free-text q, or read the categories and home endpoints for the sectioned browse surfaces Spotify renders in its apps.
The charts endpoint takes a chart such as top-podcasts, top-episodes, or trending — plus per-genre charts like comedy, news, or true-crime — and a two-letter region from the documented market list.
Show metadata and show-episodes take a Spotify uri; episode detail takes a uri or an id.
Show recommendations returns related shows for a uri, which is how you build a topic graph rather than a flat list.
FAQ
Spotify's Web API exposes shows and episodes you already have ids for, but not the podcast charts, the category browse surfaces, or the home sections. Those come from Spotify's own web client, which is what Crawlora's endpoints read and normalize.
top-podcasts, top-episodes, and trending, plus per-genre charts covering arts, business, comedy, education, fiction, health-fitness, history, leisure, music, news, religion-spirituality, science, society-culture, sports, technology, true-crime, and tv-film. Each takes a two-letter region.
A Spotify uri. Search and chart responses return them, so the normal flow is search or chart first, then pass the uri to the show, episodes, or recommendations endpoint.