Project webhooks

Tunnel projects now support webhooks for delivering lifecycle events to HTTPS endpoints.

This makes runtime tunnel state easier to connect to durable systems. A tunnel or client can be short-lived by design; with webhooks, applications can persist the lifecycle around it, update an inventory, react to labels, or clean up state when a published tunnel disappears.

The first event catalog covers client.created, client.deleted, tunnel.created, and tunnel.deleted. Connection logs and traffic summaries remain out of webhook delivery so high-volume observability data stays in logs and event inspection surfaces.

Webhook endpoints are available on Pro and Enterprise projects. The dashboard includes endpoint creation, event selection, signing secret rotation, delivery health charts, delivery filtering, request payload inspection, response details, and delivery attempt history.

The Control plane API and MCP expose the same split used in the dashboard: project events are the canonical lifecycle records, while webhook deliveries and attempts are the per-endpoint delivery diagnostics.

The rstream CLI also supports webhook-shaped local delivery starting with v1.21.0. rstream events --webhook can forward live project events to a local receiver with the same signed JSON body and headers used by configured webhook endpoints, which makes receiver development easier before registering a durable endpoint.

See Webhooks for payloads, signatures, retries, permissions, and delivery inspection.