Seedance Real-Person And Virtual Human Asset API

The Seedance real-person and virtual human asset APIs are hosted at https://yingtu.ai. All endpoints use a LaoZhang API key for Bearer authentication. A YingTu or Google session and a separate YingTu API key are not required.

Base URL: https://yingtu.aiAPI references:

The YingTu references above define the authoritative request fields, response objects, error codes, and rate limits.

Capability Status

Capability	Status	Integration path
Virtual human assets	Available	Create a reusable Asset ID from one public HTTPS image
Real-person assets	Available	Complete the official H5 consent and liveness flow before creating the Asset ID
Asset status retrieval	Available	Retrieve with the public `id` until the asset becomes `Active` or `Failed`
Seedance video generation	Available	Add the `asset://...` URI to a video task as a `reference_image`

The represented person must complete the official H5 identity, consent, and liveness checks. A virtual character based on a real person also requires the relevant likeness, voice, name, trademark, and usage rights.

Authentication

Every asset endpoint uses a LaoZhang API key:

Authorization: Bearer <LAOZHANG_API_KEY>
Content-Type: application/json

The caller does not need a YingTu session, Google session, or cookie. The API key validates the LaoZhang API account and available quota. Verification and asset records are bound to the API key that created them, so later retrieval and real-person creation requests must use the same key.

The API key should be read from a server-side environment variable such as LAOZHANG_API_KEY. The complete API key must not appear in browser code, URLs, logs, or support messages.

Endpoint Summary

Virtual Human Assets

Method	Path	Purpose
`POST`	`/api/seedance-assets/virtual-humans`	Create a virtual human asset from a public HTTPS image
`GET`	`/api/seedance-assets/virtual-humans/{id}`	Retrieve asset processing status

Real-Person Assets

Method	Path	Purpose
`POST`	`/api/seedance-assets/real-persons/verifications`	Create an official H5 verification session
`GET`	`/api/seedance-assets/real-persons/verifications/{verification_id}`	Retrieve verification status
`POST`	`/api/seedance-assets/real-persons`	Create the real-person asset after verification
`GET`	`/api/seedance-assets/real-persons/{id}`	Retrieve asset processing status

Virtual Human Asset Integration

Virtual human assets support digital people, brand characters, virtual hosts, and enterprise spokesperson workflows. Submit one public HTTPS image that can be fetched without authentication. Private, loopback, cookie-protected, and sign-in-protected image URLs are rejected.

curl --request POST \
  --url https://yingtu.ai/api/seedance-assets/virtual-humans \
  --header "Authorization: Bearer $LAOZHANG_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "image_url": "https://cdn.example.com/avatar.webp",
    "name": "brand-avatar"
  }'

A successful create response includes a public retrieval id, asset uri, and initial status:

{
  "request_id": "req_01JZEXAMPLE",
  "id": "ast_eyJvcGFxdWUiOiJleGFtcGxlIn0",
  "object": "seedance.asset",
  "kind": "virtual_human",
  "name": "brand-avatar",
  "status": "Processing",
  "uri": "asset://asset-20260729-example"
}

Use id to retrieve asset status from YingTu. Use uri in the Seedance video task. Both values must be preserved exactly. Internal identifiers must not be constructed or decoded from the examples.

Real-Person Asset Integration

Real-person assets add a consent and liveness step before asset creation. The API caller can initiate this flow inside its own product, but the verification_url must be delivered to the represented person.

Create a verification session

Call POST /api/seedance-assets/real-persons/verifications with an HTTPS callback_url. The optional language is zh, en, or zh-Hant; the default is zh.

Have the represented person complete verification

Securely deliver the one-time verification_url to that person. It expires after 30 minutes and must not be logged or stored long term.

Retrieve the verification result

Read verification_id from the callback and retrieve its status. A pending retrieval still returns HTTP 200. Create the asset only after the status is verified.

Create and retrieve the real-person asset

Submit a public HTTPS URL for a clear front-facing image of the same person. Retrieve the returned public id until the asset becomes Active.

Create the verification session:

curl --request POST \
  --url https://yingtu.ai/api/seedance-assets/real-persons/verifications \
  --header "Authorization: Bearer $LAOZHANG_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "callback_url": "https://customer.example.com/seedance/verified",
    "language": "en"
  }'

