AGTCloud API Docs
GuidesAPI ReferenceIntegrations and resourcesUpdate and help
Video generationKling

Text-to-video

Create text-to-video or Omni/O1 tasks through the Kling native API.

Standard text-to-video and Omni/O1 use the same request method and path, with different request structures for their inputs.

POST/kling/v1/videos/text2video

Use Kling native fields directly. The platform handles authentication and routing without converting the payload to the common format.

Omni/O1 uses the same native create path and is distinguished by the model and media fields.

Authorization

bearerAuth
AuthorizationBearer <token>

Use Bearer your-api-key in the Authorization header.

In: header

Request Body

application/json

Kling native text-to-video or Omni/O1 request.

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json