Change Playlist Details
Change a playlist's name and public/private state. (The user must, of course, own the playlist.)Request body which must comply to the following JSON Schema:
{
"type" : "object",
"properties" : {
"name" : {
"type" : "string",
"description" : "The new name for the playlist, for example `\"My New Playlist Title\"`\n"
},
"public" : {
"type" : "boolean",
"description" : "The playlist's public/private status (if it should be added to the user's profile or not): `true` the playlist will be public, `false` the playlist will be private, `null` the playlist status is not relevant. For more about public/private status, see [Working with Playlists](/documentation/web-api/concepts/playlists)\n"
},
"collaborative" : {
"type" : "boolean",
"description" : "If `true`, the playlist will become collaborative and other users will be able to modify the playlist in their Spotify client. <br/>\n_**Note**: You can only set `collaborative` to `true` on non-public playlists._\n"
},
"description" : {
"type" : "string",
"description" : "Value for playlist description as displayed in Spotify Clients and in the Web API.\n"
}
},
"additionalProperties" : true,
"example" : {
"name" : "Updated Playlist Name",
"description" : "Updated playlist description",
"public" : false
}
}Specify how the response should be mapped to the table output. The following formats are available:
Raw Response: Returns the raw response in a single row with the following columns:
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Spotify Nodes from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!