Skip to main content

Try it

Choose an operation in Actions, then enter AK/SK and request fields. Signing is automatic; you can also copy cURL into Postman.

Endpoint and authentication

Replace your asset client’s URL, AK and SK with TensorAI connection details. Use platform-issued asset credentials; videos use an API key for the same account. Use official HMAC-SHA256 (V4) signing, service ark, and default region ap-southeast-1:
Sign at least content-type, host and x-date, sorted by name. X-Date uses UTC YYYYMMDDTHHMMSSZ; clock skew must be within 15 minutes. If sent, X-Content-Sha256 must match the body. The SDK below signs requests automatically.

Supported Actions

All use POST and Version=2024-01-01; fields are case-sensitive. Every Action accepts optional ProjectName; omitted or empty means default, subject to credential permissions. Name allows 64 characters; Description allows 300. Omitted update fields retain their values; empty strings clear them. AssetType accepts Image, Video, Audio. URL must be publicly accessible over HTTP(S). Moderation accepts {"Strategy":"Default"} or {"Strategy":"Skip"}, subject to channel support. The request body limit is 1 MiB; submit a media URL rather than the media file.

Official Python SDK example

Install the SDK and set ASSET_AK / ASSET_SK to platform-issued credentials. ASSET_REGION defaults to ap-southeast-1; update it if your connection details differ.
Replace the example URL with an accessible media URL and save group_id / asset_id. A returned ID means creation was accepted; wait for Status=Active before referencing the asset. Processing means it is being prepared; inspect Error on Failed. If polling times out, retain the ID and query it later.

Reference assets in videos

Pass a reference in content[] when calling Seedance 2.0 or Seedance 2.5:
For audio and video, use audio_url / video_url with reference_audio / reference_video. The platform checks ownership, project, channel, media type and Active status. Use assets registered under your current account; media in one task must use compatible channels.

Visual verification for real-person groups

Real-person groups require visual verification rather than CreateAssetGroup:
  1. Call CreateVisualValidateSession to obtain H5Link / BytedToken.
  2. Have the end user open H5Link on a camera-enabled device and complete verification.
  3. Poll GetVisualValidateResult with BytedToken; continue while Status=Pending.
  4. Use the resulting GroupId with CreateAsset to register real-person media.
CallbackURL may be omitted or empty; nonempty values must be absolute HTTPS URLs within 2048 characters. A provider may still require this field. Credentials need permission for both visual Actions. Keep session links and tokens private.

Responses and errors

Success: