Spotify WebApi changed

[geffrey-dnl]

The problem

I tried adding the spotify integration today, after it wasn't possible for a long period (from december 2025).

They seem to have changed the response model

And I now get follow error log in Home Assistant

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 416, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/spotify/coordinator.py", line 117, in _async_update_data
    self._playlist = await self.client.get_playlist(context.uri)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 96, in wrapper
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 645, in get_playlist
    return Playlist.from_json(response)
           ~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "<string>", line 4, in __mashumaro_from_json__
  File "<string>", line 84, in __mashumaro_from_json__
mashumaro.exceptions.MissingField: Field "tracks" of type PlaylistTracks is missing in Playlist instance```

### What version of Home Assistant Core has the issue?

core-2026.2.1

### What was the last working version of Home Assistant Core?

_No response_

### What type of installation are you running?

Home Assistant OS

### Integration causing the issue

Spotify

### Link to integration documentation on our website

https://www.home-assistant.io/integrations/spotify/

### Diagnostics information

_No response_

### Example YAML snippet

```yaml

Anything in the logs that might be useful for us?

Unexpected error fetching spotify data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 416, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/spotify/coordinator.py", line 117, in _async_update_data
    self._playlist = await self.client.get_playlist(context.uri)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 96, in wrapper
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 645, in get_playlist
    return Playlist.from_json(response)
           ~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "<string>", line 4, in __mashumaro_from_json__
  File "<string>", line 84, in __mashumaro_from_json__
mashumaro.exceptions.MissingField: Field "tracks" of type PlaylistTracks is missing in Playlist instance

Additional information

No response

[home-assistant]

Hey there @frenck, @joostlek, mind taking a look at this issue as it has been labeled with an integration (spotify) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of spotify can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign spotify Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@geffrey-dnl Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20spotify%22%20
_{^{(message by IssueContext)}}

---

spotify documentation
spotify source
_{^{(message by IssueLinks)}}

[joostlek]

They already changed this today? I thought I still had a few months

[geffrey-dnl]

They already changed this today? I thought I still had a few months

I think this applies to newly created clients, so it applies to me. Not sure for users before today.

https://developer.spotify.com/blog/2026-02-06-update-on-developer-access-and-platform-security

[geffrey-dnl]

The problem I encountered didn't seem to be caused by the api changes. Suddenly the integration started working, maybe some error because of Spotify that was updating their platform. Should I close this issue? @joostlek

[davidesolito]

I’ve been trying since this morning to add Spotify to Home Assistant. I also had been waiting since December because it wouldn’t let me create any app on Spotify Developer. No luck. I can’t add the integration — it keeps giving errors.

[KE4HTS]

Having similar issue, I was able to create the app on Spotify, Integration installs I can add it to a dashboard, then does nothing, becomes "unavailable".

[dhkatz]

They already changed this today? I thought I still had a few months

If by a few months you mean like 3 weeks then yeah. All new clients get the new restrictions and changes. Old clients will get the new changes by March 9.

[abels7]

Same problem here:

Unexpected error fetching spotify data
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 96, in wrapper
return await func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 645, in get_playlist
return Playlist.from_json(response)
~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "", line 4, in mashumaro_from_json
File "", line 3, in mashumaro_from_json
orjson.JSONDecodeError: unexpected character: line 1 column 1 (char 0)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 416, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/spotify/coordinator.py", line 117, in _async_update_data
self._playlist = await self.client.get_playlist(context.uri)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 99, in wrapper
raise SpotifyError(msg) from e
spotifyaio.exceptions.SpotifyError: Failed to decode JSON: unexpected character: line 1 column 1 (char 0)

No way to add integration.

[ocean90]

I also received an email from Spotify informing me about the changes today. In case anyone is interested, here are the details:

Hi,

Further to the updates posted on our Developer Blog on February 6, 2026, we’re sharing a reminder of some upcoming changes to your Spotify for Developers account.

Starting March 9, 2026, we will start applying the new restrictions and requirements to all applications in “Development Mode” using Spotify’s Web API. This includes:

• A Spotify Premium requirement: Development Mode use will require a Spotify Premium account (incl. Family and duo). This is to ensure accountability and to reduce automated misuse at scale. Only the main account associated with the app must be on Premium. Authorized users do not need a subscription.

• Updated endpoints and fields: We’re limiting Web API Development Mode access to a smaller set of supported endpoints and fields. To ensure that your application continues to work, please review the changes and make the necessary modifications ahead of the March 9 deadline.

• 1 Client ID per developer: Each developer is limited to one Development Mode Client ID. If you currently have more than one, they will continue to function. However, you will not be able to create additional Development Mode Client IDs until you are back within the limit.

• Max five authorized users: Each Client ID may have up to five authorized users. If you currently have more than five authorized users, nothing will be removed on March 9. Your app will keep working, but you will not be able to add or modify users until you are within the limit.

Note: These changes do not affect apps already operating in Extended Quota Mode.

This update means Spotify will continue to support experimentation and personal projects but within more clearly defined limits. We also want to reiterate that Development Mode provides a sandboxed environment for learning and experimentation. It is intentionally limited and should not be relied on as a foundation for building or scaling a business on Spotify.

For full context, rationale, and additional details, please review the original announcement blog post.

If you have questions, we encourage you to share them on the Spotify Developer Community forum.

Spotify for Developers

[thlucas1]

@joostlek
SpotifyPlus author here - here's what I have learned from making changes for my integration ...

The new endpoints are already in place (since 02/11 I believe). All February changes are enforced starting 2026/03/09. Check out the Spotify February 2026 Migration Guide for a step-by-step process of what needs to be done.

I believe that any Spotify Developer App client id's created after 2026/02/11 are already enforcing the new rules, but can't verify this. I believe there will be intermittent issues like the OP reported up until 03/09, at which time the exceptions reported above will be the norm.

Here is a summary of the changes I made to the SpotifyPlus Integration:

• Added SpotifyClient.CheckUserFavorites method to check if one or more items are already saved in the current user's library. Accepts Spotify URIs for tracks, albums, episodes, shows, audiobooks, artists, users, and playlists.
• Added SpotifyClient.SaveUserFavorites method to add one or more items to the current user's library. Accepts Spotify URIs for tracks, albums, episodes, shows, audiobooks, users, and playlists.
• Added SpotifyClient.RemoveUserFavorites method to remove one or more items from the current user's library. Accepts Spotify URIs for tracks, albums, episodes, shows, audiobooks, users, and playlists.
• Updated the following SpotifyClient methods to use the new CheckUserFavorites method: CheckAlbumFavorites, CheckArtistsFollowing, CheckAudiobookFavorites, CheckEpisodeFavorites, CheckPlaylistFollowers, CheckShowFavorites, CheckTrackFavorites, CheckUsersFollowing.
• Updated the following SpotifyClient methods to use the new SaveUserFavorites method: SaveAlbumFavorites, SaveAudiobookFavorites, SaveEpisodeFavorites, SaveShowFavorites, SaveTrackFavorites, FollowArtists, FollowPlaylist, FollowUsers.
• Updated the following SpotifyClient methods to use the new RemoveUserFavorites method: RemoveAlbumFavorites, RemoveAudiobookFavorites, RemoveEpisodeFavorites, RemoveShowFavorites, RemoveTrackFavorites, UnfollowArtists, UnfollowPlaylist, UnfollowUsers.
• Updated the following SpotifyClient methods to return a "deprecated" exception, as they are no longer supported by Spotify: GetAlbumNewReleases, GetAlbums, GetArtists, GetArtistTopTracks, GetAudiobooks, GetBrowseCategory, GetBrowseCategorys, GetChapters, GetEpisodes, GetMarkets, GetPlaylistsForUser, GetShows, GetTracks, GetUsersPublicProfile.
• Updated SpotifyClient search methods to limit parameter maximum / default values; maximum value has been reduced from 50 to 10, and the default value has been changed from 20 to 5.

Hope it helps!