HTTP 410 on GET https://api.twitch.tv/kraken/user

Hello @Dist

Many thanks for your rapid answers. Unfortunatly, I was not aware of this change. It did not reached our team. I am working for Ubisoft and we integrate session validation in our backend using:

GET https://api.twitch.tv/kraken/user HTTP/1.1
Authorization: OAuth -the token obtained on the client app-
User-Agent: TwitchAgent
Host: api.twitch.tv

At the very moment I am not sure how difficult it is to migrate the what you call v5. But I would appreciate your hints.

1- Does it requires client changes?
2- It is manageable to change only our backend to change the way ve validate the token received from the client? If yes, how trivial it is? only an url change?
3- Since Ubisoft have important integration using Twitch, is there anyway to postpone the complete shutdown before we get ready?

Regards
Sylvain