Create the real-person asset after verification:

curl --request POST \
  --url https://yingtu.ai/api/seedance-assets/real-persons \
  --header "Authorization: Bearer $LAOZHANG_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "verification_id": "ver_eyJvcGFxdWUiOiJleGFtcGxlIn0",
    "image_url": "https://cdn.example.com/presenter.webp",
    "name": "presenter-a"
  }'

An ordinary image_url cannot replace the dedicated real-person asset flow. Workflows that preserve a real identity or person consistency must first complete verification and obtain an Active real-person asset URI.

Retrieve Asset Status

Both asset types use the public id from the create response. For example:

curl --request GET \
  --url https://yingtu.ai/api/seedance-assets/virtual-humans/ast_eyJvcGFxdWUiOiJleGFtcGxlIn0 \
  --header "Authorization: Bearer $LAOZHANG_API_KEY"

Status	Meaning	Next action
`Processing`	The upstream service is processing the asset	Retrieve again later; the asset cannot be submitted to a video task
`Active`	The asset is usable	Add its `asset://...` URI to Seedance
`Failed`	Asset processing failed	Inspect `failure`, correct the image or authorization issue, and recreate

A failed asset-processing result may still use HTTP 200 with status=Failed and a failure object. Do not treat the HTTP status alone as proof that an asset is ready.

Reference Assets In A Seedance Video Task

After the real-person or virtual human asset becomes Active, add its complete asset://... URI to content as a reference_image. Video generation continues through the LaoZhang Seedance 2.0 Video Generation API:

{
  "model": "doubao-seedance-2-0-260128",
  "content": [
    {
      "type": "text",
      "text": "A real presenter introduces the product while a virtual host responds beside them. The camera slowly pushes in."
    },
    {
      "type": "image_url",
      "image_url": {
        "url": "asset://asset-real-person-example"
      },
      "role": "reference_image"
    },
    {
      "type": "image_url",
      "image_url": {
        "url": "asset://asset-virtual-human-example"
      },
      "role": "reference_image"
    }
  ],
  "ratio": "16:9",
  "duration": 4,
  "resolution": "720p",
  "watermark": false,
  "generate_audio": true
}

Asset creation and retrieval use https://yingtu.ai/api/seedance-assets/.... Video task creation and result retrieval continue to use https://api2.laozhang.ai/seedance/api/v3/.... The two domains serve different steps, but both use the LaoZhang API key.

Limits, Errors, And Acceptance

Each API key can make up to 12 create-operation POST requests per hour. Asset-status GET requests are not counted. On 429, wait for Retry-After.
A real-person verification link is valid for 30 minutes. An expired session returns 410 verification_expired and must be recreated.
Creating a real-person asset while verification is still pending returns 409 verification_pending.
403 capability_unavailable means the server-side account does not have private portrait-asset entitlement. Changing the image does not resolve this error.
Every success and error response includes request_id. Support diagnostics should include this value but must not include the complete API key.
Integration acceptance requires an Active retrieval result and successful use of the returned asset://... URI in a Seedance task.

Getting Started

Core API

Text APIs

Video Generation APIs

Image Generation APIs

AI Understanding

Seedance Real-Person And Virtual Human Asset API

Capability Status

Authentication

Endpoint Summary

Virtual Human Assets

Real-Person Assets

Virtual Human Asset Integration

Real-Person Asset Integration

Retrieve Asset Status

Reference Assets In A Seedance Video Task

Limits, Errors, And Acceptance

​Capability Status

​Authentication

​Endpoint Summary

​Virtual Human Assets

​Real-Person Assets

​Virtual Human Asset Integration

​Real-Person Asset Integration

​Retrieve Asset Status

​Reference Assets In A Seedance Video Task

​Limits, Errors, And Acceptance

​Related Documentation

Capability Status

Authentication

Endpoint Summary

Virtual Human Assets

Real-Person Assets

Virtual Human Asset Integration

Real-Person Asset Integration

Retrieve Asset Status

Reference Assets In A Seedance Video Task

Limits, Errors, And Acceptance

Related Documentation