Capture Event
Meetings
Capture Event
The vendor’s event stream: bot lifecycle, recording, transcript.
Same three rules as every handler in this file: verify first (Svix signature, refused outright when no secret is configured); 202 for anything past verification that cannot be placed — an unknown bot id is expected, not exceptional; and no synchronous downstream work — the status write is one RPC, and the transcription request and ingest both happen in the workflow the signal wakes.
POST
Capture Event
Response
200 - application/json
Successful Response