Skip to main content
POST
Submit Kling 3.0 Motion Control Task
  1. After submission, a task_id will be returned. If you provided a callback_url, when the task status becomes finished or failed, a POST request will be sent to the callback_url.
  2. Regardless of whether callback_url is provided, you can retrieve the result through the unified Query Task Status endpoint.
kling-3.0-motion-control combines one reference image and one reference video to transfer motion to the target character.

Models

  • kling-3.0-motion-control - Motion transfer from reference video to reference image

Required parameters

  • image_urls: Exactly 1 reference image
  • video_urls: Exactly 1 reference video
  • character_orientation: image or video

Optional parameters

  • prompt: Optional scene prompt
  • resolution: 720p or 1080p. Default is 720p
  • kling_elements: Optional facial consistency element. Only available when character_orientation=video

Notes

  • Images support .jpg, .jpeg, .png, up to 10MB
  • Videos support .mp4, .mov, up to 100MB
  • Reference video must be at least 3 seconds
  • When character_orientation=image, the reference video must not exceed 10 seconds
  • When character_orientation=video, the reference video must not exceed 30 seconds
  • kling_elements supports only 1 facial element. Each element requires frontal_image_url and reference_image_urls with 1 to 3 images
  • When using kling_elements, reference the element in your prompt as @Element1

Authorizations

Authorization
string
header
required

All API endpoints require Bearer Token authentication.

Create an API key: sign in to PoYo, open Dashboard → API Key at poyo.ai/dashboard/api-key, and click to create a key.

Add it to the request header:

Body

application/json
model
enum<string>
required

Kling 3.0 Motion Control model identifier

Available options:
kling-3.0-motion-control
input
object
required
callback_url
string<uri>

Webhook callback URL for result notifications

Example:

"https://your-domain.com/callback"

Response

Task submitted successfully

code
enum<integer>
required

Business status code. 200 means success; any other value means the request failed. Always check this field: some validation errors return HTTP 200 with code: 400 in the body.

  • 200: Success
  • 400: Invalid request parameters
  • 401: Missing or invalid API key
  • 402: Insufficient credits
  • 403: Permission denied
  • 404: Resource not found
  • 408: Request timeout
  • 429: Rate limit exceeded
  • 500: Internal server error
  • 502: Upstream service error
  • 503: Service unavailable

See Error Codes for details.

Available options:
200,
400,
401,
402,
403,
404,
408,
429,
500,
502,
503
Example:

200

data
object
required