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

[Dist]

@IdentityDev

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?

1. Anywhere that you’re making Twitch API requests will need to make changes.

2. A short-term solution is to change from v3 to v5. This can be done by either adding the Accept: application/vnd.twitchtv.v5+json header to the request, or api_version=5 as a querystring param for your requests to https://api.twitch.tv/kraken/user or any other Kraken endpoint.

Please keep in mind though that v5 is also deprecated, but has no removal date as of yet so should remain for the coming months ahead.

3. I don’t speak for Twitch, but honestly it is most likely no to postponing the complete shutdown. Twitch have sent numerous emails to developers over the last couple years, v3 has been completely removed from the docs for over a year, and the docs have also contained both migration info and deprecation warnings for a long time, so if you’re still using v3 then the fault lies with the maintainers of your software. Leaving it until less than a week before the complete shutdown is not good development practice.

It is also important that you update the URL’s used in any OAuth flow you may be using, as if you’re still using v3 endpoints it’s likely you’re using old OAuth URLs (these can be identified by having ‘Kraken’ in the path), and the new OAuth URLs should look like https://id.twitch.tv/oauth2/authorize for example. Please read the auth docs to see which URLs you need to change: Authentication | Twitch Developers this should just be a simple case of swapping out the old URLs for the new ones, the actual process/params haven’t changed.