Top Related Projects
Basic examples to authenticate and fetch data using the Spotify Web API
A Node.js wrapper for Spotify's Web API.
A light weight Python library for the Spotify Web API
Open Source Spotify client library
Spotify for the terminal written in Rust 🚀
A Go wrapper for the Spotify Web API
Quick Overview
Spotify-web-api-js is a lightweight JavaScript wrapper for the Spotify Web API. It provides a simple and intuitive way to interact with Spotify's API endpoints, allowing developers to easily integrate Spotify functionality into their web applications.
Pros
- Easy to use and integrate into existing projects
- Supports both browser and Node.js environments
- Comprehensive coverage of Spotify Web API endpoints
- Well-documented with clear examples
Cons
- Requires Spotify API credentials for most operations
- Limited built-in error handling
- Doesn't handle authentication flow (requires separate implementation)
- May require frequent updates to keep up with Spotify API changes
Code Examples
- Searching for tracks:
const api = new SpotifyWebApi();
api.setAccessToken('your_access_token');
api.searchTracks('Bohemian Rhapsody')
.then(function(data) {
console.log('Search by "Bohemian Rhapsody"', data.tracks.items);
}, function(err) {
console.error(err);
});
- Getting a user's playlists:
api.getUserPlaylists('spotify_user_id')
.then(function(data) {
console.log('User playlists', data);
}, function(err) {
console.error(err);
});
- Adding tracks to a playlist:
const playlistId = 'your_playlist_id';
const trackUris = ['spotify:track:4iV5W9uYEdYUVa79Axb7Rh', 'spotify:track:1301WleyT98MSxVHPZCA6M'];
api.addTracksToPlaylist(playlistId, trackUris)
.then(function(data) {
console.log('Added tracks to playlist!', data);
}, function(err) {
console.log('Something went wrong!', err);
});
Getting Started
- Install the library:
npm install spotify-web-api-js
- Import and initialize the API wrapper:
import SpotifyWebApi from 'spotify-web-api-js';
const spotifyApi = new SpotifyWebApi();
- Set your access token:
spotifyApi.setAccessToken('your_access_token');
- Make API calls:
spotifyApi.getMe()
.then(function(data) {
console.log('User data:', data);
}, function(err) {
console.error('Error:', err);
});
Note: You'll need to handle authentication and token management separately. This library focuses on making API calls once you have a valid access token.
Competitor Comparisons
Basic examples to authenticate and fetch data using the Spotify Web API
Pros of web-api-examples
- Official Spotify repository with up-to-date examples
- Covers a wide range of API functionalities
- Provides examples in multiple programming languages
Cons of web-api-examples
- Focuses on individual API endpoints rather than providing a comprehensive library
- Requires more setup and configuration for each example
- Less abstraction, potentially leading to more verbose code
Code Comparison
spotify-web-api-js:
const spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('your_access_token');
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE')
.then(function(data) {
console.log('Artist albums', data);
}, function(err) {
console.error(err);
});
web-api-examples:
var request = require('request');
var authOptions = {
url: 'https://accounts.spotify.com/api/token',
headers: { 'Authorization': 'Basic ' + (new Buffer(client_id + ':' + client_secret).toString('base64')) },
form: { grant_type: 'client_credentials' },
json: true
};
request.post(authOptions, function(error, response, body) {
if (!error && response.statusCode === 200) {
var token = body.access_token;
// Use the token to access the Spotify Web API
}
});
The spotify-web-api-js library provides a more streamlined and abstracted approach, while web-api-examples offers more granular control but requires more setup code.
A Node.js wrapper for Spotify's Web API.
Pros of spotify-web-api-node
- Built specifically for Node.js, offering better integration with server-side JavaScript
- Provides Promise-based methods, allowing for more modern and cleaner asynchronous code
- Includes built-in authentication flow handling, simplifying OAuth 2.0 implementation
Cons of spotify-web-api-node
- Limited to server-side usage, not suitable for browser-based applications
- May have a steeper learning curve for developers new to Node.js environments
- Potentially larger package size due to additional Node.js-specific dependencies
Code Comparison
spotify-web-api-js:
var spotifyApi = new SpotifyWebApi();
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE', function(err, data) {
if (err) console.error(err);
else console.log('Artist albums', data);
});
spotify-web-api-node:
const SpotifyWebApi = require('spotify-web-api-node');
const spotifyApi = new SpotifyWebApi();
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE')
.then(function(data) {
console.log('Artist albums', data.body);
}, function(err) {
console.error(err);
});
The main differences in the code examples are the use of Promises in spotify-web-api-node and the callback-based approach in spotify-web-api-js. The Node.js version also requires importing the module, while the browser version assumes global availability.
A light weight Python library for the Spotify Web API
Pros of spotipy
- Written in Python, making it ideal for data analysis and machine learning projects
- Comprehensive documentation with examples for each endpoint
- Supports both synchronous and asynchronous operations
Cons of spotipy
- Limited to Python environments, less versatile for web applications
- Requires separate installation and management of dependencies
- May have slower performance compared to JavaScript-based alternatives
Code Comparison
spotipy:
import spotipy
from spotipy.oauth2 import SpotifyClientCredentials
sp = spotipy.Spotify(auth_manager=SpotifyClientCredentials())
results = sp.search(q='weezer', limit=20)
for idx, track in enumerate(results['tracks']['items']):
print(idx, track['name'])
spotify-web-api-js:
var spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('<access_token>');
spotifyApi.searchTracks('weezer')
.then(function(data) {
console.log('Search by "weezer"', data.tracks.items);
}, function(err) {
console.error(err);
});
Both libraries provide similar functionality for interacting with the Spotify API, but they cater to different programming environments and use cases. spotipy is more suitable for Python-based projects, especially those involving data analysis or machine learning, while spotify-web-api-js is better suited for web applications and JavaScript environments.
Open Source Spotify client library
Pros of librespot
- Native Rust implementation, offering better performance and lower resource usage
- Supports offline playback and local caching of tracks
- Provides lower-level access to Spotify's streaming protocol
Cons of librespot
- More complex to set up and use compared to spotify-web-api-js
- Limited to Spotify's streaming functionality, not covering the full Web API
- Requires more technical knowledge to integrate into projects
Code Comparison
spotify-web-api-js:
const spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('your_access_token');
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE').then(
function(data) {
console.log('Artist albums', data);
},
function(err) {
console.error(err);
}
);
librespot:
use librespot::core::authentication::Credentials;
use librespot::core::config::SessionConfig;
use librespot::core::session::Session;
let session = Session::connect(SessionConfig::default(), Credentials::with_password("username", "password"), None).await?;
The spotify-web-api-js library provides a higher-level, JavaScript-based interface for interacting with Spotify's Web API, making it easier to use for web developers. librespot, on the other hand, offers a lower-level Rust implementation that provides more control over the Spotify protocol but requires more setup and technical knowledge to use effectively.
Spotify for the terminal written in Rust 🚀
Pros of spotify-tui
- Terminal-based interface for a lightweight and efficient user experience
- Cross-platform compatibility (Linux, macOS, Windows)
- Vim-like keybindings for quick navigation and control
Cons of spotify-tui
- Limited to command-line interface, which may not be user-friendly for all
- Requires separate installation of Spotify client for playback
- May have fewer features compared to the web-based API wrapper
Code Comparison
spotify-tui (Rust):
let spotify = Spotify::default()
.client_credentials_manager(client_credentials_manager)
.build();
let track = spotify.track("11dFghVXANMlKmJXsNCbNl").await?;
spotify-web-api-js (JavaScript):
const spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('<access_token>');
spotifyApi.getTrack('11dFghVXANMlKmJXsNCbNl')
.then(function(data) {
console.log('Track information', data.body);
}, function(err) {
console.error(err);
});
The code comparison shows that spotify-tui uses Rust and async/await syntax, while spotify-web-api-js uses JavaScript with Promises. Both examples demonstrate how to retrieve track information, but the implementation details differ due to the languages and design choices of each project.
A Go wrapper for the Spotify Web API
Pros of spotify
- Written in Go, offering better performance and concurrency handling
- Provides a more comprehensive set of features, including authentication and token management
- Supports both the Web API and the Spotify Connect API
Cons of spotify
- Less actively maintained, with fewer recent updates
- May have a steeper learning curve for developers not familiar with Go
- Documentation is less extensive compared to spotify-web-api-js
Code Comparison
spotify-web-api-js:
const spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('your_access_token');
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE').then(
function(data) {
console.log('Artist albums', data);
},
function(err) {
console.error(err);
}
);
spotify:
client := spotify.New(auth.New(spotifyauth.NewAuthenticator(redirectURI, scopes...)))
client.Token = token
albums, err := client.GetArtistAlbums(spotify.ID("43ZHCT0cAZBISjO8DG9PnE"), nil)
if err != nil {
log.Fatal(err)
}
fmt.Println("Artist albums:", albums)
Both libraries provide similar functionality, but spotify offers a more idiomatic approach for Go developers, while spotify-web-api-js is tailored for JavaScript environments.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
Spotify Web API JS
This is a lightweight wrapper for the Spotify Web API (2.6kB gzipped + compressed). It includes helper functions for all Spotify's endpoints, such as fetching metadata (search and look-up of albums, artists, tracks, playlists, new releases, podcasts) and user's information (follow users, artists and playlists, and saved tracks management).
It doesn't have any dependencies and supports callbacks and promises. It is intended to be run on a browser, but if you want to use Node.JS to make the requests, please check spotify-web-api-node.
A list of selected wrappers for different languages and environments is available on the Developer site's Libraries page.
The wrapper includes helper functions to do the following:
Music and Podcast metadata
- Albums, artists, tracks and playlists
- Audio features and audio analysis for tracks
- Albums for a specific artist
- Top tracks for a specific artist
- Artists similar to a specific artist
- Shows and episodes (podcasts)
Profiles
- User's emails, product type, display name, birthdate, image
Search
- Albums, artists, tracks, playlists, shows, and episodes
Playlist Management
- Get a user's playlists
- Create playlists
- Change playlist details
- Add tracks to a playlist
- Remove tracks from a playlist
- Replace tracks in a playlist
- Reorder tracks in a playlist
- Upload custom playlist cover image
User's Library
- Add, remove, and get tracks on a user's library
- Check if a track is in the signed in user's library
- Add, remove, and get shows (podcasts) on a user's library
Personalization
- Get a userâs top artists and tracks based on calculated affinity
- Get current userâs recently played tracks
Browse
- Get new releases
- Get featured playlists
- Get a list of categories
- Get a category
- Get a category's playlists
- Get recommendations based on seeds
- Get available genre seeds
Follow
- Follow and unfollow users
- Follow and unfollow artists
- Check if the logged in user follows a user or artist
- Follow a playlist
- Unfollow a playlist
- Get followed artists
- Check if users are following a Playlist
Player
- Get a user's available devices
- Get information about the user's current playback
- Get the user's currently playing track
- Transfer a user's playback
- Start/Resume a user's playback
- Pause a user's playback
- Skip user's playback to next track
- Skip user's playback to previous track
- Seek to position in currently playing track
- Set repeat mode on user's playback
- Set volume for user's playback
- Toggle shuffle for user's playback
- Queue a track or an episode
Installation
Install via node (since the requests are made using XMLHttpRequest, you will need a tool like Browserify to run this on a browser):
$ npm install -S spotify-web-api-js
Then, in your javascript file
var Spotify = require('spotify-web-api-js');
var s = new Spotify();
//s.searchTracks()...
or by making a copy of the src/spotify-web-api.js
file
Usage
We recommend you have a look at the documentation to get an overview of the supported .
The wrapper supports callback functions, as well as Promises (you can also use a polyfill), and Promises/A+ libraries such as Q and when.
First, instantiate the wrapper.
var spotifyApi = new SpotifyWebApi();
If you have an access token, you can set it doing:
spotifyApi.setAccessToken('<here_your_access_token>');
When you set an access token, it will be used for signing your requests. An access token is required for all endpoints.
If you want to use a Promises/A+ library, you can set it:
spotifyApi.setPromiseImplementation(Q);
Here you see how to get basic information using a function like getArtistAlbums
:
// get Elvis' albums, passing a callback. When a callback is passed, no Promise is returned
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE', function (err, data) {
if (err) console.error(err);
else console.log('Artist albums', data);
});
// get Elvis' albums, using Promises through Promise, Q or when
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE').then(
function (data) {
console.log('Artist albums', data);
},
function (err) {
console.error(err);
}
);
The promises also expose an abort
method that aborts the XMLHttpRequest. This is useful to cancel
requests that were made earlier and could be resolved out-of-sync:
var prev = null;
function onUserInput(queryTerm) {
// abort previous request, if any
if (prev !== null) {
prev.abort();
}
// store the current promise in case we need to abort it
prev = spotifyApi.searchTracks(queryTerm, { limit: 5 });
prev.then(
function (data) {
// clean the promise so it doesn't call abort
prev = null;
// ...render list of search results...
},
function (err) {
console.error(err);
}
);
}
The functions that fetch data from the API support also an optional JSON object with a set of options, such as the ones regarding pagination. These options will be sent as query parameters:
// passing a callback - get Elvis' albums in range [20...29]
spotifyApi.getArtistAlbums(
'43ZHCT0cAZBISjO8DG9PnE',
{ limit: 10, offset: 20 },
function (err, data) {
if (err) console.error(err);
else console.log('Artist albums', data);
}
);
// using Promises through Promise, Q or when - get Elvis' albums in range [20...29]
spotifyApi
.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE', { limit: 10, offset: 20 })
.then(
function (data) {
console.log('Album information', data);
},
function (err) {
console.error(err);
}
);
More examples
Note: The following examples use Promises/Q/when as the return object.
Here you can see more examples of the usage of this wrapper:
// get multiple albums
spotifyApi.getAlbums(['5U4W9E5WsYb2jUQWePT8Xm', '3KyVcddATClQKIdtaap4bV']).then(
function (data) {
console.log('Albums information', data);
},
function (err) {
console.error(err);
}
);
// get an artists
spotifyApi.getArtist('2hazSY4Ef3aB9ATXW7F5w3').then(
function (data) {
console.log('Artist information', data);
},
function (err) {
console.error(err);
}
);
// get multiple artists
spotifyApi
.getArtists(['2hazSY4Ef3aB9ATXW7F5w3', '6J6yx1t3nwIDyPXk5xa7O8'])
.then(
function (data) {
console.log('Artists information', data);
},
function (err) {
console.error(err);
}
);
// get albums by a certain artist
spotifyApi.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE').then(
function (data) {
console.log('Artist albums', data);
},
function (err) {
console.error(err);
}
);
// search tracks whose name, album or artist contains 'Love'
spotifyApi.searchTracks('Love').then(
function (data) {
console.log('Search by "Love"', data);
},
function (err) {
console.error(err);
}
);
// search artists whose name contains 'Love'
spotifyApi.searchArtists('Love').then(
function (data) {
console.log('Search artists by "Love"', data);
},
function (err) {
console.error(err);
}
);
// search tracks whose artist's name contains 'Love'
spotifyApi.searchTracks('artist:Love').then(
function (data) {
console.log('Search tracks by "Love" in the artist name', data);
},
function (err) {
console.error(err);
}
);
Nesting calls
When you need to make multiple calls to get some dataset, you can take advantage of the Promises to get a cleaner code:
// track detail information for album tracks
spotifyApi
.getAlbum('5U4W9E5WsYb2jUQWePT8Xm')
.then(function (data) {
return data.tracks.map(function (t) {
return t.id;
});
})
.then(function (trackIds) {
return spotifyApi.getTracks(trackIds);
})
.then(function (tracksInfo) {
console.log(tracksInfo);
})
.catch(function (error) {
console.error(error);
});
// album detail for the first 10 Elvis' albums
spotifyApi
.getArtistAlbums('43ZHCT0cAZBISjO8DG9PnE', { limit: 10 })
.then(function (data) {
return data.albums.map(function (a) {
return a.id;
});
})
.then(function (albums) {
return spotifyApi.getAlbums(albums);
})
.then(function (data) {
console.log(data);
});
Getting user's information
In order to get user's information you need to request a user-signed access token, from either the Implicit Grant or Authorization Code flow. Say for instance you want to get user's playlists. Once you get an access token, set it and fetch the data:
// get an access token
...
// set it in the wrapper
var spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('<here_your_access_token>');
spotifyApi.getUserPlaylists('jmperezperez')
.then(function(data) {
console.log('User playlists', data);
}, function(err) {
console.error(err);
});
spotifyApi.getPlaylist('4vHIKV7j4QcZwgzGQcZg1x')
.then(function(data) {
console.log('User playlist', data);
}, function(err) {
console.error(err);
});
Some functions don't need to receive the user's id as a parameter, and will use the user's information from the access token:
var spotifyApi = new SpotifyWebApi();
spotifyApi.setAccessToken('<here_your_access_token>');
spotifyApi
.getUserPlaylists() // note that we don't pass a user id
.then(
function (data) {
console.log('User playlists', data);
},
function (err) {
console.error(err);
}
);
Integrated Typescript Typings
Get great code completion for this package using the integrated typescript typings. It includes the complete typings of the Spotify Web Api too, so you'll know both how to the navigate the API as well as the response you are getting.
When bundling the library
If you are bundling spotify-web-api-js using e.g. webpack you can include the library and the typings into a typescript file like this:
import SpotifyWebApi from 'spotify-web-api-js';
let spotify = new SpotifyWebApi();
When using the library globally
If you are using the library globally, for example including directly from index.html, include the typings in the top of your typescript file. Typescript will then assume the library is already present globally. Adjust the path to node_modules
.
/// <reference path="../node_modules/spotify-web-api-js/src/typings/spotify-web-api.d.ts" />
let spotify = new SpotifyWebApi();
Running tests
In order to run the tests, run:
$ npm test
If you want to check out the coverage, run:
$ npm run test:coverage
Top Related Projects
Basic examples to authenticate and fetch data using the Spotify Web API
A Node.js wrapper for Spotify's Web API.
A light weight Python library for the Spotify Web API
Open Source Spotify client library
Spotify for the terminal written in Rust 🚀
A Go wrapper for the Spotify Web API
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot