Conduits are a wrapper transport type for server-side applications that simplify forwarding EventSub notifications. They utilize app access tokens and consist of shards (webhooks or websockets). Twitch handles load balancing by deciding which shard receives a notification; if a shard fails, Twitch retries with another.
Key constraints and behaviors:
- Limits: Maximum 5 enabled conduits per client, with up to 20,000 shards per conduit.
- Resilience: If a shard fails, only that shard is disabled. A conduit is only deleted by Twitch if all shards remain disabled for 72 hours.
- Reliability: Avoid having more than one disabled websocket shard at a time to prevent dropped notifications.
- Cost: The subscription cost model is identical to standard webhooks (default
max_total_cost is 10,000).