[Question] Is it possible to add songs to favorites with a timestamp

[schlagmichdoch]

Thanks for this project!

I have a CSV file with the columns ISRC code and added at datetimestamps containing all my favorite tracks that I exported from another streaming service. I would now love to reproduce my favorites "added at" history in Tidal.

For this, I need to be able to add songs to the users favorite tracks with a modified addedAt attribute.

Currently, the add_track method does not include any parameters but the track id:

python-tidal/tidalapi/user.py

Lines 370 to 372 in dd803f8

	return self.requests.request(
	"POST", f"{self.base_url}/tracks", data={"trackId": ",".join(track_id)}
	).ok

I'm not sure about the used API call but for other POST calls this seems to be possible via a meta attribute:
/userCollections/{id}/relationships/tracks:

{
  "data": [
    {
      "id": "string",
      "meta": {
        "addedAt": "2025-12-15T18:49:27.670Z"
      },
      "type": "tracks"
    }
  ]
}

Do you think this would be possible for favorite tracks as well and would you be open to integrate this into your library?

[tehkillerbee]

The API you are referring to is not quite the same as the one used by tidalapi, as the latter is closed source. As far as I know, it is not possible to set any additional data fields apart from "trackId" and "onArtifactNotFound", when using the v1 tracks endpoint.

Of course, the openapi could be used for such requests, as it does look like it supports using the timestamp as well, so technically that should work.

Ideally, we should migrate all supported endpoints from the "closed source" API to the openapi, as mentioned here: #381

The ISRC method get_tracks_by_isrc() and get_albums_by_barcode() is one of the few using the openapi v2 endpoints. So adding the endpoint you mentioned could be done in a similar fashion.

[schlagmichdoch]

Sounds reasonable.

I am unsure though what the precise endpoint would be. get_tracks_by_isrc() uses /tracks and get_albums_by_barcode() uses /albums. Currently the add_track method uses POST users/{user_id}/favorites/tracks [1] but I can't find any favorites or users endpoint in the openapi documentation.

Is this not implemented yet in the openapi v2 endpoint on Tidals part or is this handled entirely differently in the new api?

[1]:

python-tidal/tidalapi/user.py

Line 286 in dd803f8

self.base_url = f"users/{user_id}/favorites"

python-tidal/tidalapi/user.py

Line 371 in dd803f8

"POST", f"{self.base_url}/tracks", data={"trackId": ",".join(track_id)}

[tehkillerbee]

I believe the userCollections/**/ that you found in openapi is essentially the same thing as the user/**/favorites/tracks in the v1 API.

The openapi can be accessed in a similar fashion like the before mentioned functions so I added them for inspiration.

Anyways, the openapi and the closed api is not really interchangeable, they don't contain the same endpoints. I'm not sure what the end goal is for tidal. But I'd like to move to the openapi wherever it's possible. So far we use a mismatch of the v1 API, v2 API and the v2 openapi...

[schlagmichdoch]

I believe the userCollections/**/ that you found in openapi is essentially the same thing as the user/**/favorites/tracks in the v1 API.

Ah, that would make sense. I’ll play around with the API and will report back whether changing the favorites endpoint would work.