Skip to main content
Create an OAuth application on Kick and put its keys in your environment so your own instance can connect the channel.
1

Create an OAuth app on Kick

Sign in to Kick and create an OAuth application. You need its client id and its secret, plus the redirect URI from the next step.She asks for three scopes, so grant all of them:
Kick uses OAuth 2.1, which means PKCE. She generates the code verifier and the S256 challenge for you, and the whole exchange runs against id.kick.com.
2

Configure the OAuth2 Redirect URI

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

Set environment variables

Copy the client id and the secret from your Kick app into your .env file.
The second variable is KICK_SECRET, not KICK_CLIENT_SECRET. Naming it the long way is the single most common reason a Kick connection fails on the first try.
4

Add the Kick 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 Kick. Kick asks you to authorize, and the channel appears once you accept.Add Channel does not check whether the two variables are set, so a missing or misspelled key shows up as a broken authorization page on the Kick 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 Kick

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