Getting 403 errors and a Captcha URL in response body of playlists queries #86
Replies: 2 comments 2 replies
-
I'm getting the same thing when trying to browse the deveoper documentation or any page at under developer.tidal.com. If I had to guess there is either something going haywire with their security solution, or misconfiguration in their cloudfront caching policies, or none of the above. ONCE it delivered me a captcha to solve which bought me a few minutes of looking through the api docs, then it showed up again without any possibility of getting through it. 😞 |
Beta Was this translation helpful? Give feedback.
-
Hey @duttonst, @philipsoutham, thanks for reaching out. It seems our bot protection got a bit to eager here. We're still considering TIDAL API to be in "beta" as we work on expanding functionality and tuning other aspect of it. We'll look into this specific situation next week. Thank you for your patience. |
Beta Was this translation helpful? Give feedback.
-
After successfully reading a 1,500 track playlist (and all of the many associated track queries I needed in order to retrieve artist & album details) I now seem to have been blocked from the endpoint for all playlist queries, e.g.
https://openapi.tidal.com/v2/playlists/me?include=items
no longer works.I now only get 403 responses with the following body:
{"url":"https://geo.captcha-delivery.com/captcha/?(lots of parameters here)"}
A couple of points:
Using 429 responses would be a more conventional way to ask a client to back-off. I did actually receive some 429s and did back-off when requested, but I still ended-up getting blocked.
Beta Was this translation helpful? Give feedback.
All reactions