Save Tracks for Current User in Spotify
A documented Spotify operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Save Tracks for Current User
- PUTChanges data · Tracks
api.spotify.com/me/tracks
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Spotify operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Spotify operations
- Add Item to Playback QueuePOST · changes data
- Create PlaylistPOST · changes data
- Add Items to PlaylistPOST · changes data
- Remove User's Saved ShowsDELETE · changes data
- Save Shows for Current UserPUT · changes data
- Remove Users' Saved AlbumsDELETE · changes data
- Save Albums for Current UserPUT · changes data
- Remove User's Saved TracksDELETE · changes data
Questions
- Can HumDay save tracks for current user in Spotify?
- Yes. This operation is published in Spotify's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Spotify data?
- Yes — this is a PUT operation, so it changes something in Spotify. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Spotify account.
Where this came from
Read from a published API description for Spotify at developer.spotify.com/_data/documentation/web-api/reference/open-api-schema.yml. The description above is the provider’s own wording, not ours. Last published 2023-02-17.