# Twitch Webhooks

Twitch delivers events through EventSub over the webhook transport. Twitch
does not follow the Standard Webhooks spec — it has its own signature scheme
and a three-way message-type protocol you must handle.

## When to Use This Skill

* How do I receive Twitch EventSub webhooks?
* How do I verify Twitch webhook signatures?
* How do I respond to the `webhook_callback_verification` challenge?
* How do I handle `stream.online`, `channel.follow`, or `channel.subscribe` events?
* Why is my Twitch webhook signature verification failing?

## Verification (core)

Twitch signs an HMAC-SHA256 over the concatenation of the
`Twitch-Eventsub-Message-Id` header, the `Twitch-Eventsub-Message-Timestamp`
header, and the raw request body (in that order). The digest is sent in
`Twitch-Eventsub-Message-Signature` as `sha256=<hex>`. There is no SDK for the
webhook transport, so verify manually. Use the raw body and compare
timing-safe.

Node:

```javascript
const crypto = require('crypto');

function verifyTwitchSignature(messageId, timestamp, rawBody, signatureHeader, secret) {
  if (!messageId || !timestamp || !signatureHeader) return false;
  const hmac = crypto.createHmac('sha256', secret);
  hmac.update(messageId);
  hmac.update(timestamp);
  hmac.update(rawBody); // string or Buffer of the raw body
  const expected = 'sha256=' + hmac.digest('hex');
  try {
    return crypto.timingSafeEqual(Buffer.from(signatureHeader), Buffer.from(expected));
  } catch {
    return false;
  }
}

```

Python:

```python
import hmac, hashlib

def verify_twitch_signature(message_id, timestamp, raw_body, signature_header, secret):
    if not (message_id and timestamp and signature_header):
        return False
    message = message_id.encode() + timestamp.encode() + raw_body  # raw_body is bytes
    expected = "sha256=" + hmac.new(secret.encode(), message, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, signature_header)

```

## Message Types

Read `Twitch-Eventsub-Message-Type` and branch. Verify the signature first for
all three types.

| `Twitch-Eventsub-Message-Type` | Respond with |
| --- | --- |
| `webhook_callback_verification` | HTTP 200, body = the raw `challenge` string from the payload, `Content-Type: text/plain` (do not JSON-wrap it) |
| `notification` | HTTP 2XX after processing `payload.event` |
| `revocation` | HTTP 2XX; log `payload.subscription.status` |

Revocation reasons: `user_removed`, `authorization_revoked`,
`notification_failures_exceeded`, `version_removed`.

> For complete handlers with route wiring, event dispatch, and tests, see:
> 
> * [examples/express/](https://github.com/hookdeck/webhook-skills/tree/main/skills/twitch-webhooks/examples/express/)
> * [examples/nextjs/](https://github.com/hookdeck/webhook-skills/tree/main/skills/twitch-webhooks/examples/nextjs/)
> * [examples/fastapi/](https://github.com/hookdeck/webhook-skills/tree/main/skills/twitch-webhooks/examples/fastapi/)

## Common Event Types

| Subscription type | Version | Triggered when |
| --- | --- | --- |
| `stream.online` | 1 | Broadcaster starts a stream |
| `stream.offline` | 1 | Broadcaster stops a stream |
| `channel.follow` | 2 | A channel receives a follow (needs `moderator_user_id`) |
| `channel.update` | 2 | Broadcaster updates title, category, or labels |
| `channel.subscribe` | 1 | A user subscribes to a channel |
| `channel.subscription.gift` | 1 | A user gifts subscriptions |
| `channel.cheer` | 1 | A user cheers with Bits |
| `channel.raid` | 1 | A broadcaster raids another channel |
| `channel.ban` | 1 | A viewer is banned |
| `channel.channel_points_custom_reward_redemption.add` | 1 | A custom channel-points reward is redeemed |

> For the full event reference, see [Twitch EventSub Subscription Types](https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/).

## Important Headers

| Header | Description |
| --- | --- |
| `Twitch-Eventsub-Message-Id` | Unique message ID (use to dedupe; part of the signed message) |
| `Twitch-Eventsub-Message-Timestamp` | RFC3339 send time (part of the signed message; reject if older than 10 min) |
| `Twitch-Eventsub-Message-Signature` | `sha256=<hex>` HMAC signature |
| `Twitch-Eventsub-Message-Type` | `notification`, `webhook_callback_verification`, or `revocation` |
| `Twitch-Eventsub-Message-Retry` | Retry attempt number (>0 means a redelivery) |
| `Twitch-Eventsub-Subscription-Type` | Event type, e.g. `stream.online` |
| `Twitch-Eventsub-Subscription-Version` | Subscription version, e.g. `1` or `2` |

## Environment Variables

```bash
# The secret you set (10-100 ASCII chars) when creating the subscription via
# POST /helix/eventsub/subscriptions. It is NOT shown in a dashboard.
TWITCH_WEBHOOK_SECRET=your_eventsub_secret_here

```

## Gotchas

* Verify the raw body, not re-serialized JSON — re-serializing changes bytes and breaks the HMAC.
* The subscription secret is set per subscription when you create it via the API with an app access token. User tokens are rejected for the webhook transport.
* The callback must be HTTPS on port 443.
* Respond within a few seconds or Twitch revokes the subscription after repeated failures.
* Delivery is at-least-once — dedupe on `Twitch-Eventsub-Message-Id` and reject timestamps older than 10 minutes.
* `channel.follow` requires version 2 with a `moderator_user_id` condition; `channel.update` is version 2.

## Local Development

```bash
# Start tunnel (no account needed)
npx hookdeck-cli listen 3000 twitch --path /webhooks/twitch

```

## Reference Materials

* [references/overview.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/twitch-webhooks/references/overview.md) - Twitch EventSub webhook concepts and events
* [references/setup.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/twitch-webhooks/references/setup.md) - Creating subscriptions and the signing secret
* [references/verification.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/twitch-webhooks/references/verification.md) - Signature verification details and gotchas