provider

Kuaishou Kling AI

Direct answerKuaishou Kling Open Platform provides image and video generation APIs for creative content production.

Updated · Reviewed

Separate the platform from this site

Kling AI is Kuaishou's image and video generation platform. Direct Kling calls and calls through this site use different credentials: direct calls follow Kling's JWT rules, while this site's /v1/videos route uses this site's token and represents only the unified video workflow adapted here. A feature in the consumer UI is not proof that either API exposes it; confirm the exact model and route in the model marketplace.

Direct authentication does not put the AK or SK in Bearer

Obtain an Access Key (AK) and Secret Key (SK) in the Kling console, use them to sign a short-lived JWT according to RFC 7519, and then send Authorization: Bearer <JWT>. Keep the SK only in a server-side secret manager; never commit it, expose it to a browser, log it, or reuse an expiring token indefinitely. This site's token cannot authenticate direct Kling calls, and Kling AK/SK values cannot authenticate this site directly.

Persist two different identifiers

The request_id returned by creation identifies the HTTP request for tracing and support. The task_id identifies the generation job and is the value used to retrieve progress and results. Persist both with the creation time, model, and redacted parameters, and never place request_id in the task-query path. Job status is submitted, processing, succeed, or failed: the first two are in progress and the last two are terminal.

Poll with explicit bounds

Poll the task endpoint with task_id, bounded exponential backoff plus jitter, a maximum attempt count, a total deadline, and cancellation. Read output only after succeed; on failed, preserve the error and request_id, because parameter or moderation failures are not repaired by infinite retry. Copy result media promptly into controlled storage instead of treating a provider URL as permanent.

Cost, limits, and safety

Validate asset type, size, aspect ratio, duration, and model support before submission. Keep an idempotency record for each business request so timeout retries do not create and bill duplicate jobs. Check JWT and permissions for 401/403, reduce creation and polling pressure for 429, and retry only transient 5xx failures with limits. Obtain rights for people, faces, brands, and copyrighted assets and account for moderation, privacy, and commercial-use requirements.

Reviewed provider catalog

Latest models by capability

These are provider-catalog models, not a promise of availability on this site. Confirm callable IDs, endpoints, and pricing in the model marketplace.

Image generation and editing

Video generation and editing

Check live availability in the model marketplace

Use cases

  • Video generation
  • Image generation
  • Creative content workflows

API protocols

  • /v1/videos

FAQ

Can a Kling AK or SK be placed directly in Bearer?

No. For direct Kling access, sign a short-lived JWT with the AK and SK according to RFC 7519, then send Authorization: Bearer <JWT>. Keep the SK server-side only.

What is the difference between request_id and task_id?

request_id is for request tracing and troubleshooting; task_id identifies the generation job for status polling and result retrieval. Persist both but never interchange them.

When should a Kling client stop polling?

submitted and processing are in-progress states; succeed and failed are terminal. Use bounded backoff, a total deadline, and cancellation rather than unbounded rapid polling.

Must I sign a Kling JWT when calling through this site?

No. This site's /v1/videos route uses this site's token. JWT signing applies only to direct Kling API calls; confirm available models and routes in this site's marketplace.

Official sources

  1. Kling AI Open Platform Overview Official
  2. Kling AI API Quick Start Official