410 gone when requesting private `/api` API namespace with 3rd party client ID

I am fully aware of this, but since there is no alternative to this, 3rd party applications have to use this endpoint. And it’s been used for the whole time now for several years. Now suddenly, it’s broken, but only for 3rd party client-ids, which is strange and raises a couple of questions.

There already are several 3rd party application developers which are now embedding the client-id of Twitch’s website in order to make it work again. I don’t think this is a proper solution and actually abusing the system.

What’s also a bit weird is that it already broke two days ago, but only for an hour, and then started working again. I would like to know if this is a bug or an intentional change, for example in order to stop certain people from view botting or so.

2 Likes