Skip to main content
POST
Seedream
Parameters and usage are aligned with the official implementation; for detailed parameters, please refer directly to the official documentation.

1. Overview

The Seedream image generation API uses the OpenAI-style image generation request format and supports text-to-image, image-to-image, and image editing. All four models share the same endpoint; the client only needs to select a model via the model field in the request body.

Supported Models

2. Endpoint and Authentication

Request headers:
{api_domain} is the API domain of your platform. Requests must use POST, and the body must be JSON.

3. Request Parameters

3.1 Common Parameters

string
required
Use a model ID from the table above.
string
required
Image description. Supports both Chinese and English.
string / string[]
Reference image URL or Base64 Data URL. You can pass a single image or an array. The exact number and image limits are subject to the restrictions of the selected model.
string
Use a resolution tier supported by the model or an explicit widthxheight. If omitted, the model default is used.
string
url or b64_json; defaults to url.
string
Only supported by Seedream 5.0 Lite and 5.0 Pro: jpeg or png. Seedream 4.0 and 4.5 always output JPEG; passing output_format will be rejected.
boolean
Whether to add an AI-generated watermark.
boolean
The image endpoint does not support streaming output; do not pass true.

3.2 Model-Specific Parameters

Seedream 5.0 Pro does not support sequential_image_generation or sequential_image_generation_options; passing either field will be rejected. Do not send other models’ specific parameters to Pro.

3.3 Text-to-Image Example

The following request uses Seedream 5.0 Pro as an example. All four models share the same endpoint; when using Seedream 4.0 or 4.5, output_format must be removed, and this field can only be included when using Seedream 5.0 Lite/Pro:

3.4 Image-to-Image Example

image can be a single URL, a single Base64 Data URL, or an array of strings:

3.5 Multi-Image Group Example (4.0, 4.5, and 5.0 Lite only)

The group generation parameters apply to the first three models. Example:
Refer to the upstream protocol of the selected model to confirm the available values and count limits for the group generation parameters.

4. Response

Example of a successful response:
  • When response_format=url, data[].url is returned; when response_format=b64_json, data[].b64_json is returned.
  • Seedream 4.0, 4.5, and 5.0 Lite can return multiple data items in multi-image group mode.
  • Seedream 5.0 Pro returns a single data item in the image generation scenario; when layer decomposition is enabled, it returns multiple data items (one base image + multiple layers), each additionally containing the layer stacking order z_index (0 for the base image), the name name, the description description, and the bounding box bounding_box (with absolute / normalized coordinates; the base image does not return this field).
  • model returns the client model ID used for this request.
  • The validity period of image URLs is determined by the platform and upstream services; download and save the images promptly after receiving the response.

5. Model Limitations

Seedream 4.0 / 4.5 / 5.0 Lite

  • Supports text-to-image, image-to-image, and multi-image group generation.
  • Multi-image groups use sequential_image_generation and its options field.
  • For the number of input images, image size, resolution, and aspect ratio, refer to the upstream documentation of the corresponding model. Seedream 4.0 and 4.5 always output JPEG and do not support the request parameter output_format; Seedream 5.0 Lite supports jpeg and png.

Seedream 5.0 Pro

  • Supports text-to-image, image-to-image from a single image, and multi-image fusion.
  • In the image generation scenario, it returns one successful image. When layer decomposition (layer_decomposition: true) is enabled, it returns one base image and multiple layers (up to 16 layers), in which case data contains multiple items. Multi-image group generation (sequential_image_generation) is not supported.
  • Does not support sequential_image_generation or sequential_image_generation_options.
  • size can be 1K, 1.5K, 2K, or an explicit widthxheight.
  • When explicit width and height are given, the aspect ratio and total pixel count must satisfy the model limitations; the actual dimensions of the output image are determined by data[].size in the response.
  • Supports layer decomposition: when layer_decomposition: true is set, a single input image is decomposed into one base image and up to 16 independently editable layers (each layer is a PNG with an alpha channel). In this scenario, image is required and only one image can be passed; passing multiple images results in an error. Layer decomposition is all-or-nothing: if any layer fails, the entire request fails; partial success is not supported.
  • size rules for layer decomposition: the base image resolution equals size; each layer’s resolution is close to size, but each layer maintains the aspect ratio of its corresponding region in the original image, so the actual pixel counts of the layers differ. This means output images from the same request may fall into different pixel-based pricing tiers. size can be 1K, 1.5K, 2K, or auto, and defaults to auto.

6. Billing and Usage

  • 4.0, 4.5, and 5.0 Lite are billed by the number of successfully generated images; for multi-image group generation, billing is based on the actual number of successful outputs.
  • 5.0 Pro is billed by successfully output images; with multi-image input, the first reference image is free and additional reference images are metered separately; different output sizes correspond to different pricing tiers. When layer decomposition is enabled, the base image and each layer each count as one successful output image, and each is billed separately according to the pricing tier its data[].size pixel count falls into (for example, the base image may be in a high-pixel tier while some layers are in lower-pixel tiers); the final bill is the sum of the quantities across all tiers.
  • The usage unit is image or item.
  • For exact pricing, refer to the product pricing page of your platform.

7. Troubleshooting