Configure Seedance asset pre-filtering with CreateAsset
Configure the pre-filtering strategy for Seedance asset ingestion through Moderation.Strategy in a CreateAsset request.
When you upload an asset for Seedance 2.0 or Seedance 2.5 with CreateAsset, you can use Moderation.Strategy to configure the content pre-filtering strategy for that asset-ingestion request.
Scope
This setting applies only to overseas services that support it. Restrictions involving copyrighted IP, public figures, and other categories still apply.
Before you begin
- You have created an asset group and obtained its
GroupId. - The server can access the asset URL directly.
- You have selected
Image,Video, orAudiobased on the asset content.
Configure CreateAsset
curl -X POST \
'https://api.agtcloud.cn/v1/assets/doubao/?Action=CreateAsset&Version=2024-01-01' \
-H 'Authorization: Bearer your-api-key' \
-H 'Content-Type: application/json' \
--data '{
"GroupId": "group-xxxxxxxx",
"URL": "https://example.com/portrait.png",
"AssetType": "Image",
"Moderation": {
"Strategy": "Skip"
}
}'| Field | Description |
|---|---|
GroupId | ID of the asset group that receives the asset |
URL | Asset URL that the server can access |
AssetType | Asset type, such as Image, Video, or Audio |
Moderation.Strategy | Content pre-filtering strategy for this asset upload; set it to Skip |
Setting Strategy to Skip only adjusts content pre-filtering for this asset upload. It does not disable all review or safety restrictions.
Process the upload result
- After the request is accepted, save
Result.Idfrom the response as the asset ID. - Call Retrieve an asset to check its processing status.
- After the status changes to
Active, reference the asset asasset://ASSET_IDin a video generation request. If the status changes toFailed, correct the asset according to the error information and upload it again.
Notes
Moderation.Strategyaffects only the currentCreateAssetrequest.- The server must be able to access the asset URL directly, and the asset content must match
AssetType. - The asset group, asset, and calling credential should belong to the corresponding account, project, and service region.
- Restrictions involving copyrighted IP, public figures, and other safety categories still apply.