Change in access to deprecated Kraken Twitch APIs

[BarryCarlyon]

@Elyot_Grant

It likely requires little-to-no effort on your end to continue to support the headerless calls, so I hope you will do so.

I’m not Twitch staff. Just a moderator on these forums.

@Elyot_Grant

The screenshot I showed was from July 25th, the day you sent us the fucking email telling us that we needed to migrate. We read all the docs that day.

There is zero reason to be rude about this matter.

Twitch can and will change the docs as it needs to as updates and changes come from the relevant teams inside Twitch. As clearly it has done in this case.

@BarryCarlyon

Probably the easiest solution for you is for your Air Application to make a request to your backend server, and then your server can fetch and maintain a cache of who is live on the stream and deal with all the fun of the actual request headers and all. You probably already have such a server in order to serve updates for your app.

This is the simplest solution, just swap the call from Twitch directly to your backend server. Then you can benefit with your server caching the streams from Twitch or even utilizing webhooks.

Additionally you will need to change when v5 is removed completely and you have to move to Helix. As v5 is also deprecated