TIDAL v1 API keeps 404-ing every request

[sushiroles]

This started about 3 days ago, suddenly any search or ID lookup call to the TIDAL v1 Web API returns a 404 error. I don't know what could possibly cause this, I haven't changed anything to my code or my network setup. Any leads?

[regorxxx]

Can also confirm the same problem.

[stefanmoro]

Hey,

The V1 API documentation was removed around 6 months ago, and the entire V1 API has now been fully deprecated. Please update any applications to use the API documented on developer.tidal.com/reference/web-api.

Thanks

[ungive]

A deprecation notice on the "removed" pages would have been nice and/or a warning in the 404 response!

[regorxxx]

Yep, the problem some devs are experiencing is that there was no deprecation notice, so timelines were not clear. Thanks for the reply though

[keenan-v1]

Thank you folks for answering, though it's disappointing to see the lack of notifications here. The developer website makes no mention of the V1 deprecation. I looked all over, not a blog or anything.

IMHO for customer satisfaction, turning V1 back on with another 6-month window and a proper notice would be the move here.

[stefanmoro]

Hey @keenan-v1 , thanks for the feedback.

TIDAL Developer API is still not considered fully production ready (marked as Beta both developer.tidal.com and the API reference, and application review still not possible.) The V1 documentation was removed from developer.tidal.com around 6 months ago, so this change was only implicitly signalled.

We don't expect any major changes to the API from now on (potentially some minor fixes and cleanup), but as long as we remain in Beta we may introduce non-backwards compatible changes. However, we'll notify more explicitly about any potential changes we make while in Beta by posting here.

Thank you.

[sushiroles]

I appreciate TIDAL's work on the API, but killing off V1 while V2 is still in Beta, and is unusable for a number of applications is possibly the worst thing you all could've done. My app requires artist and album metadata of songs, which is not included with V2 responses in an immediately usable form, and the V2 API is still so 429 trigger happy that getting the full data via the included relationship URL-s for even just a few results is impossible, unless you're ready to butcher performance of your app and make everything load for ages. I'm sure this will be ironed out in the future, but my disappointment in how mismanaged this situation is, is immeasurable.