APIs for playlist manipulation would be nice

[eras]

This would allow buildings tools like playlist organizers. In my opinion organizing playlists is a bit lacking in the current TIDAL interface.

[aliaksei-taliuk]

Hi @eras , welcome to the forum, and thanks for your suggestion!

Exposing API for playlist manipulation is definitely on our TODO list. We can unfortunately not promise any date for when this will be available, but we will continue to share any progress we make.

Thanks

[schnetzi]

Are you able to provide more insights on your project plans? So what the next features will be and at what priority this feature is?

For me this is also a very important feature as I want to sync my playlists from spotify to tidal via node.js and I haven't found the possibility to do so with tidal.

[stefanmoro]

Hi @schnetzi,

TIDAL Developer Platform is still in very early stages, and we have taken an approach where we make things available as soon as we have something new to share, rather than develop it closed and release once "feature complete".

We hope that this approach will lead to faster feedback from the community, and ultimately better solutions. But we also acknowledge that it can lead to us not being able to give a clear timeline for all requests.

However, accessing "user data" (playlists, favourites etc) is one feature we are actively looking in to. Once we have any concrete updates we will make sure to share them here.

[einaralex]

Definitely, with collaborative playlists in mind, please!

[lyzkov]

Sure!

[thephenakist]

An ideal playlist endpoint would provide (at least) the ability to:

