In a move sure to anger developers and users, Spotify has changed the terms for its Web API, cracking down on how apps can use it.
Spotify’s Web API allows third-party apps to access Spotify and provide an alternative experience for users unhappy with the company’s default apps. Like Reddit before it, Spotify seems to be changing its stance on third-party access, making it harder for developers.
The company announced the changes in a developer blog post on November 27.
Since our last broader update on the Community platform, we continue to see new integrations made through Spotify’s APIs and SDKs. We’re excited about the continued engagement we’re seeing to learn, experiment, innovate, and deliver unique experiences with Spotify.
As we continue to review the experience provided on Spotify for Developers, we’ve decided to roll out a number of measures with the aim of creating a more secure platform.
The company makes clear that the changes impact new Web API use cases, not existing apps.
Effective today, new Web API use cases will no longer be able to access or use the following endpoints and functionality in their third-party applications. Applications with existing extended mode Web API access that were relying on these endpoints remain unaffected by this change.
- Related Artists
- Recommendations
- Audio Features
- Audio Analysis
- Get Featured Playlists
- Get Category’s Playlists
- 30-second preview URLs, in multi-get responses (SimpleTrack object)
- Algorithmic and Spotify-owned editorial playlists
These changes will impact the following Web API applications:
- Existing apps that are still in development mode without a pending extension request
- New apps that are registered on or after today’s date
The company says “third party integrations continue to play an important role in the way users can experience the Spotify experiencing through third party apps.” Regardless of what the company says, however, the API change is not an encouraging indication of where things are going for third-party developers.