openapi.tidal.com/v2/tracks does not return multiple tracks when filtering by ISRC

[Inrixia]

With the removal of openapi.tidal.com/tracks/byIsrc it seems it is no longer possible to look up tracks by their ISRC, the original endpoint (mentioned here: https://github.com/orgs/tidal-music/discussions/26) had been working fine until the last few days but it now returns 404, presumably due to the removal of all pre v2 endpoints.

The new endpoint openapi.tidal.com/v2/tracks only returns a single track.

For example:
https://openapi.tidal.com/v2/tracks?countryCode=US&filter[isrc]=NZUM71200031

This correctly returns the track Royals, but only returns a single entry and the track id it gives is for the High (LOSSLESS) version despite there being multiple versions of this track with the same ISRC (linked below).

High Quality: https://tidal.com/browse/track/22964850
HiRes Quality: https://tidal.com/browse/track/77632180

Both the above tracks have the same ISRC

The previous endpoint returned all variations of the track with the same ISRC.
I presume this is a bug in the new endpoint

[RebellionBritney]

I mean, it would be cool if they unify in the official clients all the multiple versions and just show and play the higher quality version. (ex. Just show the 192kHz file, instead of the 44.1 or 96) Look how Amazon Music does it, they also unify the Stereo and Atmos versions, like Apple Music, it's easier to find them in that way.

But in the meantime they really needs to fix the new endpoint.

[stefanmoro]

Hey @Inrixia , thanks for reaching out.

We've now updated the behaviour of the "filter by isrc" endpoint to return a pageable collection of all tracks available in the country defined by countryCode for the defined isrc.

Thanks

[Inrixia]

That's perfect thanks! I'll give this a look and update here if there's anything outstanding with the new changes.

Much appreciated thanks for the work ❤️

[Inrixia]

All working perfectly now thanks! Though I am seeing slightly more rate limiting compared to before, but nothing too egregious.

It would be ideal if when getting a 429 response the retry-after header was set in seconds how long to wait before the next request.

[Inrixia]

Being able to filter to only tracks with attributes.mediaTags.includes("HIRES_LOSSLESS") would remove the need for a ton of requests to go through too which would be preferrable if possible.