Skip to main content
Register an application in the Twitch developer console and put its keys in your environment so your own instance can connect the channel.
1

Register an app in the Twitch developer console

Sign in to the Twitch developer console and register a new application. You need the client id and the client secret from it, and the redirect URL from the next step.She asks for three scopes:
The third one is the one the announcement mode needs. Grant all three at registration, because adding a scope later means reconnecting the channel.
2

Configure the OAuth2 Redirect URI

Your Twitch OAuth2 Redirect URI:
  • Production: https://postqueen.example.com/integrations/social/twitch
  • Local development: http://localhost:4200/integrations/social/twitch
  • Docker: http://localhost:4007/integrations/social/twitch
3

Set environment variables

Copy both values into your .env file.
The client id stays in use long after the connection is made. She sends it as the Client-Id header on every Twitch API call, so a channel that connected fine will still stop working if you clear that variable later.
4

Add the Twitch channel

Restart PostQueen so the new variables are read. With Docker Compose, run docker compose down and then docker compose up.In the web interface click Add Channel and pick Twitch, then authorize on the Twitch side.Add Channel does not check whether the two variables are set, so a missing key shows up as a broken authorization page on the Twitch side rather than a helpful message in PostQueen.
The channel is in the left sidebar with its avatar and name. That is the whole confirmation: if it is in the list, she can post to it.

​
Next steps

What she can post to Twitch

Limits, post types and settings

Configuration reference

Every variable she reads

Connect errors

Invalid state, invalid_grant and the rest

Another channel

Every network, and what each one asks for