Kling V2.6 Motion Control
kling-v2-6-motion-control
Action control video generation: Creating action control videos by using images and reference videos.
Endpoints
Section titled “Endpoints”POST /v1/queue/kling-v2-6-motion-control # Create taskGET /v1/queue/kling-v2-6-motion-control/requests/{request_id}/status # Check statusGET /v1/queue/kling-v2-6-motion-control/requests/{request_id}/response # Get resultPUT /v1/queue/kling-v2-6-motion-control/requests/{request_id}/cancel # Cancel taskRequest parameters
Section titled “Request parameters”curl --request 'POST' 'https://odirouter.ai/model/v1/queue/kling-v2-6-motion-control' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --header 'Content-Type: application/json' \ --location \ --data-raw '{ "image_url": "https://www.gstatic.com/webp/gallery/2.jpg", "video_url": "https://interactive-examples.mdn.mozilla.net/media/cc0-videos/flower.mp4", "character_orientation": "image", "mode": "std", "prompt": "A person dancing gracefully", "keep_original_sound": "yes"}'Reference image. The characters, backgrounds and other elements in the generated video are based on this reference image
Image content requirements:
Character proportions should match reference action proportions as much as possible; avoid using full-body actions to drive half-body characters
Character should show clear upper body or full body limbs and head, avoid occlusion
Avoid extreme orientations like handstands or lying flat; character should not occupy too small a portion of the frame
Supports realistic/stylized characters (including humans/humanoid animals/some pure animals/some characters with humanoid limb proportions)
Supports Base64 encoded image or image URL (ensure accessibility)
If using Base64, ensure all image data parameters are in Base64 encoding format. Do not add any prefix to the Base64 encoded string, such as data:image/png;base64,. The correct format should be the pure Base64 encoded string
Image requirements:
Format: .jpg, .jpeg, .png
File size: max 10MB
Dimensions: between 300px ~ 65536px
Aspect ratio: between 1:2.5 ~ 2.5:1
Reference video URL. The character actions in the generated video will match the reference video
Video content requirements:
Character should show clear upper body or full body with all limbs and head visible, avoid occlusion
Recommend uploading single-person action video; for 2+ people, the person occupying the largest portion will be used
Real human actions recommended; some stylized characters with humanoid limb proportions may work
Video should be continuous shot with character always in frame; avoid cuts and camera movements, otherwise video will be trimmed
Avoid overly fast movements; relatively smooth actions produce better results
Video requirements:
Format: .mp4, .mov
File size: max 100MB
Dimensions: both width and height between 340px ~ 3850px
Duration requirements:
Minimum: 3 seconds
Maximum depends on character_orientation:
When orientation matches video character: max 30 seconds
When orientation matches image character: max 10 seconds
Note: For difficult or fast actions, results may be shorter than uploaded video duration as the model only extracts valid action segments (minimum 3 seconds of continuous usable action). Credits consumed for such cases are non-refundable
Character orientation in the generated video, can match image or video
image: Match image character orientation; reference video duration max 10 seconds
video: Match video character orientation; reference video duration max 30 seconds
Options: image, video
Video generation mode
std: Standard mode, cost-effective
pro: Expert mode (high quality), higher performance mode with better video quality
Options: std, pro
Text prompt, can include positive and negative descriptions
Can be used to add elements or achieve camera movement effects in the video
Max 2500 characters
Whether to keep the original audio from the reference video
yes: Keep original audio
no: Discard original audio
Options: yes, no
Default: yes
Callback notification URL for task results. If configured, the server will actively notify when task status changes
Custom task ID
User-defined task ID that will not override the system-generated task ID but can be used for task queries
Must be unique within a single user account
Response parameters
Section titled “Response parameters”{ "request_id": "task_01hxyz...", "response_url": "https://odirouter.ai/model/v1/queue/kling-v2-6-motion-control/requests/task_01hxyz.../response", "status_url": "https://odirouter.ai/model/v1/queue/kling-v2-6-motion-control/requests/task_01hxyz.../status", "cancel_url": "https://odirouter.ai/model/v1/queue/kling-v2-6-motion-control/requests/task_01hxyz.../cancel", "queue_position": 0}| Field | Type | Description |
|---|---|---|
request_id | string | Task ID used for all follow-up operations. |
response_url | string | URL to fetch the final result. |
status_url | string | URL to query task status. |
cancel_url | string | URL to cancel the task. |
queue_position | int | Current queue position. |