Replies: 2 comments
-
|
Hello, The domain is invalid, you use And some keys are missing:
Some values should also be updated:
The OAuth 2.1 is describe here: Scope are listed here: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Example code for JavaScript: I am developing Kick-Alert.com application. You can check my streams live on kick.com @keremslmz. Call back : |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am experiencing an issue while trying to obtain a User Access Token using the OAuth 2.0 authorization flow. When I attempt to authorize via the following URL:
https://kick.com/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=http://127.0.0.1:5000/callback&scope=channel:manage
I am redirected to the homepage instead of being granted access or redirected to my callback URL.
Steps to reproduce:
Go to OAuth URL.
I am redirected to the homepage, not to the callback URL as expected.
Expected Result: The OAuth flow should authorize the application and redirect to the provided callback URL with an authorization code.
Actual Result: I am redirected to the homepage instead of the expected callback.
Additional Information:
The OAuth flow doesn't seem to work as expected.
The authorization URL appears correct, but I keep getting redirected to the homepage without obtaining the User Access Token.
I have followed the documentation and made sure that my client ID and redirect URI are correct.
Please let me know if there's any additional information you need.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions