Extend a Kling video
Extend Kling-generated videos via POST /kling/v1/videos/video-extend using task_id and video_id; run as a sub-task on the parent account.
Before you call it
- Start from a finished Kling video result
- Pass the
video_idfrom the parent task result - Pass the parent
task_idtogether with thevideo_id - Use a source video that is extension-compatible; unsupported source videos return HTTP 400 instead of creating an extension task
- A completed 5 s Kling v1 or v1-6 text-to-video or image-to-video parent is a safer starting point for extension compatibility
- Add
prompt,negative_prompt, orcfg_scaleonly when you need to steer the continuation - Run the extension on the same account context as the parent task
- Trigger the extension promptly before parent-task resources expire
Task flow
Finish the parent video task
Submit the extension request
task_id, video_id, and optional prompt, then save the returned task id.Poll the extension task
Authorizations
Bearer token authentication. Use your CometAPI key.
Body
Parent Kling task id for the extension-compatible video being extended.
Video id from a parent task result. The source video must be extension-compatible; unsupported videos return HTTP 400.
Text prompt describing the desired motion for the extended segment. Maximum 500 characters.
Webhook URL to receive task status updates when the task completes.
Elements to avoid in the extension.
Prompt adherence strength for the extension. Range: 0-1.