POST images/upscale — Kling API

Upscale Images

April 24, 2025 (October 20, 2026)

Request Headers
Request Body
Responses
Model
Examples
Try It

This endpoint upscales previously generated images to higher resolution. It takes a task ID and work ID from a completed task, and creates a new upscaled version of the specified image.

To improve the quality of any image by its URL, including one Kling did not generate, use POST /images/enhance.

https://api.useapi.net/v1/kling/images/upscale

Request Headers

Authorization: Bearer {API token}
Content-Type: application/json
# Alternatively you can use multipart/form-data
# Content-Type: multipart/form-data

API token is required, see Setup useapi.net for details.

Request Body

{
  "email": "[email protected]",
  "task_id": "123456789",
  "workId": "987654321"
}

email is optional. Leave it out and the job goes to one of your accounts that has a free job slot, picked at random. Each account runs at most its maxJobs jobs at once, and GET scheduler/available shows the free slots. If no account has a free slot, the response is 429.
Pass email to run the job on that account (429 if it is busy). Uploaded files, elements, voices, avatars and earlier tasks belong to one account, so pass the email of the account they came from.
With more than one account, reading the task with GET tasks/task_id needs its account’s email. The response’s task.userId is that account’s session.userId in GET accounts, and GET scheduler lists each running task with its email.
task_id is required, the ID of a completed task that generated the image. Must be in the succeed status, which can be checked using GET /tasks/task_id.
workId is required, the ID of the specific image from the task to upscale. Can be found in the works array of the GET /tasks/task_id response.
maxJobs is optional, range from 1 to 50.
Specifies the maximum number of concurrent jobs.
replyUrl is optional, a callback URL to receive generation progress and result.
See GET /tasks/task_id for response model.
replyRef is optional, a reference identifier for the callback.

Responses

200 OK

{
  "task": {
    "id": 123456789,
    "userId": 12345,
    "type": "mmu_image_upscale_aiweb",
    "scene": "NORMAL_CREATION",
    "status": 5,
    "status_name": "submitted",
    "status_final": false,
    "taskInfo": {
      "type": "mmu_image_upscale_aiweb",
      "inputs": [
        {
          "name": "input",
          "inputType": "URL",
          "token": null,
          "blobStorage": null,
          "url": "https://s21-kling.klingai.com/....jpg",
          "cover": null,
          "fromWorkId": 987654321
        }
      ],
      "arguments": [
        {
          "name": "biz",
          "value": "klingai"
        },
        {
          "name": "__initialType",
          "value": "mmu_img2img_aiweb"
        },
        {
          "name": "__initialPrompt",
          "value": "Portrait of a woman with blue eyes"
        }
      ],
      "extraArgs": {},
      "callbackPayloads": [],
      "scene": "NORMAL_CREATION"
    },
    "favored": false,
    "deleted": false,
    "viewed": false,
    "createTime": 1745376611075,
    "updateTime": 1745376611075
  },
  "works": [],
  "status": 5,
  "status_name": "submitted",
  "status_final": false,
  "message": "",
  "limitation": {
    "type": "mmu_image_upscale_aiweb",
    "remaining": 10000,
    "limit": 10000
  },
  "userPoints": {
    "points": [],
    "total": 0
  },
  "userTickets": {
    "ticket": []
  },
  "editProject": null
}

400 Bad Request

The parameters are invalid. When Kling refuses the submitted parameters, error carries Kling’s own message.
```
{
  "error": "Task 123456789 is not completed"
}
```

401 Unauthorized

{
  "error": "Unauthorized",
  "code": 401
}

500 Internal Server Error

Kling uses a 500 response to indicate moderation and other issues with the input. It may be hard to separate actual 500 errors from moderation errors, so use the error field text and your best judgement to tell them apart, since the message field most often has very generic and perhaps misleading text.
```
{
  "error": "The content you uploaded appears to violate the community guidelines. (CM_EXT.POther)",
  "message": "Service busy (CM_EXT.POther)"
}
```

When successful, the response includes a task ID which can be used to check the status using GET /tasks/task_id.

Model

{ // TypeScript, all fields are optional
    task: {
        id: number
        userId: number
        type: string
        scene: string
        status: number
        status_name: 'submitted' | 'failed' | 'processing' | 'succeed'
        status_final: boolean
        taskInfo: {
            type: string
            inputs: Array<{
                name: string
                inputType: string
                token: string | null
                blobStorage: any | null
                url: string
                cover: string | null
                fromWorkId: number | null
            }>
            arguments: Array<{
                name: string
                value: string
            }>
            extraArgs: Record<string, any>
            callbackPayloads: any[]
            scene: string
        }
        favored: boolean
        deleted: boolean
        viewed: boolean
        createTime: number
        updateTime: number
        viewTime: number
    }
    works: Array<any>
    status: number
    status_name: 'submitted' | 'failed' | 'processing' | 'succeed'
    status_final: boolean
    message: string
    error: string
    limitation: {
        type: string
        remaining: number
        limit: number
    }
    userPoints: {
        points: Array<{
            orderId: string
            type: string
            amount: number
            balance: number
            startTime: number
            endTime: number
        }>
        total: number
    }
    userTickets: {
        ticket: Array<{
            orderId: string
            type: string
            packageType: string
            amount: number
            balance: number
            startTime: number
            endTime: number
        }>
    }
    editProject: any | null
}

Examples

curl -X POST "https://api.useapi.net/v1/kling/images/upscale" \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer …" \
   -d '{
     "email": "[email protected]",
     "task_id": "123456789",
     "workId": "987654321"
   }'

const token = "API token";
const email = "Previously configured account email";
const apiUrl = "https://api.useapi.net/v1/kling/images/upscale"; 
const response = await fetch(apiUrl, {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": `Bearer ${token}`,
  },
  body: JSON.stringify({
    email: email,
    task_id: "123456789",
    workId: "987654321"
  })
});
const result = await response.json();
console.log("response", {response, result});

import requests
token = "API token"
email = "Previously configured account email"
apiUrl = "https://api.useapi.net/v1/kling/images/upscale"
headers = {
    "Content-Type": "application/json", 
    "Authorization" : f"Bearer {token}"
}
data = {
    "email": email,
    "task_id": "123456789",
    "workId": "987654321"
}
response = requests.post(apiUrl, headers=headers, json=data)
print(response, response.json())