Twilio video-insights webhook events
Twilio sends 5 video-insights events, including com.twilio.video.insights.room-summary.complete, com.twilio.video.insights.participant-summary.complete and com.twilio.video.insights.track-summary.complete.
Twilio has two systems that send you webhooks. Messaging, Voice and other products call a URL you set on a number or resource, with form parameters and no event type field. Event Streams sends JSON CloudEvents with a type. The events list names Event Streams types and Conversations (classic) actions, because a status callback has no event name to list. SendGrid's email events are separate: see SendGrid webhooks.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
com.twilio.video.insights.room-summary.complete
documented from Twilio docs (example)
com.twilio.video.insights.room-summary.complete Final summary of a video room is ready
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource video-insights
{
"specversion": "1.0",
"type": "com.twilio.video.insights.room-summary.complete",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/VideoInsights.RoomSummaryApi/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.video.insights.room-summary.complete |
Full schema: 38 fields.
From Twilio docs
-
Content type
application/json
com.twilio.video.insights.participant-summary.complete
documented from Twilio docs (example)
com.twilio.video.insights.participant-summary.complete Final summary of a video participant is ready
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource video-insights
{
"specversion": "1.0",
"type": "com.twilio.video.insights.participant-summary.complete",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/VideoInsights.ParticipantSummaryApi/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.video.insights.participant-summary.complete |
Full schema: 58 fields.
From Twilio docs
-
Content type
application/json
com.twilio.video.insights.track-summary.complete
documented from Twilio docs (example)
com.twilio.video.insights.track-summary.complete Final summary of a video track is ready
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource video-insights
{
"specversion": "1.0",
"type": "com.twilio.video.insights.track-summary.complete",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/VideoInsights.TrackSummaryApi/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.video.insights.track-summary.complete |
Full schema: 93 fields.
From Twilio docs
-
Content type
application/json
com.twilio.video.insights.log-analyzer.room-summary
documented from Twilio docs (example)
com.twilio.video.insights.log-analyzer.room-summary Log Analyzer produces a video room summary
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource video-insights
{
"specversion": "1.0",
"type": "com.twilio.video.insights.log-analyzer.room-summary",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/VideoInsights.VideoLogAnalyzerRoomSummary/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.video.insights.log-analyzer.room-summary |
Full schema: 33 fields.
From Twilio docs
-
Content type
application/json
com.twilio.video.insights.log-analyzer.participant-summary
documented from Twilio docs (example)
com.twilio.video.insights.log-analyzer.participant-summary Log Analyzer produces a video participant summary
Identified by type in each CloudEvent on Event Streams; none on classic callbacks
Resource video-insights
{
"specversion": "1.0",
"type": "com.twilio.video.insights.log-analyzer.participant-summary",
"source": "AB00000000000000000000000001",
"id": "NO00000000000000000000000001",
"dataschema": "https://events-schemas.twilio.com/VideoInsights.VideoLogAnalyzerParticipantSummary/2",
"datacontenttype": "2025-10-08T07:17:02.363Z",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | NO00000000000000000000000001 |
type | string | com.twilio.video.insights.log-analyzer.participant-summary |
Full schema: 46 fields.
From Twilio docs
-
Content type
application/json
Route Twilio events by type.
Event Gateway receives every Twilio delivery and filters and routes it by event type, so each service gets only the events it handles.