Build and deploy a Twitch Extension with a configuration service and backend messaging

domain: gaming · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create the extension in the Twitch Developer Console (dev.twitch.tv/console), choosing its type (panel, overlay, or component) and generating its shared secret
  2. Implement the frontend using twitch-ext.min.js to receive the JWT-authenticated context and bootstrap configuration
  3. Use the Extension Configuration Service to store Developer, Broadcaster, and Global segments, keeping in mind that Global/Broadcaster segment data delivered to the frontend is effectively public and unauthenticated on read
  4. Send real-time updates to viewers with the Send Extension PubSub Message endpoint, authenticating backend calls with a JWT signed by the extension's shared secret using the 'external' role
  5. Respect the Extension PubSub limits of one message per second per channel and a 5 KB max payload per message
  6. Submit the extension for Twitch review before making it available to broadcasters, and rotate secrets carefully since an old secret only stays valid for about an hour after a new one is generated

Known gotchas

Related routes

Validate incoming JWTs on a Twitch Extension's EBS backend using the extension's shared secret
dev.twitch.tv · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans