Registering for an API key
To use The Echo Nest API, you'll need to get an API key. You'll need to use this API key in every API call. We use the key to enforce rate limits and compliance with our terms of service. As of March 29, 2016 we no longer allow new API keys.
We’re always working to make improvements to our Web APIs and today, we have some updates to share that will impact both The Spotify and The Echo Nest Web APIs.
Over the past two years, following Spotify’s acquisition of The Echo Nest, it’s become clear that rather than have two separate APIs with considerable overlap in features, it makes sense to migrate functionality and focus all of our future development on the Spotify API.
In doing so, there are a couple important dates you should be aware of:
- March 29th, 2016 - We are announcing three new APIs (details below) and The Echo Nest API will no longer be issuing new API keys
- May 31, 2016 - As of May 31st, The Echo Nest platform will no longer serve requests and developers will need to move over to the Spotify API.
As part of our migration of many of The Echo Nest API features over to the Spotify Web API, we’re announcing three new APIs today. The new Spotify Web APIs include:
- Audio Features - Access to audio information about tracks (energy, danceability, tempo, loudness, etc. as well as full detailed audio analysis)
- Recommendations - A recommendation API (to generate a list of tracks given a starting point from a seed artist, track or genre), with filtering capabilities to restrict the set of tracks that are returned.
- User's Top Artists, Tracks - Top-level user information such as top artists and tracks.
If you currently have an app that uses The Echo Nest API, check out the Spotify Web API as we’ve already migrated the most-used features.
As always, we’ll continue to add additional features and enhancements to ensure you have what you need for development.
For more information on these new APIs check out the details on the Spotify Blog.