feat(apps): broaden Spotify read-only scopes#14
Merged
Conversation
Adds user-follow-read, user-read-playback-state, user-read-currently-playing, user-read-playback-position, and user-personalized so agents can access followed artists, player state, and personalized content in addition to library/playlists/top-tracks/history. Signed-off-by: Radek Ježek <radek.jezek@ibm.com>
github-project-automation
bot
moved this from Backlog
to Done
in Kagenti Issue Prioritization
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands the Spotify connector's default scopes to cover additional read-only endpoints that agents hit in practice. No write scopes added.
New scopes (all read)
user-follow-readGET /me/followinguser-read-playback-stateGET /me/player,/me/player/devices,/me/player/currently-playinguser-read-currently-playinguser-read-playback-positionuser-personalizedCombined with the existing scopes (
user-read-email,user-read-private,user-library-read,playlist-read-private,playlist-read-collaborative,user-top-read,user-read-recently-played), the connector now covers every read scope Spotify exposes on the Web API. The only Spotify scopes intentionally excluded are:user-library-modify,user-follow-modify,playlist-modify-public,playlist-modify-private,user-modify-playback-state,ugc-image-uploadstreaming(Web Playback SDK),app-remote-control(iOS/Android SDK)user-soa-*,soa-*(Spotify Open Access, for integration partners)Note unrelated to scopes
GET /playlists/{id}/tracksreturning 403 is a Spotify Web API access change from Nov 2024 — endpoints like/playlists/{id}/tracks,/audio-features,/audio-analysis, recommendations, and related-artists are restricted for apps in Development mode. No scope unlocks them. Workaround: read items embedded inGET /playlists/{id}(includes first 100 tracks with anextURL for pagination).Test plan
pnpm --filter @onecli/web lint— cleanpnpm --filter @onecli/web check-types— clean/me/following,/me/player,/me/player/currently-playingnow return 200