Spotify Web API

Name: Spotify Web API API
Brand: Spotify Web API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio Processingoauth289 EndpointsREST

For Agents

Search Spotify's catalog of tracks, albums, artists, and podcasts, control playback across devices, and manage user playlists and libraries. Covers 89 endpoints with OAuth 2.0 user-scoped access.

Quickstart

Get started with Spotify Web API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search for music tracks and create a playlist"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Spotify Web API API.

Search the Spotify catalog across tracks, albums, artists, shows, episodes, and audiobooks with filtered queries

Control playback on any Spotify Connect device including play, pause, skip, seek, volume, and queue management

Build and modify playlists with track ordering, collaborative editing, and custom cover images

Retrieve audio features (danceability, energy, tempo, valence) and audio analysis for algorithmic music discovery

GET STARTED

Start building with Spotify Web API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Spotify Web API, keeping it validated and agent-ready.

Discover music, podcasts, and audiobooks, control playback across devices, and manage personal libraries through 89 endpoints spanning the Spotify platform. The API provides access to Spotify's catalog of 100+ million tracks with search, recommendations, audio features analysis, and playlist management. OAuth 2.0 authorization code flow enables user-scoped actions including playback control via Spotify Connect, library curation, and listening history retrieval.

Use Cases

Patterns agents use Spotify Web API API for, with concrete tasks.

★ AI Agent Music Discovery and Playlist Curation

AI agents build personalized playlists by combining Spotify's recommendation engine with audio feature analysis through Jentic. The agent searches for tracks matching target mood attributes (valence, energy, danceability), retrieves recommendations seeded from user favorites, and assembles a playlist — all without the user manually browsing the Spotify catalog. Jentic handles OAuth token management so the agent can access user-scoped endpoints.

Get the user's top 5 tracks via GET /me/top/tracks, use them as seeds in GET /recommendations with target_energy=0.8, then create a playlist via POST /users/{user_id}/playlists and add the recommended tracks via POST /playlists/{playlist_id}/tracks

Cross-Device Playback Control

Control Spotify playback across all connected devices through the Spotify Connect protocol. The Player endpoints enable starting, pausing, skipping, seeking, and adjusting volume on any active device — phones, speakers, desktops, or smart displays. The API exposes the full device list with current volume and active status, enabling automated playback routing and multi-room audio orchestration without the Spotify app UI.

List available devices via GET /me/player/devices, transfer playback to a specific device via PUT /me/player with device_ids, then start playing a specific album via PUT /me/player/play with context_uri

Audio Feature Analysis for Music Apps

Analyze the musical characteristics of any track in Spotify's catalog using audio features (tempo, key, time signature, danceability, energy, valence, speechiness, acousticness, instrumentalness, liveness) and detailed audio analysis (beats, bars, sections, segments). These features power mood-based filtering, BPM matching for DJ tools, workout playlists by energy level, and music education applications.

Retrieve audio features for 5 tracks via GET /audio-features?ids={id1},{id2},..., filter by danceability > 0.7 and energy > 0.6, and return the matching tracks

Podcast and Audiobook Discovery

Search and browse Spotify's podcast and audiobook catalog with the same API used for music. The search endpoint supports type filtering for shows, episodes, and audiobooks. Users can save shows to their library, track listening progress with playback position, and discover new content through Spotify's recommendation algorithms applied to spoken-word content.

Search for podcasts about AI using GET /search?q=artificial+intelligence&type=show, then retrieve episodes for the top result via GET /shows/{id}/episodes and check if any are in the user's library via GET /me/episodes/contains

Key Endpoints

89 endpoints — discover music, podcasts, and audiobooks, control playback across devices, and manage personal libraries through 89 endpoints spanning the spotify platform.

METHOD

PATH

DESCRIPTION

GET

/search

Search the catalog for tracks, albums, artists, shows, or audiobooks

GET

/recommendations

Get track recommendations based on seeds and tunable attributes

GET

/me/player

Get current playback state and active device

PUT

/me/player/play

Start or resume playback on a device

POST

/playlists/{playlist_id}/tracks

