Kick Setup and Authentication

Use the exact channel URL slug, then choose simple page capture or the richer WebSocket alert source.

Choose A Kick Source Mode

ModeBest ForSign-In
Standard Reading visible Kick chat from the normal or popout chat page. Usually not required for public chat capture. The page still must load and show chat.
WebSocket Structured chat plus official follow, subscription, reward, KICKs, moderation, and live-status events. Public chat can connect separately, but OAuth is required for official event subscriptions, sending chat, and channel/moderation controls.

Use The URL Slug, Not The Display Name

For https://kick.com/example-channel, the source value is example-channel. You may paste the full URL or enter only that slug.

Kick display names can differ from URL slugs. A display name may contain underscores while the URL uses hyphens. Copy the slug from the address bar instead of retyping the displayed name.

Desktop App Setup

  1. Select Add source → Kick.
  2. Paste the full Kick channel URL or enter its URL slug.
  3. Leave WebSocket selected for structured alerts. Kick currently defaults to WebSocket mode in the app.
  4. Select Activate source.
  5. In the Kick source window, select Sign in with Kick and approve the requested permissions.
  6. Keep the source window open and check the Channel, Chat socket, Bridge, and Subscriptions status chips.
Kick Alerts for Social Stream source showing channel status, chat socket, bridge, subscription status, authentication methods, and channel slug input
A fresh Kick WebSocket source before sign-in. In the desktop app, External browser is usually easiest when embedded login is blocked or a CAPTCHA appears.

Browser Extension WebSocket Setup

  1. Install and enable the current Social Stream Ninja extension.
  2. Open the Kick WebSocket source page.
  3. Replace example-channel with the channel's exact URL slug.
  4. Select Connect channel if the page has not connected automatically.
  5. Select Sign in with Kick to enable official event subscriptions and account controls.
  6. Keep the page open while streaming.
https://socialstream.ninja/sources/websocket/kick.html?channel=CHANNEL_SLUG

For Standard capture, open https://kick.com/CHANNEL_SLUG or its popout chat and leave chat visible.

What The Current Kick Login Requests

Permission GroupUsed For
User and channel readResolve the signed-in user, channel, category, and current channel information.
Channel writeUpdate stream title/category from Advanced Controls.
RewardsRead channel reward information and normalize reward redemptions.
Chat writeSend broadcaster or bot chat from the source.
Event subscriptionsSubscribe to official real-time Kick events.
ModerationBan/unban users and manage chat messages when the account has permission.
KICKsRead KICKs-related support information.

Kick's current OAuth flow uses authorization-code login with PKCE. Do not paste an access token, refresh token, client secret, or browser cookie into a guide, chat, or support ticket.

Official references: OAuth 2.1, scopes, and the Kick API reference.

Official Events The Current Source Subscribes To

  • Chat: chat.message.sent.
  • Follows: channel.followed → Social Stream new_follower.
  • Subscriptions: new, renewal, and gifts → new_subscriber, resub, and subscription_gift.
  • Rewards: channel.reward.redemption.updated → reward.
  • KICKs gifts: kicks.gifted → donation with the KICKs amount.
  • Moderation: moderation.banned.
  • Stream status: livestream.status.updated → stream_online or stream_offline.

Raid/host note: Kick's current official webhook list does not publish a raid/host event. Social Stream has compatibility handling if Kick exposes one through a connected feed, but a Kick raid alert should not be treated as guaranteed.

See Kick's current official webhook event list and Social Stream's Events and Alerts Compatibility guide.

Fix A Kick Source That Will Not Connect

  1. Copy the exact channel slug from the Kick URL.
  2. Check that Channel shows the intended slug and Chat socket changes from disconnected.
  3. If chat works but official alerts do not, sign in again and wait for Bridge and Subscriptions to connect.
  4. If embedded login or CAPTCHA fails, use External browser in the desktop app.
  5. Confirm the signed-in account owns or may moderate the channel before testing send/moderation controls.
  6. Check the Social Stream dock before debugging OBS. If the dock receives Kick data, the remaining problem is the overlay or OBS URL.