Kling O1 API for Multimodal Video Generation

Access Kling O1 through GoEnhance for prompt-only video, first-frame or first-and-last-frame control, ordered reference images, multi-image elements, and one reference video. Submit one asynchronous request, save the returned img_uuid, then poll or receive a callback. GoEnhance provides independent access and is not Kuaishou or Kling’s official API, partner, or model developer.
Get API Key
Cinematic video production scene representing Kling O1 API generation

One endpoint for several reference-driven workflows

Prompt, frame, and reference control

POST to https://api.goenhance.ai/api/v1/videos/generations with model: kling-o1. A prompt is required. Add a first frame, a first-and-last-frame pair, ordered ref_imgs, element IDs, or one ref_videos input when the material rules allow it.
Unbranded film set representing prompt and image guided video generation

Generate from motion or edit a base video

With a reference video, use video_type: feature to imitate motion or style, or video_type: base to edit the supplied video in place. O1 can retain that video’s original sound, but it cannot generate a new audio track.
Unbranded video editing stage representing reference video workflows
Validate material combinations before submitting a task.

Kling O1 API capabilities and validation rules

Model and prompt

Set model to kling-o1. The prompt is required and accepts up to 2,500 characters; use indexed references such as @image_1, @element_1, and @video_1.

Frames and references

Use image_url for the first frame and image_end_url for the last frame. Reference images use ordered ref_imgs; one reference video may be supplied through ref_videos.

Material budget

Frames, reference images, and element IDs may total no more than 7 materials, or no more than 4 when a reference video is used. A first-and-last-frame pair disallows extra reference images and element IDs.

Duration

Choose an integer from 3 to 10 seconds; the documented default is 5. A first-frame request without reference images or video accepts only 5 or 10 seconds.

Resolution and ratio

Choose 720p or 1080p. Text-only requests accept 16:9, 9:16, or 1:1; a first frame or reference video determines the ratio instead. O1 has no 4K tier.

Audio behavior

generate_audio does not create new audio. With a reference video, it can retain the original sound; otherwise O1 produces no generated audio track.
GoEnhance bills generated video per second at $0.02 per token.

Kling O1 API pricing

720p

Without video input: 4.2 tokens per second ($0.084/s). With video input: 6.3 tokens per second ($0.126/s).

1080p

Without video input: 5.6 tokens per second ($0.112/s). With video input: 8.4 tokens per second ($0.168/s).

Estimate each task

Multiply the requested duration by the exact rate for the selected resolution and whether a reference video is present. Retaining reference-video audio has no separate surcharge.

Integrate Kling O1 in six steps

1

1. Create an API key

Generate a GoEnhance API key and send it in the Authorization header.
2

2. Choose materials

Select the first frame, last frame, ordered references, elements, or one reference video required by the shot.
3

3. Validate the budget

Enforce the 7-material limit, or the 4-material limit when a reference video is present, before submission.
4

4. Submit the job

POST to https://api.goenhance.ai/api/v1/videos/generations with model: kling-o1 and persist the returned img_uuid.
5

5. Track completion

Poll GET /api/v1/jobs/detail or provide a publicly accessible HTTPS custom_callback_url.
6

6. Handle terminal states

Process success and failure idempotently. Callback bodies match the job-detail response; non-200 callback responses are retried up to three times with a three-second timeout per attempt.
Get API Key
Build repeatable video workflows around explicit reference semantics.

Developer use cases for Kling O1

Character continuity

Use ordered reference images or reusable element IDs to keep approved subjects available to prompt templates.

Product motion

Animate a hosted product frame while your application manages validation, prompt templates, and approvals.

First-to-last transitions

Define opening and ending frames for short transitions without adding incompatible reference materials.

Motion reference

Use a feature reference video to guide motion or visual style while preserving one asynchronous task pipeline.

Video editing

Use base-video mode for prompt-directed edits to one supplied clip within O1’s documented duration and resolution limits.

Localized creative variants

Parameterize prompts and aspect ratios for regional campaigns while keeping task submission and completion handling consistent.
Answers to common integration, pricing, and Kuaishou API questions.

Kling O1 API FAQ

What is the Kling O1 API endpoint on GoEnhance?

Submit requests to POST https://api.goenhance.ai/api/v1/videos/generations with model set to kling-o1. The response returns an img_uuid for asynchronous tracking.

How does Kling O1 API pricing work?

Pricing is per generated second. Rates are 4.2 tokens/s at 720p and 5.6 tokens/s at 1080p without video input, or 6.3 and 8.4 tokens/s respectively with video input. USD equivalents are $0.084/s, $0.112/s, $0.126/s, and $0.168/s.

Which reference inputs are supported?

You can use a first frame, a first-and-last-frame pair, ordered reference images, element IDs, or one reference video. Each combination must satisfy the shared material budget and compatibility rules.

Can Kling O1 generate or retain audio?

O1 cannot generate a new audio track. When a reference video is supplied, generate_audio can retain that video’s original sound.

Is Kling O1 interchangeable with Kling V3 Omni?

No. O1 has a distinct request contract: no multi-shot, no 4K, no generated audio, a 10-second maximum duration, and a 2,500-character prompt limit.

Is this Kuaishou’s official Kling O1 API?

No. This page describes independent Kling O1 access through GoEnhance. GoEnhance is not presented as Kuaishou or Kling’s official API, partner, or model developer.

Should I poll or use a callback?

Use polling when your worker already maintains a job loop. Use custom_callback_url when your public HTTPS endpoint can validate and idempotently process status updates.

Start building with the Kling O1 API