Automation

Spotify changes

What changed in Spotify's API and what it affects

Spotify has implemented sweeping changes to their developer API over the past year. Crucially, the API is no longer accessible to free accounts and is now strictly restricted to Spotify Premium users.

In addition to the new access restrictions, Spotify has completely deprecated multiple endpoints and stopped sharing several key pieces of metadata. The following information can no longer be retrieved from their API:

  1. Related artists
  2. Top tracks by an artist
  3. Playlists created by specific users
  4. Editorial playlists
  5. Popularity metrics (Artist, Track, and Album)

Click here to review the full list of endpoint changes directly on Spotify

What’s Included in This Update

To ensure your RKHM platform remains stable and optimized, we have removed all the deprecated Spotify endpoints in this release. To help fill the missing data gaps, we have integrated initial support for the MusicBrainz API, allowing you to fetch the following metadata natively

  1. Artists: Genres, tags, and similar artists
  2. Tracks & Albums: Genres and tags

The Roadmap: Building Independence

Our priority over the coming months is to integrate additional third-party metadata APIs, allowing us to partially or fully replace Spotify's data ecosystem within RKHM.

We are also planning to build and host our own dedicated metadata API. By compiling an small proprietary database of over 1 million popular artists, we intend to independently gather the missing data—including popularity metrics, top tracks, and similar artists—and feed it directly into your RKHM installation via our existing API

Recheck your Music Cronjobs
Some endpoints are removed. If you have previously created cronjobs to get "user's playlists" or "category's playlists" you might need to remove them