AsyncAPI channel · Sendspark
· Sendspark Webhooks
{subscriberUrl}
Channel address
{subscriberUrl}
Parameters
subscriberUrl— The HTTPS endpoint registered on the webhook subscription.
Operations
receive
receiveVideoEvent
Messages
video_request_received
A dynamic video generation request was received.
Content-Type:
video_generated_dv
A dynamic video was generated.
Content-Type:
video_mp4_ready
The rendered MP4 is ready.
Content-Type:
video_generated_error
Video generation failed with an error.
Content-Type:
video_played
The viewer started playing the video.
Content-Type:
video_watched
The viewer watched the video.
Content-Type:
video_viewed
The video landing page was viewed.
Content-Type:
video_liked
The viewer liked the video.
Content-Type:
video_cta_clicked
The viewer clicked the call-to-action.
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.