Reorder or Replace Playlists Tracks

Update Playlist Items

Either reorder or replace items in a playlist depending on the request's parameters. To reorder items, include range_start, insert_before, range_length and snapshot_id in the request's body. To replace items, include uris as either a query parameter or in the request's body. Replacing items in a playlist will overwrite its existing items. This operation can be used for replacing or clearing items in a playlist.
Note: Replace and reorder are mutually exclusive operations which share the same endpoint, but have different parameters. These operations can't be applied together in a single request.

Options

Playlist Id

The Spotify ID of the playlist.

Uris (*)

A comma-separated list of Spotify URIs to set, can be track or episode URIs. For example: uris=spotify:track:4iV5W9uYEdYUVa79Axb7Rh,spotify:track:1301WleyT98MSxVHPZCA6M,spotify:episode:512ojhOuo1ktJprKbVcKyQ
A maximum of 100 items can be set in one request.

Body

Request body which must comply to the following JSON Schema:

{
  "type" : "object",
  "properties" : {
    "uris" : {
      "type" : "array",
      "items" : {
        "type" : "string"
      }
    },
    "range_start" : {
      "type" : "integer",
      "description" : "The position of the first item to be reordered.\n"
    },
    "insert_before" : {
      "type" : "integer",
      "description" : "The position where the items should be inserted.<br/>To reorder the items to the end of the playlist, simply set _insert_before_ to the position after the last item.<br/>Examples:<br/>To reorder the first item to the last position in a playlist with 10 items, set _range_start_ to 0, and _insert_before_ to 10.<br/>To reorder the last item in a playlist with 10 items to the start of the playlist, set _range_start_ to 9, and _insert_before_ to 0.\n"
    },
    "range_length" : {
      "type" : "integer",
      "description" : "The amount of items to be reordered. Defaults to 1 if not set.<br/>The range of items to be reordered begins from the _range_start_ position, and includes the _range_length_ subsequent items.<br/>Example:<br/>To move the items at index 9-10 to the start of the playlist, _range_start_ is set to 9, and _range_length_ is set to 2.\n"
    },
    "snapshot_id" : {
      "type" : "string",
      "description" : "The playlist's snapshot ID against which you want to make the changes.\n"
    }
  },
  "additionalProperties" : true,
  "example" : {
    "range_start" : 1,
    "insert_before" : 3,
    "range_length" : 2
  }
}

Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

Snapshot Id:

Raw Response: Returns the raw response in a single row with the following columns:

body: Response body
status: HTTP status code

Input Ports

: Configuration data.

Output Ports

: Result of the request depending on the selected Result Format.
: Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

No recommendations found

Popular Successors

No recommendations found

Views

This node has no views

Workflows

No workflows found

Developers

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.

Go to Product

Installation

To use this node in KNIME, install the extension Spotify Nodes from the below update site following our NodePit Product and Node Installation Guide:

v5.9

A zipped version of the software site can be downloaded here.

Plugin provider: NodePit

Plugin version: 1.2.2.202503311329

On NodePit since: 2025-12-11

Last update: 2026-01-10

KNIME versions: Since v4.4

NodePit ExclusiveOnly available on NodePit

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!