Hi again
I will have to reach the teams within our organisation that implemented the clients side of the applications integrating the Twitch api. For my part, I am simply responsible in the flow to receive the token, validate it, and obtain Twitch profile identity.
I have just tested the addition of v5 as a query param and it looks positive. I haven’t identify any api breaks that would prevent me to simply change the url used by our backend from the broken one, to the one with the query param v5. Sound like a good short term option.
So if I understand correctly, the v5 will be deprecated as well, but not super short term. It will give us enough time to look into the latest and greatest api.
For upcoming changes, what is the best way to be notified? I just created this Developper account, so I guess from now on, we should receive an email for the upcomming changes.
Again, thank for your help
Sylvain