GPT Image 2.5 Flare & Sunburst are live on EvoLinkTry GPT Image 2.5

Kling 4.0 Flash API

Generate 3–20 second 720p clips with Kling 4.0 Flash (Kling 4 Flash) through EvoLink's unified API. Choose text, a first frame, reference images and videos, or video editing, then check the model ID and billed duration for your route.

KuaishouVideo GenerationAvailable
From ~$0.094 / s at 720p without video input
Text-to-VideoImage-to-VideoReference-to-VideoVideo EditFirst FrameShort-Form Clips
Production routeLive
Model Highlights
Short 720p clips, creative drafts, and video editing
Use Cases
Social clips, ad variations, reference-led drafts
Input
Text, a first frame, reference images and videos, a source video to edit
Output
MP4 at 720p, 3-20s

Try Kling 4.0 Flash in the browser

Choose a Kling 4.0 Flash route and check its estimated cost before generating with your EvoLink balance. The playground uses the same endpoint and billing rules as your API integration.

Create a video

Runs against the live API with your own balance
Duration5s
Resolution
Aspect ratio
Estimated cost ~$0.47031.96 cr
720P × 5s
Ready

Write a prompt, add the first frame, references, or source video your route needs, then hit Generate — your result will appear here.

History

Results are kept for 24 hours — download anything you want to keep.

Your generation history will appear here

Know your Kling 4.0 Flash testing cost before you add credits.

Kling 4.0 Flash bills per second of 720p output video. When a reference-to-video request includes reference video, billed seconds are the output plus the longer of the reference video total or the output, at a lower per-second rate. Video edit bills the output plus the longer of the source video or the output at the video-edit rate, which is twice the source length with the default auto duration. First frames and reference images are free.

Your first test

Text-to-video, 3s at 720P — the cheapest possible request, no reference video
Minimum charge
Credits19.176

3 seconds at 720P

Approx. cost$0.282

About 33 runs for $10

Credits are reserved when the task is created and settled when it finishes. Failed tasks are refunded in full.

Top up

At the first-test settings: 3s at 720P
Add credits
$10
About 33 videos

Enough to validate the four routes end to end

$50
About 177 videos

Enough for a full round of creative iteration

$100
About 354 videos

Enough to run a small production batch

Common cost examples

Short clipText-to-video, 5s at 720P
~$0.470
~31.96 cr
20-second clipText-to-video, 20s at 720P
~$1.880
~127.84 cr
With reference videoReference-to-video, 5s output + 8s reference video at 720P
~$0.819
~55.692 cr
Video editVideo edit, 5s source video at 720P, billed as 10s
~$0.630
~42.84 cr

Calculated with the same function the Playground uses, at the rate for your user group. With reference video, an 8s reference and a 5s output bill as 13 seconds at the video-input rate. A video edit of a 5s clip with duration auto bills as 10 seconds at the video-edit rate.

Per-second rates

Text-to-video
kling-v4-flash-text-to-video · Output seconds
720P $0.094/s · 6.392 cr/s
Image-to-video
kling-v4-flash-image-to-video · Output seconds
720P $0.094/s · 6.392 cr/s
Reference-to-video
With reference images only · Output seconds
720P $0.094/s · 6.392 cr/s
Reference-to-video
With reference video · Output + max(reference video, output)
720P $0.063/s · 4.284 cr/s
Video edit
kling-v4-flash-video-edit · Output + max(source video, output)
720P $0.063/s · 4.284 cr/s

First frames and reference images are never billed. The reference-video row has a lower per-second rate, but billed seconds include the reference video, so a request with video input usually costs more in total. Video edit bills the output plus the longer of the source video or the output; with the default auto duration a 5s clip costs 10 billed seconds.

The minimum charge is 3s at 720P, which is also the cheapest request you can send.

Kling 4.0 Flash for 720p clips and creative iteration

Kling 4.0 Flash is the short-clip tier of Kuaishou's Kling 4.0 family. EvoLink exposes four model IDs on one endpoint: text-to-video, image-to-video from a first frame, reference-to-video with up to 10 images and 5 videos, and video edit for an existing clip. Clips run 3–20 seconds at 720p.

Open the playground
Model IDs
4 routes, one model
Resolution
720p
Duration
3-20s per request
Billing
Per second, video input billed
References
10 images · 5 videos

Kling 4.0 Flash: four routes, one model

Pick the model ID that matches your input. Each route accepts only its own media fields.

Kling 4.0 Flash Text-to-Video

kling-v4-flash-text-to-video

Generate 720p video from a text prompt, 3-20 seconds.

Kling 4.0 Flash Image-to-Video

kling-v4-flash-image-to-video

Animate a first frame into a 720p clip of 3-20 seconds.

Kling 4.0 Flash Reference-to-Video

kling-v4-flash-reference-to-video

Guide the video with up to 10 reference images and 5 reference videos.

Kling 4.0 Flash Video Edit

kling-v4-flash-video-edit

Edit one source video with a prompt and optional reference images; framing follows the source and length defaults to it.

Kling 4.0 Flash model information

The fields that decide how you call it, and what each one means for your integration.

Four model IDs

kling-v4-flash-text-to-video / kling-v4-flash-image-to-video / kling-v4-flash-reference-to-video / kling-v4-flash-video-edit

Each route accepts only its own media: no media on text-to-video, a first frame on image-to-video, reference images and videos on reference-to-video, and one source video plus reference images on video edit. Sending another route's fields returns 400.

Resolution

720p

Every request is generated and billed at 720p, with or without the quality field. Use Kling 4.0 when you need 1080p.

Duration

3-20 seconds, integer

One request produces a clip of up to 20 seconds; it does not guarantee an uninterrupted take. Billing follows the requested duration. Video edit also accepts auto (the default), which matches the source video’s length.

Reference material

Up to 10 images and 5 videos

Reference videos are 3-20s each and 20s in total. The prompt addresses them as <<<image_1>>> and <<<video_1>>>, numbered independently in array order.

Aspect ratio

16:9 / 9:16 / 1:1 / 21:9

Available on text-to-video and reference-to-video. Image-to-video follows the first frame and video edit follows the source video; neither takes aspect_ratio.

Frame control

First frame only

Image-to-video takes image_start only; image_end and keyframes return 400. Use Kling 4.0 image-to-video for first-to-last frame or keyframe control.

Video edit

One source video, 3-20s

The output keeps the source aspect ratio and original audio, so aspect_ratio is not accepted. duration is auto by default (same length as the source) or 3-20 seconds. Billed seconds are the output plus the longer of the source or the output, so auto bills twice the source length.

Key Kling 4.0 Flash API parameters

These fields cover the main integration decisions. Open the API Reference for route-specific request and response examples.

modelstring

Choose the text, image, reference, or edit model ID that matches your input.

Default: route-specific

promptstring

Describe the scene, motion, and camera. Up to 2500 characters; reference assets are addressed as <<<image_1>>> and <<<video_1>>>.

Default: required

qualityenum

720p is the only option. Omitting it gives the same result.

Default: 720p

durationinteger

Set 3-20 output seconds. Video edit also takes auto (the default) to match the source length.

Default: 5

aspect_ratioenum

Use 16:9, 9:16, 1:1, or 21:9 on text and reference routes.

Default: 16:9

image_startstring

First frame for image-to-video. Last and middle frames are not accepted on Flash.

Default: image route

image_urlsarray

Up to 10 reference images, addressed as <<<image_1>>>, <<<image_2>>>… in array order. Not billed.

Default: reference / edit routes

video_urlsarray

Reference route: up to 5 reference videos, 20s in total. Edit route: exactly one source video, 3-20s. Their seconds are billed together with the output.

Default: reference / edit routes

Two ways to use Kling 4.0 Flash: EvoLink API or Agent

Use the EvoLink API for product integration and batch jobs, or call it from Codex, Claude, or Gemini for fast creative and development workflows. Both paths share the same EvoLink API key, balance, model routes, and task history.

Option 1

Integrate with the EvoLink API

Best for: product backends, batch jobs, automated workflows

Call EvoLink’s unified video API from your server and control the model ID, parameters, task queue, callbacks, and result storage.

  1. 1Validate output and cost with a real brief in Playground
  2. 2Create an EvoLink API key in the console
  3. 3Pick the model ID that matches your task from the route cards above
  4. 4Submit the task and retrieve the result by polling or HTTPS callback
Option 2

Call it with an Agent

Best for: creative and development tasks in Codex, Claude, and Gemini

Give the Agent your output goal, assets, and acceptance criteria. It can choose the route, assemble the request, track the task, and return the result without requiring you to hand-code every step.

  1. 1Set EVOLINK_API_KEY in your local environment; never put it in code or a prompt
  2. 2Describe the output goal, references, and the key parameters
  3. 3Ask the Agent to call a Kling 4.0 Flash route and save the task ID
  4. 4Let the Agent poll the final state, download the result, and report failure reasons

What people build with Kling 4.0 Flash

Use Kling 4.0 Flash to test short video ideas when 720p meets your delivery requirements.

Fast concept drafts

Try prompt and camera ideas at the lower Flash rate before committing the best ones to a final render.

Short social clips

Produce 9:16 and 1:1 clips of up to 20 seconds for feeds, stories, and ads.

Ad variations from one product frame

