mirror of
https://github.com/jpochyla/psst.git
synced 2026-04-27 15:35:56 +03:00
[GH-ISSUE #561] Depreciated API endpoints (Nov 27) #339
Labels
No labels
api
bug
build
documentation
duplicate
enhancement
good first issue
help wanted
idea
invalid
linux
lowprio
macos
pull-request
upstream
windows
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/psst#339
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jacksongoode on GitHub (Nov 28, 2024).
Original GitHub issue: https://github.com/jpochyla/psst/issues/561
https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
I'm not sure how this impacts Psst but I wanted to add it here to start a thread on issues that folks might find.
@karelbilek commented on GitHub (Nov 29, 2024):
Looking at the client.rs, it does indeed use exactly the deprecated APIs for the recommendations and for the audio analysis, at least.
github.com/jpochyla/psst@69314f9fe8/psst-gui/src/webapi/client.rs (L1353)@kingosticks commented on GitHub (Nov 29, 2024):
If you're using an access token derived from Spotify's desktop client ID (or similar), it should keep working for now. Presumably you're doing that. I think there's a good chance they won't ever kill that.... famous last words...
Edit:
You are:
github.com/jpochyla/psst@69314f9fe8/psst-core/src/session/access_token.rs (L11)@SO9010 commented on GitHub (Dec 2, 2025):
we can probably close this now @jacksongoode