Kling Omni Video - DeerAPI Documentation

POST

/

kling

/

v1

/

videos

/

omni-video

cURL

curl https://api.deerapi.com/kling/v1/videos/omni-video \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DEERAPI_KEY" \
  -d '{
    "model_name": "kling-video-o1",
    "prompt": "A cinematic shot of a modern glass workspace at sunrise with smooth camera movement.",
    "image_list": [
      {
        "image_url": "https://example.com/omni-reference.png"
      }
    ],
    "mode": "pro",
    "aspect_ratio": "16:9",
    "duration": "5",
    "callback_url": "https://example.com/kling/callback"
  }'

{
  "code": 123,
  "message": "<string>",
  "request_id": "<string>",
  "data": {
    "task_id": "<string>",
    "task_status": "<string>",
    "task_info": {
      "external_task_id": "<string>"
    },
    "created_at": 123,
    "updated_at": 123
  }
}

Overview

Use this endpoint to call the Kling Omni Video workflow through DeerAPI. The API reference on this page shows the request schema, response schema, authentication requirements, and runnable examples for the configured endpoint.

Before you start

Use the DeerAPI base URL and pass your API Key in the Authorization header:

https://api.deerapi.com

Authorization: Bearer $DEERAPI_KEY

Model selection

Choose a current model ID from the live pricing page. Model availability changes over time, so avoid copying a model ID from an old project without checking the live list first.

Implementation notes

Use the OpenAPI playground for the exact request fields accepted by this endpoint.
Keep API Keys on the server side when you build production applications.
Log the request ID from failed calls so support can investigate the request.
Retry 429, 500, and 503 responses with exponential backoff.

Authorizations

Authorization

string

header

required

Use a DeerAPI API Key as a Bearer token.

Headers

Content-Type

string

Body

application/json

Use this field according to the endpoint schema.

prompt

string

default:Hello

required

Use this field according to the endpoint schema.

model_name

string

Use this field according to the endpoint schema.

multi_shot

boolean

Use this field according to the endpoint schema.

shot_type

string

Use this field according to the endpoint schema.

multi_prompt

object[]

Use this field according to the endpoint schema.

Show child attributes

sound

string

Use this field according to the endpoint schema.

image_list

object[]

Use this field according to the endpoint schema.

Show child attributes

element_list

object[]

Use this field according to the endpoint schema.

Show child attributes

mode

string

Use this field according to the endpoint schema.

aspect_ratio

string

Use this field according to the endpoint schema.

duration

string

Use this field according to the endpoint schema.

Use this field according to the endpoint schema.

Show child attributes

watermark_info

object

Use this field according to the endpoint schema.

Show child attributes

callback_url

string

Use this field according to the endpoint schema.

external_task_id

string

Use this field according to the endpoint schema.

Response

200 - application/json

Use this field according to the endpoint schema.

code

integer

required

Use this field according to the endpoint schema.

message

string

required

Use this field according to the endpoint schema.

request_id

string

required

Use this field according to the endpoint schema.

data

object

required

Show child attributes

Kling Video Effects

Kling Omni Query

cURL

curl https://api.deerapi.com/kling/v1/videos/omni-video \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DEERAPI_KEY" \
  -d '{
    "model_name": "kling-video-o1",
    "prompt": "A cinematic shot of a modern glass workspace at sunrise with smooth camera movement.",
    "image_list": [
      {
        "image_url": "https://example.com/omni-reference.png"
      }
    ],
    "mode": "pro",
    "aspect_ratio": "16:9",
    "duration": "5",
    "callback_url": "https://example.com/kling/callback"
  }'

{
  "code": 123,
  "message": "<string>",
  "request_id": "<string>",
  "data": {
    "task_id": "<string>",
    "task_status": "<string>",
    "task_info": {
      "external_task_id": "<string>"
    },
    "created_at": 123,
    "updated_at": 123
  }
}