POST Webhook robots.job.generate_engagement_insights.processing
Payload
Example payload
{
"created_at": "2022-01-01T00:00:00.000000Z",
"attempts": [
{
"created_at": "2022-01-01T00:00:00.000000Z"
}
],
"data": {
"parameters": {
"asset_id": "mux_asset_123abc"
},
"resources": {
"assets": [
{
"id": "abc123asset",
"meta": {
"title": "My Video",
"creator_id": "user123",
"external_id": "ext456"
},
"_links": {
"self": {
"href": "/video/v1/assets/abc123asset"
}
}
}
]
},
"outputs": {
"moment_insights": [
{
"start_ms": 30000,
"end_ms": 60000,
"engagement_score": 0.89,
"insight": "Viewers are highly engaged during the product demo, with minimal drop-off."
}
],
"overall_insight": {
"summary": "Engagement peaks during hands-on demonstrations and drops during introductory segments.",
"trends": [
"Product demos drive the highest retention",
"Viewers skip past the first 15 seconds of intro"
]
}
}
}
}Response
Return a 200 to indicate that the data was received successfully
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.