You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 20, 2024. It is now read-only.
The first step to getting an access token is to register your application (this includes Twitch Extensions and chatbots). To register an application:
Log in to the developer console using your Twitch account. If you don’t have an account, select the Sign Up tab to create one.
When you sign up for an account, Twitch sends you an email to verify your account. Be sure to open the email and verify your account before proceeding.
You must also enable two-factor authentication (2FA) for your account. To enable 2FA, navigate to Security and Privacy, and follow the steps for enabling 2FA under the Security section.
You’ll need to refresh your console for these changes to take effect.
Select the Applications tab on the developer console and then click Register Your Application.
Set Name to your application’s name. The name must be unique among all Twitch applications. Your app’s name is listed on the Connections page under Other Connections if your app requires user consent to access or modify the user’s resources.
Set OAuth Redirect URLs to the callback URL that your app uses for authorizations. After adding your redirect URL, click Add. you can add http://localhost:3000
Select a Category (type of application) that your app belongs to.
Click the I’m not a robot checkbox.
Click Create.
Back in the Applications tab, locate your app under Developer Applications, and click Manage.
Note your Client ID, which you’ll use to get your access token and to set the Client-Id header in all API requests. Client IDs are considered public and can be embedded in a web page’s source.
Depending on the flow you use to get a token, you may need a client secret. For example, the Authorization Code Grant Flow requires a client secret. Click New Secret to generate a secret that you’ll use to get your access token. You must copy the secret and store it somewhere safe. Getting a new secret invalidates the previous secret, which might make your API requests fail until you update your app.
documentationImprovements or additions to documentation
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Set Name to your application’s name. The name must be unique among all Twitch applications. Your app’s name is listed on the Connections page under Other Connections if your app requires user consent to access or modify the user’s resources.
Set OAuth Redirect URLs to the callback URL that your app uses for authorizations. After adding your redirect URL, click Add. you can add http://localhost:3000
Select a Category (type of application) that your app belongs to.
Click the I’m not a robot checkbox.
Click Create.
Note your Client ID, which you’ll use to get your access token and to set the Client-Id header in all API requests. Client IDs are considered public and can be embedded in a web page’s source.
Depending on the flow you use to get a token, you may need a client secret. For example, the Authorization Code Grant Flow requires a client secret. Click New Secret to generate a secret that you’ll use to get your access token. You must copy the secret and store it somewhere safe. Getting a new secret invalidates the previous secret, which might make your API requests fail until you update your app.
Now we need to generate chatbot oauth token, visit Twitch Chat OAuth Password Generator
Click Connect
Finished, you can now run
botway tokens set --twitch BOT_NAME
Beta Was this translation helpful? Give feedback.
All reactions