Kling O3 Photo error codes | Runblob API

Reference every Kling O3 Photo error code, HTTP status, and retry rule. Build robust image pipelines with machine-readable messages and clear recovery.

Errors return a stable code in the message field — handle programmatically using these codes, not the human-readable text.

Error Categories

User Errors

Issues caused by invalid requests or insufficient resources.

INSUFFICIENT_CREDITS

Description: Not enough credits to complete the request

Solution: Add more credits to your account

{
  "success": false,
  "message": "INSUFFICIENT_CREDITS"
}

GENERATION_NOT_FOUND

Description: Generation with specified ID does not exist

Solution: Verify the generation ID is correct

{
  "detail": "Generation not found"
}

INVALID_PARAMETERS

Description: Request parameters are invalid or missing required fields

Solution: Check parameter values and types

{
  "detail": "Validation error: prompt is required"
}

INVALID_IMAGE

Description: One or more input images are not valid

Solution: Ensure you’re uploading valid JPEG, PNG, or WEBP files

{
  "status": "failed",
  "message": "INVALID_IMAGE"
}

IMAGE_INACCESSIBLE

Description: One or more image URLs are inaccessible

Solution: Verify all image URLs are accessible via HTTPS

{
  "status": "failed",
  "message": "IMAGE_INACCESSIBLE"
}

INVALID_RESOLUTION

Description: Invalid resolution specified (must be 1k, 2k, or 4k)

Solution: Use one of the supported resolution values

{
  "detail": "Invalid resolution. Must be 1k, 2k, or 4k"
}

TOO_MANY_IMAGES

Description: More than 10 images provided

Solution: Limit input images to maximum of 10 total

{
  "detail": "Maximum 10 images allowed (URLs + base64 combined)"
}

MIXED_IMAGE_INPUTS

Description: Both images_url and images_base64 provided in the same request

Solution: Use only one image input method per request

{
  "detail": "Cannot mix images_url and images_base64 in one request"
}

Content Errors

Issues with prompt content or uploaded images.

CONTENT_POLICY_VIOLATION

Description: Content violates usage policies

Solution: Modify your prompt to comply with content guidelines

{
  "status": "failed",
  "message": "CONTENT_POLICY_VIOLATION"
}

MODERATION_FAILED

Description: Content rejected by moderation system

Solution: Modify your content to comply with our guidelines

{
  "status": "failed",
  "message": "MODERATION_FAILED"
}

System Errors

Technical issues on RunBlob or service provider side.

TIMEOUT

Description: Task exceeded maximum processing time (15 minutes)

Action: Credits are automatically refunded

{
  "status": "failed",
  "message": "TIMEOUT"
}

TASK_FAILED

Description: Generation failed due to system error

Action: Credits are automatically refunded, try again

{
  "status": "failed",
  "message": "TASK_FAILED"
}

SERVICE_UNAVAILABLE

Description: Service is temporarily unavailable

Action: Wait and retry your request later

{
  "detail": "Service temporarily unavailable"
}

HTTP Status Code Reference

201 · Created

Generation created successfully

200 · OK

Request successful

400 · Bad Request

Invalid parameters or request format

401 · Unauthorized

Invalid or missing API key

402 · Payment Required

Insufficient credits

404 · Not Found

Generation not found

422 · Validation Error

Invalid input format or missing required fields

500 · Internal Server Error

Server-side error

503 · Service Unavailable

Service temporarily unavailable

Common Issues & Solutions

Why is my generation failing immediately?

Possible causes:

• Prompt contains prohibited content
• Invalid image format or corrupted file
• Image URLs are not accessible

Solution: Check webhook payload for specific error code

Generation taking too long?

Normal timeline:

• Simple text-to-image: 1-2 minutes
• With reference images: 2-3 minutes
• 4K resolution: May take longer

If exceeds 5 minutes: Check status endpoint or wait for webhook

Credits deducted but no image?

If generation failed: Credits are automatically refunded within 5 minutes

If successful but no URL: Check the status endpoint - the webhook may have failed to deliver