Both methods below use
dreamina-seedance-2-0-260128. You can also use
dreamina-seedance-2-5-260628 with these examples. Model-specific media and output limits still
apply; see Seedance 2.0 and
Seedance 2.5.
Method 1: Create a Group and Asset yourself (recommended)
This method lets you prepare a portrait once and reuse its Asset ID in later generation requests. A Group organizes assets; each uploaded image or video receives its own Asset ID.Step 1: Create an Asset Group
Call Create an asset group:Result.Id as your Group ID. If you already have a group owned by your user in the
current workspace, reuse it instead of creating another. You can find existing groups with
List asset groups. This create-group endpoint
uses GroupType: "AIGC" for Virtual Portrait groups.
Step 2: Add a portrait image or video to the group
Call Create an asset:GroupId with the value from Step 1:
To add a video, set
AssetType to Video and replace URL with the video URL. The endpoint,
response format, and status-checking steps are the same for both media types.
This example uses Moderation.Strategy: "Skip", as in GENGEN’s automatic portrait registration
flow. It is available only where enabled. If the API rejects that option, contact support;
omitting Moderation uses the standard moderation policy. Generation content checks still apply.
Response excerpt:
Result.Id as your Asset ID. This response means preprocessing was accepted; it does
not mean the asset is ready. Repeat this step for additional images or videos, saving each
returned ID. No local file path, browser blob: URL, or Base64 upload is accepted by this flow.
Step 3: Wait for the asset to become Active
In most cases, asset preprocessing returns a result within 2 seconds. It can also fail; check the returned status and error details, and continue only whenResult.Status is Active.
Call Get an asset. This is a POST request:
asset:// prefix:
Use the returned status to decide when to continue, rather than assuming a fixed processing
time. If you uploaded multiple assets, wait for every asset you plan to use to become
Active.
Step 4: Generate with the Asset URI
Prefix the Asset ID withasset:// and call
Create a video task:
id and follow the polling steps below. Requests using only existing
Asset URIs do not need the automatic URL-registration stage. To reuse this portrait in another
video, submit a new generation request with the same Asset URI; you do not need to recreate the
group or re-upload the image while the asset remains available and accessible.
Method 2: Send an HTTPS URL
Step 1: Submit the portrait with your video request
Call:request.json and send it with cURL:
Step 2: Save the returned video task ID
An accepted URL request returns HTTP200 with a response like:
preparingAssets means GENGEN is still preparing the reference media. The returned id is the
video task ID, not an Asset ID. Save the complete value, including its seedance20: or
seedance25: prefix.
Step 3: Poll the same video task
Follow Poll the video task below. The task ID stays the same from asset preparation through video completion; you do not need to obtain or substitute the automatically created Asset IDs.Poll the video task
Both methods finish with a video task ID. Use the same API key that created the video task to call Retrieve a video task:id returned by your generation request. GET has no JSON
body. Poll at a moderate interval, for example every five seconds, and continue while the task
is pending or processing.
A completed Seedance task returns a response like:
outputs.videos[0]. If a compatible response reports succeeded, also
treat that as success. Stop polling on failed, cancelled, or expired; inspect the returned
error for the next action. An HTTP 200 response alone does not mean generation succeeded.
Use a portrait video instead of an image
For Method 1, create an asset withAssetType: "Video", wait for Active, and put its
Asset URI in assets.referenceVideos. For Method 2, put the HTTPS video URL in that field.
Refer to it as Video 1 in the prompt.
For example, the manual video-asset request is:
POST /api/gengen/v1/assets, then poll POST /api/gengen/v1/assets/get with its
returned Asset ID as described above, until its status is Active.