• Get Playlist (GET, information about the playlist, description, image, created date, owner...)
• Update Playlist (PUT, image, description...)
• Create Playlist (PUT, if no playlist ID specified a new playlist is created and the new playlist ID is returned in response)
• Get Playlist Items (GET, in addition to details provided by Get Playlist, this would also return the track IDs for items within the playlist)
• Add Items To Playlist (PUT, at a specified 'index' if specified, else index = length of items currently in playlist)
• Remove Items From Playlist (PUT, either by index w/ length of items, or by supplying IDs to remove from the playlist)
• Replace Playlist Items (PUT, all current items will be replaced by the supplied list of items)
• Get Playlist Version (GET, It may be beneficial to keep a unique version ID for the playlist, which clients can cache on calls and reference later to determine if they are in-sync with TIDAL's servers. This could simply be provided in the Get Playlist call, but worth mentioning.)
• Get User Playlists (GET, returns all playlists where specified user id is the creator / owner)

[fmalhe]

Hi @thephenakist, Thanks for the suggestion!
We are planning to get started on this soon, and community feedback is very welcome. Will post here once we have some more updates to share.

[gigbuilder]

Can you define "soon"

[ngoreico]

Hi !
I was wondering if there is any endpoint available right now to add songs to a playlist, considering that Tidal suggests using a third-party application to add songs from another platform to your account.
I would like to do the same thing as TuneMyMusic by my own.
Thanks !

[stefanmoro]

Hey @ngoreico

There are currently no endpoints available for this, but we are hoping to start this work soon!

[philipwilk]

Hello, I'm making a small program in rust for moving user's playlists from spotify to other streaming services using the ISRC of each track as the common ID across all services - so far I've implemented spotify to youtube, but I want to add Tidal as another destination. For this, I need to be able to get tracks by their ISRC, which you already have implemented, but also need to be able to create playlists and add tracks to them.

I have a suggestion for whatever endpoint you decide to have for adding tracks to a playlist; please support adding multiple tracks per api call. While this isn't much of a problem for me developing against the api; I can just have a for loop that iterates over each track and calls the endpoint for each one individually, it's admittedly very wasteful when it could just be batch processed with minimal requests. This is important for devs if you charge for using the api per request.

Youtube does not support this so the number of requests ends up being very high, which is especially important in their case where you have a quota and each request has a cost. Spotify currently supports this kind of action up to 100 tracks at a time, which is a fairly reasonable limit; a playlist of say 2500 tracks on takes 25 requests rather than 2500.

Also, would the saved tracks in 'my collection' be treated as a playlist or would they have their own endpoint?

[stefanmoro]

Hi @philipwilk ,

Our current priority is to expose more and unify existing data domains (my collection, user, playlists, revamped catalogue) on TIDAL Developer, so very timely input, thank you!

We will take your input into consideration as we now build out this access, and we hope to open up this functionality within the coming months.

[Kubas556]

Theoretically it is possible to use unofficial endpoint "https://listen.tidal.com/v2/my-collection/playlists/folders/create-playlist".

[dylmye]

I'm excited for this - I've been building a concert setlist app and my use case for this API is adding the tracks from a setlist to a user's playlist. I've been able to do this with Spotify's API but they aren't approving anyone's production usage this year 😬 Tidal is the superior platform so 🤞 this is on their roadmap soon!

[lyzkov]

Spotify has a terrible mobile SDK. They cut off most of the valuable partnerships couple of years ago with one unconsulted decision about discontinuing streaming services to integrated players. TIDAL has the potential to fill an abandoned niche.

[trbryant]

Also interested in this would like to build a workflow that accepts a request (artist name, track name) and then performs a search which returns a result set which can then be added to a playlist.

[peavers]

Simply being able to read a users collections/playlists would be enough for me at this point in time. I have user oauth flows wired up, but nothing to invoke with them :(

[gigbuilder]

Its been a year and we still do not have any method to generate or populate playlists. I write a CRM for DJs and we have about 2,000 customers - many want to use Tidal but the API is so limited that we really can't do anything to help them. When are you going to provide something similar to Spotify? They did it right.

[stefanmoro]

Hey,

A couple of months back we started rolling out our "V2" endpoints, essentially an improved way to format and structure our endpoints - mainly in how we handle relationships. We started with catalogue and search, and over the last 2 months we have also started exposing user data.

Just last week we rolled out the first endpoints giving access to playlists. At this stage we allow read access to user playlists, but we will start work on building support for write operations relatively soon.

The entire API is still in "beta", and will remain so for some more time as we continue to build out our new API, and also to integrate it into our own apps.

In addition to write operations for playlists, we are also planning for read/write operations to user collections.

[thephenakist]

Ah, thank you. I understand the design behind this endpoint now (that is: for users who have authorized an application permission to read the contents of THEIR OWN playlists). In the future I would like the ability for my application to READ the contents (items, description, owner, etc) of PUBLIC playlists, regardless of creator or app authorizations by using the playlist UUID.

[stefanmoro]

Hey @thephenakist,

Thank you for explaining your use case further, I get what you mean now.

You are correct, the current playlist endpoints require a request to be made on behalf of a TIDAL user (i.e. they require the supplied access token to be acquired through authorization code flow), regardless of if the playlist is public or not.

We have briefly discussed the possibility to allow "client credentials" access to public playlists, and will pick up that discussion as we continue expanding our playlist endpoints later this year. Good to hear you have a use case for it, valuable input for us!

[1729patrick]

Hi @stefanmoro,

I'm currently implementing your API in my app and am excited about the upcoming playlist creation feature. However, I'm encountering an issue with retrieving the user's playlists.

In the API Explorer Mode, I can see all my playlists. Yet, when I run the authorization flow to obtain user permissions (playlists.write and playlists.read), and use that token to fetch the playlists, the response returns an empty array of items.

I’ve debugged the access token and noticed one difference: the presence of "cuk": "developerPortal" and kid.

API Explorer Mode

User Authorization Flow

Could you please help me understand why this might be happening?

Thank you!

[1729patrick]

Just a follow-up on the previous issue @stefanmoro. It turns out the problem was related to the scopes. Having multiple scopes, even including "playlists.read", was causing the API to return an empty list of playlists for the user.

I resolved the issue by requesting only the permission to read users' playlists.

[aliaksei-taliuk]

@1729patrick This is also fixed already. Should be working for multiple scopes.

[jasongrishkoff]

Hi there, just chiming in with my use-case for the ability to manipulate playlists. We're implementing "playlist syncing" on SubmitHub.com, allowing the users to automatically keep their playlists synced cross-platform. So far we've integrated Apple, YouTube, Deezer, and SoundCloud. I've had a few curators ask me to add Tidal support, so will be keeping an eye on this thread :)

[smoothquark]

Thank you for this. I have been playing with the API. Quick question please - are the number of items returned limited to a maximum of 20? Am I missing something?
Examples: running from https://developer.tidal.com/apiref?spec=catalogue-v2&ref=get-artist-albums-v2 (https://openapi.tidal.com/v2/artists/{artist}/relationships/albums?countryCode=GB&include=albums)

1. id 1566 (Beyoncé) generates 20 albums on the API and also 20 on listen.tidal.com -> albums -> view all
2. Herbert von Karajan (64046) the api generates 20 albums as well but on listen.tidal.com -> albums -> view all there are well over 200 listed
   I am pretty sure Beyoncé has more than 20 albums on Tidal but only 20 are listed with both the API and listen.tidal.com, but Herbert von Karajan has 20 vs > 200?

[aliaksei-taliuk]

Hi @smoothquark

We're applying global cap of 20 items everywhere at this moment. But you definitely can iterate over all items.

For example, If you want iterate over an artist albums you must pick this particular relationship endpoint and use links -> next cursor you're getting in the response in order to request the next chunk of items.

[aliaksei-taliuk]

@dylmye is right, thanks for replying!

[smoothquark]

Ah, thank you! I've just seen the links->next after you pointed it out to me. I knew I must have been missing something. I don't think this is documented in the API documentation? I shall try it a bit later, and hopefully, everything will be OK. Also, I just realised that my query is off topic.

[aliaksei-taliuk]

I don't think this is documented in the API documentation?

It's part of the JSON:API spec.

[smoothquark]

Thank you. I was not aware that it was part of the JSON API spec.