We have just released our new Web API. It’s based on industry-standard REST principles and allows your applications to query the Spotify catalogue and users’ playlists through standard HTTP requests.
This Web API lets you include album art, 30 second track previews, top tracks per artist per country, album genres, and much more, within your web applications.
And by using standard OAuth 2.0 mechanisms, users can grant your application access to profile information including playlists, display name, image, country, email, external URL, and subscriber status. Among other things, this means web apps can now build real Spotify playlists that users can listen to later using a wide variety of methods.
On that front, we’ve forged a tighter link between the Spotify and Echo Nest APIs, making it easier to build apps on the capabilities and deep data of both resources. The Echo Nest now has the most up-to-date view of Spotify’s catalog, and you can use Spotify Artist and Track IDs in Echo Nest API calls to build playlists, streaming radio stations, and more. But really, the best way to understand that integration is to check out the demos.
Take a look at our detailed documentation; we have user guides and tutorials and full reference pages for each endpoint. We also have many useful code examples, and members of our community have prepared wrappers for some of the most popular languages and platforms.
In the near future we will be adding more endpoints to the Web API, giving developers access to yet more Spotify data.
Note: With the release of the Web API we are formally deprecating our existing Metadata API. All the data that was returned by the Metadata API is available through the Web API, and we have a comprehensive Migration Guide to help you through the transition. For now, the Metadata API endpoints are still available, but be aware that they will be removed some time in the future.