Resource POST userCollections/{id}/relationships/tracks returns GENERIC_REQUEST_ERROR

[rickybasse]

hey team!

first of all, thanks a bunch for all the work you are doing to design, develop and improve the TIDAL API in an open way! really really appreciated that! 💙

I am in the process of migrating some programs I use to automate stuff on Spotify to TIDAL and I happened to run into what looks like a bug on the POST userCollections/{id}/relationships/tracks resource.

here are some of my curl tests that happen to work well for artists and albums but not for tracks unfortunately:

# albums
> curl -X 'POST' \
  'https://openapi.tidal.com/v2/userCollections/{id}/relationships/albums?countryCode=DE' \
  -H 'Authorization: Bearer ***' \
  -H 'Content-Type: application/vnd.api+json' \
  -d '{ "data": [{ "id": "2530370", "type": "albums" }] }'

200: ok  # ~> album is added to my collection

# artists
> curl -X 'POST' \
  'https://openapi.tidal.com/v2/userCollections/{id}/relationships/artists?countryCode=DE' \
  -H 'Authorization: Bearer ***' \
  -H 'Content-Type: application/vnd.api+json' \
  -d '{ "data": [{ "id": "6361", "type": "artists" }] }'

200: ok  # ~> artist is added to my collection

# tracks
> curl -X 'POST' \
  'https://openapi.tidal.com/v2/userCollections/{id}/relationships/tracks?countryCode=DE' \
  -H 'Authorization: Bearer ***' \
  -H 'Content-Type: application/vnd.api+json' \
  -d '{ "data": [{ "id": "2530371", "type": "tracks" }] }'

{"errors":[{"code":"GENERIC_REQUEST_ERROR","detail":"Your request could not be processed due to invalid input. Please check your data and try again."}]}

the Bearer access_token is obtained via the PKCE flow describe here

I am experiencing the same behavior in the Swagger UI available here upon authorization with my client_id and client_secret and the following scopes:

• collection.read
• collection.write
• playlists.read
• playlists.write

I am still getting familiar with the TIDAL API so perhaps I am missing something?

please let me know if any additional context can be helpful to help debug this!

[john-kick]

Same here. I tried adding the accept: */* or accept: application/vnd.tidal.v1+json header as well to the requests, as it is done in the swagger documentation, but no success. This should not make a difference, but who knows...

[rickybasse]

I retried today the same exact command and it worked for me

curl -X 'POST' \
  'https://openapi.tidal.com/v2/userCollections/{id}/relationships/tracks?countryCode=DE' \
  -H 'Authorization: Bearer ***' \
  -H 'Content-Type: application/vnd.api+json' \
  -d '{ "data": [{ "id": "2530371", "type": "tracks" }] }'

[rickybasse]

as mentioned here the endpoint is now working so I'll close this discussion

[kddlb]

I'm having this issue now.

[blackarcanis]

Same issue here on the /albums and /artists; got this error:
{"errors":[{"code":"GENERIC_REQUEST_ERROR","detail":"Your request could not be processed due to invalid input. Please check your data and try again."}]}
Randomly and sometimes it's working just by retrying the request.