REST API reference

Virtual-human asset API

Create a private AIGC virtual-human asset. The returned asset:// URI can be used for video generation after the asset becomes Active.

Virtual-human asset APICreate a reusable virtual-human Asset ID from one public HTTPS image URL.Real-person asset APICreate an official H5 verification session, check its result, and create an authorized real-person Asset ID.

Endpoint

Base URL

https://yingtu.ai

POST /api/seedance-assets/virtual-humans

GET /api/seedance-assets/virtual-humans/{id}

Authentication

The caller does not sign in to YingTu or Google. Authenticate with a LaoZhang API key using Authorization: Bearer <LAOZHANG_API_KEY>.

Header	Required	Description
`Authorization`	Yes	LaoZhang API key using Bearer authentication.
`Content-Type`	POST only	Create operations use application/json.

Request

Field	Required	Description
`name`	No	Optional asset name, up to 64 characters.
`image_url`	Yes	Required public HTTPS image URL. The official CreateAsset API accepts URLs only.

Create request

cURL

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"
  }'

HTTP request

POST /api/seedance-assets/virtual-humans
Content-Type: application/json
Authorization: Bearer $LAOZHANG_API_KEY

{
  "image_url": "https://cdn.example.com/avatar.webp",
  "name": "brand-avatar"
}

Response example

HTTP/1.1 202 Accepted
Content-Type: application/json

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

Code examples

JavaScript · Node.js

const response = await fetch("https://yingtu.ai/api/seedance-assets/virtual-humans", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LAOZHANG_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    image_url: "https://cdn.example.com/avatar.webp",
    name: "brand-avatar",
  }),
});

if (!response.ok) throw new Error(await response.text());
console.log(await response.json());

Python · requests

import os
import requests

response = requests.post(
    "https://yingtu.ai/api/seedance-assets/virtual-humans",
    headers={"Authorization": f"Bearer {os.environ['LAOZHANG_API_KEY']}"},
    json={
        "image_url": "https://cdn.example.com/avatar.webp",
        "name": "brand-avatar",
    },
    timeout=60,
)

response.raise_for_status()
print(response.json())

Retrieve asset status

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

Status response

HTTP/1.1 200 OK
Content-Type: application/json

{
	  "request_id": "req_01JZEXAMPLE",
	  "id": "ast_eyJvcGFxdWUiOiJleGFtcGxlIn0",
  "object": "seedance.asset",
  "kind": "virtual_human",
  "status": "Active",
  "uri": "asset://asset-20260729-example",
	  "created_at": "2026-07-29T05:00:00Z",
	  "updated_at": "2026-07-29T05:01:00Z"
}

Failed · HTTP 200

{
  "request_id": "req_01JZEXAMPLE",
  "id": "ast_eyJvcGFxdWUiOiJleGFtcGxlIn0",
  "object": "seedance.asset",
  "kind": "virtual_human",
  "status": "Failed",
  "uri": "asset://asset-20260729-example",
  "failure": {
    "code": "InvalidImage",
    "message": "The image did not pass upstream validation."
  }
}

Errors

HTTP status	Error code	Description	Retryable
400	`invalid_request`	The request body, field, or parameter value is invalid.	No
401	`invalid_api_key`	The API key is missing, invalid, or disabled.	No
403	`resource_not_owned`	The verification or asset is not owned by this API key, or the public ID is invalid.	No
403	`capability_unavailable`	Private portrait-asset entitlement is not enabled for the service account.	No
413	`payload_too_large`	The JSON request body exceeds 16 KB.	No
415	`unsupported_media_type`	A POST request did not use application/json.	No
429	`rate_limit_exceeded`	The API key has reached its request limit.	Yes
500	`internal_error`	The service could not complete the request.	No
502	`upstream_error`	The upstream asset or verification service returned an error.	Yes
503	`authentication_unavailable`	API-key validation is temporarily unavailable.	Yes
503	`service_unavailable`	The asset API server configuration is temporarily unavailable.	Yes

Error object

{
  "error": {
    "code": "invalid_request",
	    "message": "image_url is required.",
    "request_id": "req_01JZEXAMPLE",
    "retryable": false
  }
}

Rate limits and tracing

Each API key can make up to 12 create-operation POST requests per hour; GET status requests are not counted. Upstream entitlement may add limits. A limited request returns 429 with Retry-After in seconds.

Every success and error response includes request_id. Include it in support requests, but never send your complete API key.

X-RateLimit-Limit: <limit>
X-RateLimit-Remaining: <remaining>
X-RateLimit-Reset: <unix-seconds>
Retry-After: <seconds>