Animate an approved product image in several directions and keep the variation that performs.

Reference-led variations

Keep a product or character from reference images while borrowing camera movement from a reference video.

Quick edits to existing footage

Swap an outfit, prop, or background in a short clip while keeping its framing and audio.

Prompt A/B tests

Run the same brief with different wording to learn what the model responds to before scaling a batch.
Browse AI video generators

Kling 4.0 Flash API code example and error handling

This example shows the shortest runnable flow: create a task, save the returned task ID, then poll or wait for an HTTPS callback. Open the API tab for the complete parameter and response reference.

View complete API docs
cURL
curl -X POST https://api.evolink.ai/v1/videos/generations \
  -H "Authorization: Bearer $EVOLINK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "kling-v4-flash-text-to-video",
    "prompt": "A paper boat drifts down a rain-soaked street at dusk, neon reflections ripple, slow tracking shot",
    "duration": 5,
    "quality": "720p",
    "aspect_ratio": "16:9",
    "callback_url": "https://your-domain.com/webhooks/video-task-completed"
  }'

# Save the returned task ID, then query:
curl https://api.evolink.ai/v1/tasks/{task_id} \
  -H "Authorization: Bearer $EVOLINK_API_KEY"

Parameter validation failed

Check every value against the parameter cards above: ranges, allowed options, asset counts, and file types must match the selected route.

Authentication or balance issue

Check the Authorization bearer token and confirm the available balance and task billing in the console.

Content or asset rejected

Review likeness rights, brand assets, readable text, sensitive content, and input-asset compliance.

Task failed or timed out

A Kling 4.0 Flash task that reaches a final failed state is not charged. Keep the task ID, inspect the final state, and identify whether the cause is validation, review, or execution before retrying.

Callback not received

callback_url must be a public HTTPS URL, not localhost or a private network address. Always keep the task ID as a polling fallback.

Choose Kling 4.0 Flash for short 720p clips and per-second billing

Choose Kling 4.0 Flash for short 720p clips, high-volume drafts, and quick edits. Move to Kling 4.0 when a shot needs 1080p, a longer take, or frame-by-frame control.

Good fit

  • Clips of up to 20 seconds at 720p are enough for the job
  • You iterate on many prompt or reference variations and want a lower per-second rate
  • You animate a single approved first frame or edit an existing clip

Consider another route

  • You need 1080p or a take longer than 20 seconds — use Kling 4.0
  • You need first-to-last frame or keyframe control — use Kling 4.0 image-to-video
  • You need 4K, negative prompts, or a sound on/off switch — they are not accepted on these routes
  • You need multi-shot storyboards, saved subjects, custom voices, or video extension — not part of this release
Test it in the Playground

Run Kling 4.0 Flash in production

Generation is asynchronous. Design around completion events and promote the drafts you keep to a final route.

1

Keep the flow asynchronous

Return the task ID immediately, show a pending state, and finish through polling or an HTTPS callback.

2

Budget for reference video

Budget for creative retries as well as video seconds: a completed clip may still fail your review. Reference-video seconds are billed too; trim inputs to the part that matters.

3

Download results promptly

Store the files you want to keep as part of your completion handler instead of relying on result links.

Kling 4.0 Flash details worth knowing

Reference numbering is positional

Images and videos are numbered independently and follow array order. Reordering an array changes what <<<image_2>>> refers to.

Video input changes the billed seconds

With reference video, billed seconds are the output plus the longer of the reference total or the output. A 10s output with 5s of reference video bills as 20 seconds; with 15s of reference video, it bills as 25 seconds. Both use the video-input rate.

Fields Flash does not take

image_end, keyframes, 1080p, negative_prompt, sound, watermark settings, saved subjects, and multi-shot storyboards (model_params) are not accepted on Kling 4.0 Flash routes and return 400.

Why call Kling 4.0 Flash through EvoLink

Transparent per-second pricing

Billed per second of video, with a separate rate when video input is included. Your exact rate is in the table above.

One API key

Reuse your EvoLink API key and the shared video generation endpoint, without a separate Kling developer account.

One balance

Use one prepaid balance for Kling 4.0 Flash and other EvoLink models, without buying separate vendor credits.

Task tracking built in

Poll a single task endpoint or register a callback. Reserved and settled amounts are both visible in your logs.

Reuse your integration flow

Keep the same EvoLink API key, video generation endpoint, and task tracking flow when switching models. Check the new model’s accepted fields, duration limits, and pricing, then test its output before changing production traffic.

Kling Model Family

Compare Kling generations under one EvoLink account and API key, then choose by resolution, length, editing features, and cost.

Compare all Kling models
Kling 4.0

Kling 4.0

