> ## Documentation Index
> Fetch the complete documentation index at: https://apidoc.deerapi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Kling Query Task

> Use DeerAPI to call the Kling Query Task endpoint with request details, response details, examples, and an OpenAPI playground.

## Overview

Use this endpoint to call the Kling Query Task 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:

```text theme={null}
https://api.deerapi.com
```

```text theme={null}
Authorization: Bearer $DEERAPI_KEY
```

## Model selection

Choose a current model ID from the [live pricing page](https://api.deerapi.com/pricing). 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.


## OpenAPI

````yaml /api/openapi/video/kling/get-query-task.openapi.json GET /kling/v1/{action}/{action2}/{task_id}
openapi: 3.1.0
info:
  title: DeerAPI Kling Task Query
  description: Use this field according to the endpoint schema.
  version: 1.0.0
servers:
  - url: https://api.deerapi.com
security:
  - bearerAuth: []
paths:
  /kling/v1/{action}/{action2}/{task_id}:
    get:
      summary: DeerAPI Kling Task Query
      description: Use this field according to the endpoint schema.
      operationId: getKlingTaskByRoute
      parameters:
        - name: action
          in: path
          required: true
          description: Use this field according to the endpoint schema.
          schema:
            type: string
        - name: action2
          in: path
          required: true
          description: Use this field according to the endpoint schema.
          schema:
            type: string
        - name: task_id
          in: path
          required: true
          description: Use this field according to the endpoint schema.
          schema:
            type: string
      responses:
        '200':
          description: Use this field according to the endpoint schema.
          content:
            application/json:
              schema:
                type: object
                required:
                  - code
                  - message
                  - request_id
                  - data
                properties:
                  code:
                    type: integer
                    description: Use this field according to the endpoint schema.
                  message:
                    type: string
                    description: Use this field according to the endpoint schema.
                  request_id:
                    type: string
                    description: Use this field according to the endpoint schema.
                  data:
                    type: object
                    description: Use this field according to the endpoint schema.
                    required:
                      - task_id
                      - task_status
                      - created_at
                      - updated_at
                      - task_info
                      - task_result
                    properties:
                      task_id:
                        type: string
                        description: Use this field according to the endpoint schema.
                      task_status:
                        type: string
                        description: Use this field according to the endpoint schema.
                      created_at:
                        type: integer
                        description: Use this field according to the endpoint schema.
                      updated_at:
                        type: integer
                        description: Use this field according to the endpoint schema.
                      task_info:
                        type: object
                        description: Use this field according to the endpoint schema.
                        required:
                          - parent_video
                        properties:
                          parent_video:
                            type: object
                            description: Use this field according to the endpoint schema.
                            required:
                              - id
                              - url
                              - duration
                            properties:
                              id:
                                type: string
                                description: >-
                                  Use this field according to the endpoint
                                  schema.
                              url:
                                type: string
                                description: >-
                                  Use this field according to the endpoint
                                  schema.
                              duration:
                                type: string
                                description: >-
                                  Use this field according to the endpoint
                                  schema.
                      task_result:
                        type: object
                        description: Use this field according to the endpoint schema.
                        required:
                          - videos
                        properties:
                          videos:
                            type: array
                            description: Use this field according to the endpoint schema.
                            items:
                              type: object
                              properties:
                                id:
                                  type: string
                                  description: >-
                                    Use this field according to the endpoint
                                    schema.
                                url:
                                  type: string
                                  description: >-
                                    Use this field according to the endpoint
                                    schema.
                                duration:
                                  type: string
                                  description: >-
                                    Use this field according to the endpoint
                                    schema.
      x-codeSamples:
        - lang: Python
          label: Example
          source: >
            import os

            import requests


            url =
            "https://api.deerapi.com/kling/v1/example-id/example-id/example-id"

            headers = {"Authorization": "Bearer " + os.environ["DEERAPI_KEY"]}

            response = requests.request("GET", url, headers=headers)

            print(response.json())
        - lang: JavaScript
          label: Example
          source: >
            const response = await
            fetch("https://api.deerapi.com/kling/v1/example-id/example-id/example-id",
            {
              method: "GET",
              headers: { Authorization: `Bearer ${process.env.DEERAPI_KEY}` },
            });

            console.log(await response.json());
        - lang: Shell
          label: Example
          source: >
            curl -s
            "https://api.deerapi.com/kling/v1/example-id/example-id/example-id"
            \
              -H "Authorization: Bearer $DEERAPI_KEY"
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Use a DeerAPI API Key as a Bearer token.

````