OAuth AppAccessToken seemingly not getting automatically added to request headers. about helix HOT 7 CLOSED

@pyorot hey man, you have to add the token to the twitch obj,it’s all well fetching one but you also need to use either a app access or user token, when declaring the twitch helix obj, or update the options in some way or form

from helix.

Do you have a worked example? I was just following this one; I define the helix object using client ID and client secret.

from helix.

I just found out that this library has not been sending the Bearer token. I found out because resp.GetRateLimit() returned 30 instead of 800.

It seems a lot of oauth code has been re-written instead of using the official oauth2 package, so it doesn't quite behave the same as other packages. I wonder what happens when the app token expires?

Got it to work using this:

ops := &helix.Options{
	ClientID:     config.Config.TwitchClientID.Get(),
	ClientSecret: config.Config.TwitchClientSecret.Get(),
}

client, err = helix.NewClient(ops)
token, err := client.GetAppAccessToken()
client.SetAppAccessToken(token.Data.AccessToken)

from helix.

Yeah, I also got it to work the same way, confirmed during the 2020/5/4 token requirement window. Leaving the issue open until issues #42, #44, and the usage example are updated accordingly.

from helix.

This is already documented here.

Please open a PR if you would like to add any further documentation.

from helix.

The authentication_docs.md usage example is missing the SetAppAccessToken() line. I don't fancy forking the repo just to correct that.

from helix.

I don't fancy forking the repo just to correct that.

Then stop wasting our time, and either write your own library or use another.

from helix.