Refresh Token API Documentation is Incorrect/Outdated

Refreshing Access Tokens | Twitch Developers documents the client_secret attribute as required which is not correct anymore. It is only required for confidential client types, not for public ones. Public clients using the recently introduced Device Code Grant Flow do not have a client_secret and do not need to provide it.

My tests confirm this, as I was able to exchange a refresh token of a public client for a new access token without including a client_secret attribute in the body of the request.

I was not able to provide this feedback on the documentation page itself, since Twitch forces users to enable cross-site tracking in their browser for that … but that is a different topic. I just mention it to explain why this report landed here instead.

Documentation issues can be filed on the github - Issues · twitchdev/issues · GitHub

I keep forgetting that repo exists, thank you!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.