-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth AppAccessToken seemingly not getting automatically added to request headers. #45
Comments
@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 |
Do you have a worked example? I was just following this one; I define the helix object using client ID and client secret. |
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:
|
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. |
This is already documented here. Please open a PR if you would like to add any further documentation. |
The authentication_docs.md usage example is missing the |
Then stop wasting our time, and either write your own library or use another. |
(Reposting because may be urgent). Hey, this doesn't seem to work as you say. I have this code:
and my program output
during the migration test window that just ended (is back to normal now). Any ideas?
Originally posted by @pyorot in #42 (comment)
The text was updated successfully, but these errors were encountered: