Get Information About the Users Current Playback

Go to Product

Get Playback State

Get information about the user’s current playback state, including track or episode, progress, and active device.


Market (*)

An ISO 3166-1 alpha-2 country code. If a country code is specified, only content that is available in that market will be returned.
If a valid user access token is specified in the request header, the country associated with the user account will take priority over this parameter.
Note: If neither market or user country are provided, the content is considered unavailable for the client.
Users can view the country that is associated with their account in the account settings.

Additional Types (*)

A comma-separated list of item types that your client supports besides the default track type. Valid types are: track and episode.
Note: This parameter was introduced to allow existing clients to maintain their current behaviour and might be deprecated in the future.
In addition to providing this parameter, make sure that your client properly handles cases of new types in the future by checking against the type field of each object.

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.
    • Device:
    • Repeat State: off, track, context
    • Shuffle State: If shuffle is on or off.
    • Context:
    • Timestamp: Unix Millisecond Timestamp when data was fetched.
    • Progress Ms:

      Progress into the currently playing track or episode. Can be null.

    • Is Playing:

      If something is currently playing, return true.

    • Item:

      The currently playing track or episode. Can be null.

    • Currently Playing Type:

      The object type of the currently playing item. Can be one of track, episode, ad or unknown.

    • Actions:
  • 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


This node has no views


  • No workflows found



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.