The full Kling 4.0 model: 1080p, takes of up to 30 seconds, and first, middle, and last frame control.

View
Kling 3.0 Turbo

Kling 3.0 Turbo

The previous generation's faster route for text-to-video and image-to-video.

View
Kling 3.0 Motion Control

Kling 3.0 Motion Control

The previous generation's motion control route: copy a reference video's motion onto a character image.

View

Other video models on EvoLink besides Kling 4.0 Flash

Seedance 2.5

Seedance 2.5

ByteDance's video model with multi-shot storytelling and image, video, and audio references.

View
Wan 3.0

Wan 3.0

Alibaba's Wan 3.0 with mixed references, documents, and web pages as input.

View
MiniMax H3

MiniMax H3

MiniMax's 2K route with first/last frame control and multimodal references.

View
Veo 3.1

Veo 3.1

Google DeepMind's Veo 3.1: 8-second clips with native audio, available in Fast and Pro variants.

View

Next steps with Kling 4.0 Flash

Where to go once you have decided Kling 4.0 Flash fits.

Kling 4.0 Flash FAQ

What is the Kling 4.0 Flash API?

Kling 4.0 Flash is the 720p short-clip tier of Kuaishou's Kling 4.0 family. EvoLink provides kling-v4-flash-text-to-video, kling-v4-flash-image-to-video, kling-v4-flash-reference-to-video, and kling-v4-flash-video-edit through /v1/videos/generations.

How is Kling 4.0 Flash different from Kling 4.0?

Flash outputs 720p only, runs 3 to 20 seconds per request, and takes a first frame only on image-to-video. Kling 4.0 adds 1080p, takes of up to 30 seconds, and first, middle, and last frame control. Both use the same endpoint and request format, and Flash costs less per second.

Why are there four model IDs?

Each route accepts different media: none on text-to-video, a first frame on image-to-video, reference images and videos on reference-to-video, and one source video on video edit. Choose the ID that matches your input; media fields from another route return 400.

How much does Kling 4.0 Flash cost?

Total cost depends on output duration and any input video. Without video input, only output seconds are billed. With reference video, billed seconds are the output plus the longer of the reference total or the output, at the video-input rate. A lower per-second rate does not necessarily mean a cheaper task. Video edit bills the output plus the longer of the source or the output; auto bills twice the source length. See the table above for current rates.

What resolution does Kling 4.0 Flash output?

720p only. You can omit quality or send 720p; any other value returns 400. Use Kling 4.0 when you need 1080p.

How long can a Kling 4.0 Flash video be?

3 to 20 seconds per request, in whole seconds. Video edit defaults to the length of its source video (duration auto) or takes 3 to 20 seconds.

Does Kling 4.0 Flash support last frames or keyframes?

No. Flash image-to-video takes image_start only; image_end and keyframes return 400. Use Kling 4.0 image-to-video when you need a first-to-last frame transition or middle frames.

How do I reference images and videos in the prompt?

Write <<<image_1>>> for the first image in image_urls and <<<video_1>>> for the first video in video_urls. Images and videos are numbered independently and follow array order.

Are reference images billed?

There is no separate input charge for first frames or reference images. Video generation is still billed; reference videos and source videos also affect the billed duration.

How is video edit billed?

On the output plus the longer of the source video or the output, at the video-edit rate; the source length is rounded up to a whole second. With the default duration auto the output matches the source, so a 5s clip bills as 10 seconds; a 10s clip with duration 20 bills as 40 seconds. Reference images are free.

Can I control individual shots with Kling 4.0 Flash?

These routes do not accept structured multi-shot storyboards through model_params. A prompt can describe scene changes, and a generated clip may contain cuts; a single uninterrupted take is not guaranteed. For precise editing, generate shots separately and review the results.

Can I use saved subjects or custom voices?

Not in this release. Saved subjects (element_list), custom voices, and video extension are not available on these routes yet.

Do all features in Kling's announcement work on EvoLink?

No. Use the EvoLink API reference for each route. These routes accept 720p output and prompts up to 2500 characters. 4K, HDR controls, saved subjects, custom voices, multi-shot storyboards and video extension are not offered here. A provider announcement or client subscription does not define EvoLink's request fields.

Do I need a Kling subscription to use this API?

Use an EvoLink account, API key, and sufficient EvoLink balance. A Kling app subscription is not required for these EvoLink routes, and Kling app credits do not pay for EvoLink API requests. Check the pricing section before submitting a task.

Is Kling 4.0 Flash always faster than Kling 4.0?

Kling positions Flash for faster creation, but that is not a fixed API completion-time guarantee. Queue time, input media, output duration, and retries affect your workflow. Compare completion time and cost per accepted clip using your own prompts and inputs.