Kling: Kling 4.0 Flash Omni Video API

Kling 4.0 Flash Omni Video: combine a first frame, reference images, reference videos, a video to edit and elements in one API to generate or edit videos — 720P up to 20 seconds, at a lower per-second rate than 4.0.

Frequently Asked Questions

Why does submission say my balance is insufficient when it covers one video?

On submission the gateway reserves the **most the request could cost**: without `settings.duration` the model may make a video of up to 20 seconds from the prompt, so 20 seconds is assumed, and attached videos are assumed at the input maximum. On completion you are charged the credits Kling actually deducted and the rest is returned. Setting `settings.duration` makes the reservation match the real cost.

Can I keep the result URLs long-term?

Kling deletes generated videos after **30 days**. If object storage is enabled on this site, the gateway re-hosts the result when the task succeeds (callbacks and the unified task API return the re-hosted URL); otherwise download and keep it yourself.

How long does a task take and how do I get the result?

Video generation is asynchronous and usually takes from tens of seconds to a few minutes. Set `options.callback_url` to get a push on every status change, or poll the query endpoint.

Kling 4.0 Flash or Kling 4.0?

Flash is the lightweight 4.0 with a lower per-second rate (0.6 credits per second without video input, versus 1.0 for 4.0 at 720P), suited to quick drafts, prompt testing and many variations. Choose Kling 4.0 for 1080P, videos longer than 20 seconds (4.0 goes up to 30), middle / last frames, or referencing voices directly in Omni Video.

How do I use my own elements?

Create them through Element Management (`POST /kling/v1/general/advanced-custom-elements`), then reference the `element_id` in `contents` with an `id` (e.g. `element_1`) that the prompt mentions as `@element_1`. Elements are shared with Kling 4.0. Elements created through this site are routed to the account that created them automatically; if custom elements in one request belong to different service nodes the request returns 400 — use elements created together. Elements created by other users of this site cannot be referenced.