Skip to content

Twitch Developer Application

alsi-lawr edited this page Jul 17, 2026 · 2 revisions

Configure a Twitch developer application

BlokeBot uses one Twitch developer application for dashboard sign-in, the host bot, and hosted-channel authorization. Create and configure it before starting the live Twitch runtime.

Register the application

  1. Sign in to the Twitch Developer Console with the account that will own the application. Twitch requires a verified account with two-factor authentication enabled.

  2. Open Applications, then choose Register Your Application.

  3. Give the application a unique name and choose the category that best describes it.

  4. Add each OAuth redirect URL below, replacing https://bot.example.com with the public HTTPS address of this BlokeBot server:

    https://bot.example.com/auth/twitch/callback
    https://bot.example.com/oauth/callback
    https://bot.example.com/oauth/channel-bot/callback
    

    Add every URL individually before creating the application. They must match exactly, including the scheme, host, port when present, and path.

  5. Complete Twitch's verification and create the application.

  6. In Developer Applications, choose Manage for the new application. Copy its Client ID. Choose New Secret, copy the generated secret immediately, and store it as a private server secret. Generating a replacement invalidates the old secret.

Twitch's Register your app guide is the provider reference for these console steps.

Configure BlokeBot

Put the client ID and secret under TwitchBot:Identity; do not put them under TwitchWebAuth.

{
  "TwitchBot": {
    "Identity": {
      "BotUsername": "your-bot-login",
      "ClientId": "your-client-id",
      "ClientSecret": "your-client-secret",
      "RedirectUri": "https://bot.example.com/oauth/callback"
    }
  }
}

RedirectUri must be the second URL registered above. Keep the configuration file, token cache, and database on private durable storage; see State and secrets and Configuration sources for how to provide them to the server.

Why all three callback URLs are needed

Callback Used for
/auth/twitch/callback Dashboard sign-in
/oauth/callback Connecting the host bot account
/oauth/channel-bot/callback Authorizing a hosted channel's bot access

BlokeBot requests the required permissions during the relevant Twitch consent flow. The shipped identity and hosted-channel scopes are listed in Twitch identity and OAuth; there is no separate scope list to enter in the Twitch developer console.

Clone this wiki locally