Webhook: the tool calls back when a video is ready
A webhook is an address on the caller's own server that a tool calls when a job changes state, so the result arrives without anyone asking for it. From 4 source pages, read 2026-09-25 to 2026-10-25; no maker pays to be listed.
Kling AI notifies a callback URL whenever a task's status changes and signs each request. Luma's callback receives status updates and the video. Replicate's webhooks deliver a finished prediction's metadata and output, and PixVerse reports each change in a task's status.
Video generation takes minutes, so a webhook saves a loop of requests that return nothing new.
It needs a public endpoint that can check the call is genuine; a signature, as Kling AI documents, is the usual check.
Webhooks also fail quietly. If the endpoint is down when the call comes, the result may be missed, so most pipelines keep a status check as a fallback.
Of the 28 tools in the register, 16 document a webhook or callback URL.
A callback URL set per request, as BytePlus's reference offers, suits pipelines that route different jobs to different handlers.
| Tool | Hook | What the documentation says |
|---|---|---|
| Kling AI | Webhooks | A callback URL notified when a task's status changes, with signed requests |
| Luma | Webhooks | A callback URL that receives status updates and the video |
| Replicate | Webhooks | Webhooks that deliver a finished prediction's metadata and output |
| PixVerse | Webhooks | A webhook that reports each change in a task's status |
Inclusion rule. Readings from the register used on this page. Order. The order the text takes them in.
1As the documentation puts it
the server will actively notify you when the task status changes
Kling AI, API documentation: callback protocol
It will get status updates (dreaming/completed/failed)
Luma, API documentation: Python video generation
Sending notifications when long-running predictions finish.
Replicate, documentation: webhooks
PixVerse can send task-status updates to your callback URL whenever the status of a video-generation task changes.
PixVerse, platform documentation: webhook callbacks
- Callback protocolA callback URL notified when a task's status changes, with signed requests
- CallbacksA callback URL that receives status updates and the video
- About webhooksWebhooks that deliver a finished prediction's metadata and output
- OverviewA webhook that reports each change in a task's status
2Where a drama generator fits
Read against “Webhook”, this is how SceneMixer describes the matching stage of its own pipeline:
Every character gets an AI-generated full-body reference sheet at analysis time. Face and body crops from that sheet are injected into every video segment that features the character, so the same face, hair, and signature look persist across all episodes.
SceneMixer, Turn a Novel into a Video Series with AI — “How does SceneMixer keep characters consistent across episodes?” (read 2026-10-13)
The shot seconds in the storyboard add up to the segment length, so editing them changes it.
SceneMixer, Fixing One Shot Without Redoing Everything — “Can I change the duration of a segment?” (read 2026-10-13)