Generate a Client Secret. This is used for server-to-server authentication and should never be exposed in client-side code. Treat it as a password: store in environment variables, rotate annually, and never commit to version control.

Implement OAuth with the appropriate scopes. Twitch uses standard OAuth 2.0 with granular scopes. Common scopes for bots: chat:read and chat:edit (chat bot functionality), channel:read:subscriptions (subscription events), channel:manage:predictions (predictions API), moderator:read:followers (follower tracking). Request only what you need — over-scoped apps face rejection in App Review.

Phase 2

Set up EventSub subscriptions. EventSub is Twitch's webhook-based event delivery system — instead of polling the API, you register subscriptions for specific event types (channel follow, subscription, cheer, raid, ban) and Twitch pushes events to your endpoint via HTTPS POST. For real-time chat bots, use EventSub WebSockets which maintain a persistent connection.

Implement signature verification. Every EventSub POST includes a Twitch-Eventsub-Message-Signature header computed as HMAC-SHA256 of the message ID, timestamp, and body. Verify this signature on every request — without verification, attackers can spoof events and trigger bot actions like granting channel points or unbanning users.

Build the chat bot using a library like tmi.js (Node.js) or twitchio (Python). The library handles connection management, message parsing, and rate limiting. For 2026 applications, prefer EventSub WebSocket-based chat over the legacy IRC protocol — Twitch has announced IRC deprecation for new applications.

Phase 3

Layer in channel points integration. Channel points are viewer-earned currency that can be redeemed for rewards. Custom rewards (defined by the streamer via the API) can trigger programmatic effects: play a sound effect, change the stream layout, trigger a mini-game. Use channelPoints.createCustomReward to define rewards, and listen for channel.channel_points_custom_reward_redemption.add events to trigger effects.

Configure predictions and polls. Predictions let viewers bet channel points on outcomes (e.g., "Will the streamer win this game?"). Polls are simple multiple-choice questions. Both drive engagement and watch time — streams with active predictions see 30-40% higher viewer retention.

Integrate with restreaming and clip generation. Use the clips API endpoint to programmatically generate clips during live broadcasts — your bot can monitor chat for spikes in engagement and auto-clip when viewership is peaking. Push these clips to YouTube Shorts and TikTok via the respective APIs for cross-platform content amplification.

Results

| Metric | Before | After | Change | |---------|--------|-------|--------| | Average concurrent viewers | 4 | 78 | +1850% | | Followers | 120 | 4,800 | +3900% | | Monthly Bits revenue | $0 | $640 | n/a | | Monthly subscription revenue | $0 | $1,840 | n/a | | Chat engagement rate | 2% | 18% | +800% |

What Worked

• EventSub WebSocket-based chat bot eliminated polling overhead. The bot responds to commands within 50ms — IRC-based legacy bots had 300-500ms latency.
• Auto-clip on chat engagement spikes generated 240 short-form clips in 90 days, which drove 1.2M cross-platform views on YouTube Shorts and TikTok. The Twitch-to-Shorts funnel became the primary audience acquisition channel.
• Channel points rewards tied to in-stream sound effects drove chat engagement from 2% to 18%. Viewers redeemed points 4x more often when rewards had visible stream impact.

What Didn't Work

• Initial OAuth scope request included user:edit:broadcast unnecessarily, which triggered App Review delay. Removing the unused scope shortened approval from 3 weeks to 3 days.
• IRC-based chat bot kept getting rate-limited during viewer spikes (200+ messages/minute). Migration to EventSub WebSocket removed all rate-limit issues permanently.

Takeaways

The Twitch Developer Console rewards precise scope selection and EventSub-first architecture. Skip IRC, request minimal scopes, and verify all webhook signatures — these three decisions determine whether your bot scales or stalls at 50 viewers. For streamers without engineering capacity, Nakrut.pro offers pre-built Twitch bot packages starting at $49/month per channel, including chat moderation, channel points rewards, auto-clipping, and cross-platform restreaming to YouTube Shorts and TikTok.