Pixmind
All API models
Kling AIKling AI/ VideoPlanned

Kling 4.0 API

kling-v4

Generate 3–30 second videos with stereo audio. First/last frames, keyframes, multimodal references, video editing and extension.

  • Text to video
  • Image to video
  • Multi-reference
  • First / last frame

This route is published for integration planning and is not accepting requests yet.

Playground

Configure a request, inspect the exact JSON, then run it with your account.

Playground opens when this route becomes available.
Response
The API response will appear here.

OUTPUT GALLERY

Kling 4.0 in action

Real Kling 4.0 outputs across text-to-image, multilingual text rendering, natural-language editing, and multi-reference composition.

Prompt: ワークフローの概念図。 Kling 出力サンプルではありません。 最初の構図から最後の構図までゆっくりと移動してください。カメラを 1 回スムーズに動かすだけで、製品の形状とラベルを維持できます。
Prompt: ワークフローの概念図。 Kling 出力サンプルではありません。 @Image1の人は海岸沿いを歩きます。 @Video1 のカメラの動きに従い、服装の一貫性を保ちます。
Prompt: ワークフローの概念図。 Kling 出力サンプルではありません。 @Video1 を雪の降る冬の夜に変更します。被写体、動き、カメラのパスを保存します。

API PRICING

API pricing

Compare the complete API billing table for this route. Token models separate input, output, cache-read, cache-write, and long-context rates; media models vary by configuration.

Pricing coming soon

CAPABILITIES

What this route supports

Use one stable PixMind model ID while keeping provider-specific setup out of your application.

Text to video

Turn a complete shot brief into a generated video sequence.

Image to video

Animate a supplied image while preserving its subject and visual direction.

Multi-reference

Carry subjects, products, or visual direction across reference-led outputs.

First / last frame

Control a transition by defining both the opening and closing composition.

Native audio

Generate an audio-capable result on supported video routes.

TECHNICAL SPECS

Supported parameters

Inputs, supported configurations, and request parameters for the Kling 4.0 API.

期間
3–30s
出力層
720p / 1080p
最初と最後のフレーム
開始画像とオプションの終了画像を設定します。 API は最大 8 つの中間キーフレームも受け入れます。
マルチモーダルな参照
最大 10 個の画像と 5 個のビデオを使用し、最大 30 秒の参照ビデオを使用します。 API は、5 ~ 30 秒のオーディオ クリップを 3 つ受け入れます。すべての参照の合計は最大 15 個のアセットです。

MODEL WORKFLOWS

What to build with Kling 4.0

Choose a task that matches the live route capabilities, then adapt one of these prompt starters.

Best-fit tasks

  • Turn a complete shot brief into a generated video sequence.
  • Animate a supplied image while preserving its subject and visual direction.
  • Carry subjects, products, or visual direction across reference-led outputs.
  • Control a transition by defining both the opening and closing composition.

Prompt starters

Replace the brackets
Starter

Use the reference images to keep [person/product] consistent. Create a coordinated [number]-image campaign across [scenes] in one visual direction.

Starter

Create one [duration]-second shot of [subject] in [setting]. The subject [action]. Camera: [movement and framing]. Lighting: [direction and mood]. Keep motion physically coherent and the shot continuous.

Starter

Animate the supplied image into a [duration]-second shot. Preserve [subject details]. Add [subject motion] and [camera motion]. Keep the original composition, lighting, and visual identity stable.

Starter

Start exactly from the first frame and end on the supplied last frame. Build one continuous transition where [subject or camera action] connects both compositions without cuts.

MODEL SELECTION

Choose Kling 4.0 when the job fits

Compare nearby live routes by task, supported capability, and current entry price before you lock a model ID into production.

ModelBest forKey capabilitiesEntry priceAvailabilityAction
Kling 4.0
Kling AI · current page
Turn a complete shot brief into a generated video sequence.Text to video · Image to video · Multi-referencePricing coming soonPlannedSelected
Kling 3.0 Turbo
Kling AI
Turn a complete shot brief into a generated video sequence.Text to video · Image to video$0.13 / secAvailableView route
Happy Horse 1.0
MiniMax
Turn a complete shot brief into a generated video sequence.Text to video · Image to video · Multi-reference$0.19 / secAvailableView route
Happy Horse 1.1
HappyHorse
Turn a complete shot brief into a generated video sequence.Text to video · Image to video$0.24 / secAvailableView route

Capabilities and starting prices are a current PixMind route snapshot. The accepted request contains the final configuration and billing quote.

GET STARTED

From playground to production

01

Create a scoped key

Create an API key with the permissions required by this model.

02

Send the request

Use the model ID and endpoint shown above from your backend service.

03

Track the task

Read language-model output from the response. For image and video requests, use the returned task ID to retrieve the result.

FAQ

Kling 4.0 API questions

どのモデル ID と API エンドポイントを使用すればよいですか?+

kling-v4 を POST /api-platform/v1/generations に送信します。 GET /api-platform/v1/tasks/{taskId} で、返された PixMind taskId をポーリングします。

参照、編集、または拡張モードを選択するにはどうすればよいですか?+

omni_reference_task_type を参照、編集、または拡張するように設定します。編集と拡張には 1 つの入力ビデオが必要です。拡張子は aspect_ratio または audio_setting を受け入れません。

720p 入力価格とは何を意味しますか?+

ビデオ編集およびビデオ参照の場合、請求対象となる 1 秒あたり 0.105 米ドルの料金がかかります。期間なしの 3.04 秒の編集には、4 + 4 = 8 秒の料金がかかります。

どの Kling 4.0 パラメータが拒否されますか?+

ルートは、mode=std/pro/4k、negative_prompt、watermark=true、および audio=false を拒否します。検証とメディアの調査は請求前に行われます。失敗した世代は全額返金されます。

What model ID should I use for the Kling 4.0 API?+

Use kling-v4 in the model field. This is the stable PixMind route identifier shown in the playground request JSON.

Which endpoint does the Kling 4.0 API use?+

Send POST requests to /v1/generations. Keep your API key on your server and pass it as a Bearer token.

Is the playground using a real API request?+

Yes. When you click Run model, PixMind forwards the displayed payload with the API key you entered. A successful request may create a paid task.

Does PixMind save the API key entered here?+

No. The playground keeps the key only in component memory and sends it for the current request; it is not written to browser storage.

Is API pricing the same as PixMind Studio pricing?+

No. API usage resolves through the apiPlatform pricing role and a separate pay-as-you-go ledger. Studio pricing includes the creation interface and product workflow services.

Why can the final price differ from the starting price?+

The entry price reflects the configuration displayed on this page. Resolution, duration, quality, audio, references, and output count can affect the final task price.

START WITH THE CONTROL PLANE

Turn your first Kling 4.0 prompt into a real API request

Test the exact payload in the playground, then create a scoped key and move the same model ID into your application.