Kwaivgi Kling Image V4.0 Long Image API Documentation
Playground
Try it on WaveSpeedAI!Kling Image 4.0 Long Image creates long-form vertical images from product photos or text prompts, making it suitable for ecommerce product detail pages, landing pages, promotional layouts, and web design workflows. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.
Features
Kling Image 4.0 Long Image generates a single tall image for an ecommerce product detail page or a webpage design concept. Use product photos and a brief to plan an ecommerce layout, or describe a website concept with optional reference images.
Why Choose This?
- Two page types — Choose an ecommerce product page or a webpage design.
- Product references — Provide 1–3 product photos for ecommerce pages.
- Ecommerce length options — Choose short, medium, or long page layouts.
- Resolution options — Select a 1K or 2K page-width tier.
Parameters
| Parameter | Required | Description |
|---|---|---|
| prompt | Yes | Describe the page content, visual style, and section priorities. Refer to inputs as <<<image_1>>>, <<<image_2>>>, and so on. |
| page_type | Yes | ecommerce or webpage. Default: ecommerce. |
| images | Optional | 1–3 product image URLs are required for ecommerce. For webpage, up to 3 reference images are optional. |
| length | No | Ecommerce only: short (about 2–5 sections), medium (about 6–10), or long (about 11–18). Default: medium. Ignored for webpage. |
| resolution | No | Page-width tier: 1k or 2k. Default: 1k. |
| output_format | No | Output format: png, jpeg, or webp. Default: png. |
How to Use
- Select a page type — Choose
ecommercefor a product detail page orwebpagefor a website concept. - Add images — Provide 1–3 product photos for ecommerce, or optional webpage references.
- Write the page brief — Describe the content, section order, requested text, and visual style.
- Choose output settings — Set the resolution and format. For ecommerce, also choose the page length.
- Submit and review — Inspect the generated page image and its text.
Pricing
Pricing is based on page_type, resolution, and, for ecommerce pages, length.
| Page type | Length | 1K price | 2K price |
|---|---|---|---|
| Ecommerce | Short | $0.235 | $0.282 |
| Ecommerce | Medium | $0.470 | $0.549 |
| Ecommerce | Long | $0.784 | $0.862 |
| Webpage | Not applicable | $0.549 | $0.596 |
Each input image adds $0.003 per request.
Total price = the selected page rate + input image count × $0.003.
Example Costs
| Configuration | Price |
|---|---|
| Short ecommerce page at 1K + 1 product image | $0.238 |
| Medium ecommerce page at 1K + 1 product image | $0.473 |
| Long ecommerce page at 2K + 3 product images | $0.871 |
| Webpage at 2K, no reference images | $0.596 |
Best Use Cases
- Product page concepts — Draft layouts for product features, specifications, and imagery.
- Landing-page concepts — Explore section order, styling, and visual hierarchy.
- Campaign presentations — Create a long-form visual for design review.
Pro Tips
- List sections in the intended order and identify the most important content.
- Provide concise copy for headings and labels.
- Use product photos that clearly show the features mentioned in the prompt.
Notes
promptandpage_typeare required; ecommerce pages also need 1–3 product images.- Each reference image must be no larger than 30 MB.
- Each request returns one image of a page design, rather than HTML or an interactive website.
- Section counts are approximate, and the generated page height depends on the layout.
- Review generated copy, product details, and layout before use.
Related Models
- Kling Image 4.0 Text-to-Image — Generate images from text prompts.
- Kling Image 4.0 Edit — Generate images guided by reference images and edit instructions.
- Kling Image 4.0 Image Set — Generate related images in one request.
Authentication
For authentication details, please refer to the Authentication Guide.
API Endpoints
Submit Task & Query Result
set -euo pipefail
export WAVESPEED_API_KEY="your-api-key"
REQUEST_BODY=$(cat <<'JSON'
{
"prompt": "A cinematic ocean wave at sunrise, highly detailed",
"page_type": "ecommerce",
"length": "medium",
"resolution": "1k",
"output_format": "png"
}
JSON
)
# 1. Submit the prediction once. Never retry this request automatically:
# a retry after an unclear failure can create a second, billed task.
CHECK='The task may already exist. Check History or the predictions list before submitting again.'
if ! SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
--connect-timeout 10 --max-time 60 \
-X POST "https://api.wavespeed.ai/api/v3/kwaivgi/kling-image-v4.0/long-image" \
-H "Authorization: Bearer ${WAVESPEED_API_KEY}" \
-H "Content-Type: application/json" \
-d "${REQUEST_BODY}"); then
printf 'Submit failed. %s\n' "${CHECK}" >&2
exit 1
fi
TASK=$(printf '%s' "${SUBMIT_RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
PREDICTION_ID=$(printf '%s' "${TASK}" | jq -r '.id // empty')
if [ -z "${PREDICTION_ID}" ]; then
printf 'Submission response did not contain a prediction id. %s\n' "${CHECK}" >&2
exit 1
fi
RESULT_URL="https://api.wavespeed.ai/api/v3/predictions/${PREDICTION_ID}/result"
# 2. Poll until the prediction reaches a final status.
BODY_FILE=$(mktemp)
trap 'rm -f "${BODY_FILE}"' EXIT
while true; do
# Transient errors (429, 5xx) are retried, honoring Retry-After.
HTTP_CODE=$(curl --silent --show-error --fail-with-body \
--connect-timeout 10 --max-time 60 --retry 5 --retry-delay 2 \
--output "${BODY_FILE}" --write-out '%{http_code}' \
"${RESULT_URL}" \
-H "Authorization: Bearer ${WAVESPEED_API_KEY}" || true)
case "${HTTP_CODE}" in
2??) ;;
000|429|5??) # dropped connection or temporary error: keep polling
printf 'Task %s: HTTP %s, polling again in 10s\n' "${PREDICTION_ID}" "${HTTP_CODE}" >&2
sleep 10; continue ;;
*) printf 'Task %s: HTTP %s\n' "${PREDICTION_ID}" "${HTTP_CODE}" >&2
cat "${BODY_FILE}" >&2; exit 1 ;;
esac
RESULT=$(jq 'if type == "object" and has("data") then .data else . end' "${BODY_FILE}")
STATUS=$(printf '%s' "${RESULT}" | jq -r '.status // empty')
case "${STATUS}" in
completed) printf '%s\n' "${RESULT}" | jq '.outputs'; break ;;
failed|cancelled|timeout|deleted)
printf 'Task %s ended with status %s\n' "${PREDICTION_ID}" "${STATUS}" >&2
printf '%s\n' "${RESULT}" | jq . >&2; exit 1 ;;
*) sleep 2 ;;
esac
doneRetry temporary errors only while polling, never the submit request. Errors, retries and timeouts
Parameters
Task Submission Parameters
Request Parameters
| Parameter | Type | Required | Default | Range | Description |
|---|---|---|---|---|---|
| prompt | string | Yes | - | Describe the page: the product and its selling points for an ecommerce page, or the site and its content for a webpage design. Refer to the input images as <<<image_1>>>, <<<image_2>>>, etc. in array order. | |
| page_type | string | Yes | ecommerce | ecommerce, webpage | ecommerce: a product detail page built from your product photos. webpage: a website visual design. |
| images | array<string> | No | - | 0 ~ 3 items | Product photos (1-3, required for an ecommerce page), or optional references (up to 3) for a webpage design. |
| length | string | No | medium | short, medium, long | Length of an ecommerce page: short (about 2-5 sections), medium (about 6-10) or long (about 11-18). Not used for a webpage. |
| resolution | string | No | 1k | 1k, 2k | Output resolution (page width tier). |
| output_format | string | No | png | png, jpeg, webp | Output image format. |
Every model also accepts the global request options enable_sync_mode and enable_base64_output; see their pages for details.
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data.id | string | Unique identifier for the prediction, Task Id |
| data.model | string | Model ID used for the prediction |
| data.outputs | array | Output values, usually URL strings; some models return text strings or structured result objects (empty when status is not completed) |
| data.urls | object | Object containing related API endpoints |
| data.status | string | Task status. completed is successful; failed, cancelled, timeout, and deleted are failure terminal statuses. |
| data.created_at | string | ISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”) |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |
Result Request Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| id | string | Yes | - | Task ID |
Result Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data | object | The prediction data object containing all details |
| data.id | string | Unique identifier for the prediction |
| data.model | string | Model ID used for the prediction |
| data.outputs | array<string | object> | Array of generated outputs (empty when status is not completed). Items are usually URL strings, but may be text strings or structured result objects, depending on the model. |
| data.urls | object | Object containing related API endpoints |
| data.status | string | Status: completed is successful; failed, cancelled, timeout, and deleted are failure terminal statuses |
| data.created_at | string | ISO timestamp of when the request was created |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |