starred/zotify

Fork 0

mirror of https://github.com/Googolplexed0/zotify.git synced 2026-04-24 22:05:53 +03:00

[GH-ISSUE #166] Bulk API Endpoints To-Be Removed #150

New issue

Open

opened 2026-02-27 04:57:49 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 04:57:49 +03:00

Owner

Originally created by @RGPZ on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/166

https://developer.spotify.com/blog/2026-02-06-update-on-developer-access-and-platform-security
https://developer.spotify.com/documentation/web-api/references/changes/february-2026

Seems like they're removing a lot of endpoints that allow us to grab information in bulk, seems like they're not getting rid of many playback information endpoints, however.

Originally created by @RGPZ on GitHub (Feb 6, 2026). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/166 https://developer.spotify.com/blog/2026-02-06-update-on-developer-access-and-platform-security https://developer.spotify.com/documentation/web-api/references/changes/february-2026 Seems like they're removing a lot of endpoints that allow us to grab information in bulk, seems like they're not getting rid of many playback information endpoints, however.

kerem added the

discussion

documentation

labels

2026-02-27 04:57:49 +03:00

kerem commented

2026-02-27 04:57:49 +03:00

Author

Owner

@yashikada commented on GitHub (Feb 8, 2026):

Development Mode use will require a Spotify Premium account

Maybe all the development IDs created with free accounts will no longer work.
I hope so.

@yashikada commented on GitHub (Feb 8, 2026): - Development Mode use will require a Spotify Premium account Maybe all the development IDs created with free accounts will no longer work. I hope so.

kerem commented

2026-02-27 04:57:49 +03:00

Author

Owner

@RGPZ commented on GitHub (Feb 9, 2026):

To be fair, Librespot requires a Spotify Premium account anyway so it's not like that affects us by much.

@RGPZ commented on GitHub (Feb 9, 2026): To be fair, Librespot requires a Spotify Premium account anyway so it's not like that affects us by much.

kerem commented

2026-02-27 04:57:50 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Feb 12, 2026):

Yes, this will affect us. It also undoes some of the optimizations added by the efficient-api branch, so that is unfortunate. I'll have a fix out before it goes into effect.

@Googolplexed0 commented on GitHub (Feb 12, 2026): Yes, this will affect us. It also undoes some of the optimizations added by the efficient-api branch, so that is unfortunate. I'll have a fix out before it goes into effect.

kerem commented

2026-02-27 04:57:50 +03:00

Author

Owner

@fafamobile commented on GitHub (Feb 12, 2026):

Would this still require development apps?

@fafamobile commented on GitHub (Feb 12, 2026): Would this still require development apps?

kerem commented

2026-02-27 04:57:50 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Feb 14, 2026):

Would this still require development apps?

These changes only serve to make Dev Apps more restricted and less efficient by forcing requests to go out individually per Content. They change nothing about credential accessibility.

But don't lose hope, I may have a lead on how to get around them being a hard requirement. I think it will still prevent some of the nice features like UserItem Queries and Search but it would be way more usable than the current state of the project for those without Dev Apps. All of this assumes the idea works, though.

@Googolplexed0 commented on GitHub (Feb 14, 2026): > Would this still require development apps? These changes only serve to make Dev Apps more restricted and less efficient by forcing requests to go out individually per Content. They change nothing about credential accessibility. **_But don't lose hope_**, I may have a lead on how to get around them being a hard requirement. I think it will still prevent some of the nice features like `UserItem` Queries and Search but it would be **way** more usable than the current state of the project for those without Dev Apps. All of this assumes the idea works, though.

kerem commented

2026-02-27 04:57:50 +03:00

Author

Owner

@RGPZ commented on GitHub (Feb 14, 2026):

Would this still require development apps?

These changes only serve to make Dev Apps more restricted and less efficient by forcing requests to go out individually per Content. They change nothing about credential accessibility.

But don't lose hope, I may have a lead on how to get around them being a hard requirement. I think it will still prevent some of the nice features like UserItem Queries and Search but it would be way more usable than the current state of the project for those without Dev Apps. All of this assumes the idea works, though.

Just wanna say thanks for all the effort that you've put in to try to support this branch with the amount of content that Spotify keeps changing, thought the app was going to be dead when they changed the login system from mercury to login5.

@RGPZ commented on GitHub (Feb 14, 2026): > > Would this still require development apps? > > These changes only serve to make Dev Apps more restricted and less efficient by forcing requests to go out individually per Content. They change nothing about credential accessibility. > > **_But don't lose hope_**, I may have a lead on how to get around them being a hard requirement. I think it will still prevent some of the nice features like `UserItem` Queries and Search but it would be **way** more usable than the current state of the project for those without Dev Apps. All of this assumes the idea works, though. Just wanna say thanks for all the effort that you've put in to try to support this branch with the amount of content that Spotify keeps changing, thought the app was going to be dead when they changed the login system from mercury to login5.