Add tracks to a playlist

GET

/audio-features/{id}

Get audio features for a track

GET

/me/top/tracks

Get user's top tracks by listening frequency

GET

/artists/{id}/top-tracks

Get an artist's top tracks by country

GET

/search

Search the catalog for tracks, albums, artists, shows, or audiobooks

GET

/recommendations

Get track recommendations based on seeds and tunable attributes

GET

/me/player

Get current playback state and active device

PUT

/me/player/play

Start or resume playback on a device

POST

/playlists/{playlist_id}/tracks

Add tracks to a playlist

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Spotify OAuth 2.0 client credentials and user tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens for specific OAuth scopes — the client secret and refresh token never enter the agent's execution context.

Intent-based discovery

Agents search by intent (e.g., 'create a playlist with recommended tracks') and Jentic returns matching Spotify operations with their required OAuth scopes and request schemas, so the agent can navigate Spotify's 89-endpoint surface without reading documentation.

Time to first call

Direct Spotify integration: 2-4 days for OAuth flow, scope management, token refresh, and device discovery. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

SoundCloud API

Audio streaming platform focused on independent creators and user-generated music content

Choose SoundCloud when the use case involves independent or unsigned artist content, user-uploaded tracks, or community-driven audio sharing rather than major-label catalog access

Complementary

Musixmatch API

Song lyrics and metadata database for enriching Spotify track data with synchronized lyrics

Choose Musixmatch when you need song lyrics, synchronized lyric timestamps, or translation data to complement Spotify's audio features and playback

Complementary

Deepgram API

Speech-to-text transcription for generating searchable transcripts from podcast episodes

Choose Deepgram when you need to transcribe Spotify podcast episodes or audiobooks into searchable text for content indexing or summarization

FAQs

Specific to using Spotify Web API API through Jentic.

What authentication does the Spotify Web API use?

The Spotify Web API uses OAuth 2.0 with the authorization code flow for user-scoped access. It defines 19 scopes covering playback control, library management, playlist editing, user data access, and content upload. Access tokens expire after one hour and must be refreshed. Through Jentic, OAuth tokens and refresh cycles are managed in the MAXsystem vault — agents receive scoped access tokens without handling the OAuth dance.

Can I control playback on a specific device via the API?

Yes. GET /me/player/devices returns all active Spotify Connect devices with their IDs, names, and volume. Transfer playback with PUT /me/player passing the target device_id. Then use PUT /me/player/play, POST /me/player/pause, POST /me/player/next, POST /me/player/previous, and PUT /me/player/seek to control playback. Requires the user-modify-playback-state scope.

What are the rate limits for the Spotify Web API?

Spotify applies rate limits based on a rolling 30-second window. The exact limits vary by endpoint and app category. When exceeded, the API returns HTTP 429 with a Retry-After header indicating seconds to wait. Typical apps get approximately 180 requests per minute for most endpoints. Web API status endpoints and search may have different thresholds.

How do I build a recommendation playlist through Jentic?

Install the Jentic SDK with pip install jentic, then search for 'get music recommendations from spotify'. Jentic returns the GET /recommendations endpoint schema with seed_tracks, seed_artists, seed_genres parameters and tunable attributes (target_energy, target_valence, etc.). The agent constructs the request, receives recommended track URIs, and calls POST /playlists/{playlist_id}/tracks to populate a playlist.

Can I access audio analysis data for any track?

Yes. GET /audio-features/{id} returns high-level attributes (danceability, energy, tempo, key, time signature, valence) for any track. GET /audio-analysis/{id} returns detailed timing data including beats, bars, sections, and segments with pitch and timbre vectors. Both endpoints work with any track in Spotify's catalog regardless of user authorization.

Does the API support podcast and audiobook content?

Yes. The search endpoint accepts type=show for podcasts and type=audiobook for audiobooks. Dedicated endpoints exist for retrieving show details (GET /shows/{id}), episodes (GET /shows/{id}/episodes), audiobook chapters (GET /audiobooks/{id}/chapters), and managing saved shows and audiobooks in the user's library.