webhooks
Livekit Egress Webhook
Receive LiveKit egress lifecycle events and reflect them onto the corresponding session row.
LiveKit's webhooks carry a signed JWT in the Authorization header. The WebhookReceiver from livekit.api verifies it against our api secret and parses the body — never trust the payload before that runs.
Events we handle:
- egress_started → status='active'
- egress_updated → status='active' (no-op if already active)
- egress_ended → status='completed' on EGRESS_COMPLETE, status='failed' on EGRESS_FAILED/ABORTED
Unknown events are 200-OK'd silently — LiveKit retries on non-2xx and we don't want to enter a retry loop over an event we don't model yet.
post/v1/webhooks/livekit/egress
Response
Successful Response
{"stackTrail":"paths:/v1/webhooks/livekit/egress:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}
Changes
No recorded changes to this endpoint across all 1 revision of this API.