Motion Control
Create Task
Request Header
Data Exchange Format
Authentication information, refer to API authentication
Request Body
Model Name
Text prompt, can include positive and negative descriptions
- Can add elements to the scene, achieve camera movement effects, etc. See Kling "Motion Control" User Guide
- Cannot exceed 2500 characters
Reference image. Characters, background and other elements in generated video will follow this reference.
- Video content requirements:
- Character proportions should match the reference motion as much as possible; avoid driving half-body characters with full-body motions
- Character should show clear upper body or full body including limbs and head, avoid occlusion
- Avoid extreme orientations (upside down, lying flat, etc.). Character should occupy sufficient screen area
- Supports realistic/stylized characters (including humans/humanoid animals/some pure animals/some humanoid body proportion characters)
- Supports image Base64 encoding or image URL (ensure accessibility)
- Important: When using Base64, do NOT add any prefix like
data:image/png;base64,. Submit only the raw Base64 string.
- Correct Base64 format:
- Incorrect Base64 format (with data: prefix):
- Supported image formats: .jpg / .jpeg / .png
- File size: ≤10MB, dimensions: 300px ~ 65536px, aspect ratio: 1:2.5 ~ 2.5:1
URL of reference video. Character actions in generated video will follow this reference.
- Video content requirements:
- Character should show clear upper body or full body including all limbs and head, avoid occlusion
- Recommend uploading single-person action video; for 2+ people, actions will be taken from the character with largest screen proportion
- Recommend using real person actions; some stylized characters/humanoid body proportions may work
- Video should be single continuous shot with character always visible, avoid cuts or camera movements (will be truncated otherwise)
- Avoid overly fast actions; relatively stable actions produce better results
- Supported formats: .mp4 / .mov, file size: ≤100MB, dimensions: 340px ~ 3850px. Validation failures will return error codes.
- Duration limits: minimum 3 seconds, maximum depends on character_orientation:
- When character_orientation is "video": maximum 30 seconds
- When character_orientation is "image": maximum 10 seconds
- The duration range of the uploaded motion reference is from 3 to 30 seconds, in which the generated video length will align with the duration of the uploaded video. If motions are complex or fast-paced, there is a chance that the output may be shorter than the uploaded video duration, as the model can only extract the valid action duration for generation. The minimum extractable continuous action duration is 3 seconds. Please note that in such cases, the consumed credits cannot be refunded. It is recommended to adjust the complexity and speed of the actions accordingly.
- System will validate video content and return error codes if issues are found
Reference Element List based on element ID configuration
- Load with key:value format as follows:
- When referencing the element, the generated video can only temporarily refer to the orientation of the person in the video.
- Currently, only one element can be introduced.
Element ID from element library
Whether to keep the original sound of the video
Character orientation in generated video, can match image or video
- image: Match character orientation in the image; reference video duration must not exceed 10 seconds
- video: Match character orientation in the video; reference video duration must not exceed 30 seconds
- When referencing the element, the generated video can only temporarily refer to the orientation of the person in the video.
Video generation mode
- std: Standard Mode - basic mode, cost-effective
- pro: Professional Mode (High Quality) - high performance mode, better video quality
Support varies by model version and video mode. See Capability Map for details.
Whether to generate watermarked results simultaneously
- Defined by the enabled parameter, format:
- true: generate watermarked result, false: do not generate
- Custom watermarks are not currently supported
Callback notification URL for task result. If configured, server will notify when task status changes.
- For specific message schema, see Callback Protocol
Customized Task ID
- Will not overwrite system-generated task ID, but supports querying task by this ID
- Must be unique within a single user account
Query Task (Single)
Request Header
Data Exchange Format
Authentication information, refer to API authentication
Path Parameters
Task ID for Motion Control. Fill the value directly in the request path. Choose either task_id or external_task_id for querying.
Customized Task ID for Motion Control. Fill the value directly in the request path. Choose either task_id or external_task_id for querying.
Query Task (List)
Request Header
Data Exchange Format
Authentication information, refer to API authentication
Query Parameters
Page number
- Value range: [1, 1000]
Data volume per page
- Value range: [1, 500]