StreamHub partners (OBS plugins, analytics dashboards, clip bots) register webhook URLs. When a stream goes live or a clip is created, StreamHub POSTs a signed JSON payload to each registered endpoint — with retries, backoff, and dead-letter handling when partners are down.
Webhooks vs polling
| Aspect | Webhooks (push) | Polling (pull) |
|---|---|---|
| Latency | Near real-time delivery | Bounded by poll interval |
| Efficiency | Events sent only when they happen | Empty polls waste bandwidth |
| Complexity | Retry, signing, idempotency on sender | Simple client loop |
| Partner downtime | Missed deliveries without retry/DLQ | Partner catches up on next poll |
| StreamHub default | Primary for registered integrations | Fallback + public API sync |
Latency
Webhooks (push)Near real-time deliveryPolling (pull)Bounded by poll intervalEfficiency
Webhooks (push)Events sent only when they happenPolling (pull)Empty polls waste bandwidthComplexity
Webhooks (push)Retry, signing, idempotency on senderPolling (pull)Simple client loopPartner downtime
Webhooks (push)Missed deliveries without retry/DLQPolling (pull)Partner catches up on next pollStreamHub default
Webhooks (push)Primary for registered integrationsPolling (pull)Fallback + public API sync
Webhook delivery architecture
Webhook delivery architecture
Delivery pipeline
- Event trigger: Internal event (stream.started) enters webhook dispatch queue.
- Subscription lookup: Find all registered endpoints for this event type + streamer.
- Delivery worker: HTTP POST with signed payload, timeout, and retry policy.
- Delivery log: Record attempt, status code, latency for partner debugging.
- DLQ: After max retries, park failed deliveries for manual replay.
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 3 sections
- Payload and security
- Retry strategy
- Partner best practices
Test yourself
Answer these before moving on — recall is what makes it stick.