|
Some time in the next few hours we will be releasing the first official (i.e. non-beta) release of Version 4 of the Echo Nest API. There are lots of new features in V4 - too many to mention here, but to highlight just a few:
- Faster
- song/identify - Identifies a song given Echo Nest Musical Fingerpint hash codes.
- artist search - now supports extended constraints and sorts, query by description
- artist similarity - now supports extended constraints and sorts
- more artist data
- improved song search (with super powerful boosting)
- Data Feeds - we’ve got rss feeds for nearly everything
There are updates to our client libraries to support all the new features: pyechonest and jEN.
So what does this mean to you? Well, if you are using our APIs, you don't have to do anything right now, everything should work the same as it did before the release. Version 3 APIs will still be available and will still work exactly the same as they did last week. If you've been using the V4 beta APIs via 'beta.developer.echonest.com', these will continue to work as before as well. However, you will also be able to use the new V4 APIs directly via the URL 'developer.echonest.com/api/v4.
The Transition Plan
If you are using the V4 beta, you should switch your URLs from beta.developer.echonest.com to developer.echonest.com within the next month. We will stop supporting beta.developer.echonest.com by August 15. If you are using V3 of the APIs, you should think about transitioning to V4 in the next 6 months. We do not plan to support the V3 API beyond 2010. If you are using V2 of the API (is there anyone still using V2 of the API?), you should plan on transitioning to V4 by the end of July. V2 has been deprecated for a while and support for V2 will stop in the very near future.
|