Skip to main content
Use kling/kling-image-o1 with the Comfy Router API. Kling provides the model; Router gives it the shared authentication and request route below.

Quick start

Create a key at platform.comfy.org/profile/api-keys and export it as COMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP. Model ID: kling/kling-image-o1 Endpoint: POST https://api.comfy.org/v2/models/kling/kling-image-o1

Schema

Input

Router has not published an authored input schema for this model yet: GET /v2/models/kling/kling-image-o1/openapi.json returns an open object with x-comfy-input-schema-authored: false. Router forwards the body to Kling unchanged, so Kling’s own API reference is authoritative for the request fields, and nothing is validated server side.

Output

integer
Error code
object
integer
Task creation time, Unix timestamp in milliseconds
string
The deduction units of task
string
Task ID
object
string
Customer-defined task ID
object
object[]
integer
Image Number (0-9)
string (uri)
URL for generated imageFormat: uri
string
Whether the result is a single image or a series of imagesPossible values: single, series
object[]
Series images result list
integer
Series-image sequence number
string (uri)
URL for generated imageFormat: uri
string
Task StatusPossible values: submitted, processing, succeed, failed
string
Task status information, displaying the failure reason when the task fails (such as triggering the content risk control of the platform, etc.)
integer
Task update time, Unix timestamp in milliseconds
string
Error message
string
Request ID

Examples

Output

Before you ship

Save one Idempotency-Key for each call and reuse it for retries. Router can hold the connection for up to 10 minutes. The SDKs handle authentication; raw HTTP clients send the headers themselves. Use X-Comfy-Error-Type to classify a failure. A 422 means Router rejected the input before calling the provider. Download generated assets promptly because result URLs can expire.

Headers

Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.

Using the Router API

Find models, inspect schemas, and retry safely.

Limitations

What Router does not do today, and what to use instead.