Submit Task (Kling Format)
Consistent with the Kling official API: text-to-video and image-to-video use separate endpoints, and the omni models kling-video-v3-omni / kling-video-o1 use the same pair of endpoints (the gateway routes omni requests automatically by model; query and billing stay unchanged). The motion-control models kling-video-motion-control-v3.0 / v2.6 also enter through the same endpoints (see Motion Control). Fields such as image_tail / negative_prompt / resolution work both at the top level and inside metadata. Kling-official-only fields such as cfg_scale / camera_control / static_mask / dynamic_masks are not supported upstream and are ignored.
Endpoints
- Text-to-video:
POST /kling/v1/videos/text2video - Image-to-video:
POST /kling/v1/videos/image2video
Besides the Kling format, you can also use the generic endpoint POST /v1/video/generations (OpenAI style, see Create Video Task) and POST /v1/responses (Responses format; the artifact is rendered as a <video> tag).
Request Body
Before submission the gateway validates resolution / duration / audio / multi_shot per model. Invalid values get an immediate 400 with the allowed values in the message — just fix them as instructed. This protects your balance: the upstream does not reject these parameters, it silently falls back to defaults and still charges.
Model × Parameter Matrix
Additional constraints (verified upstream): first + last frame on v2.5 / v2.6 only supports 1080p (auto-adjusted); at most 3 elements (v3 / v3-omni / o1) and 2 voices; see Elements & Voices for creating and referencing assets.
Request Example
Legacy code keeps working unchanged: the legacy mode (std / pro), native settings object, and metadata.image_tail / metadata.negative_prompt tunnels all behave as before. Two differences: mode: "mock" is no longer available (returns 400; for zero-cost testing use the platform's self-use mode), and invalid parameter combinations now return 400 instead of being silently dropped (preventing silent default-tier charges). Legacy details: Legacy Guide (v2.5-turbo).
Response Body
A successful submission returns a task object; use data.task_id (also mirrored at the top level) for polling. task_status starts as submitted.
Response Example
For status polling and downloads see Query & Download.
