Create Real-Person Asset

POST /api/volc-user/assets

Add an asset to a verified real-person group. First Create Verification Session, complete verification, and obtain its groupId. Submitted assets still need processing and review.

Authentication

Use a logged-in session Cookie or the Authorization: <access_token> header. Obtain the access token through Generate Access Token. It is different from the sk- key used for model requests.

Request Parameters

Name	Type	Required	Description
groupId	string	Required	Platform group ID obtained from verification by the current user; required for real-person assets
groupType	string	Optional	Explicitly sending LivenessFace is recommended; if omitted, the specified group determines the type
url	string	Required	Public asset URL accessible upstream; real-person assets do not support multipart file or Base64 uploads
assetType	string	Required	Image, Video, or Audio; usability depends on upstream review and the chosen video model
name	string	Optional	Asset name
remark	string	Optional	Platform-only remark; not forwarded upstream

Request Example

POST /api/volc-user/assets
Authorization: <access_token>
Content-Type: application/json

{
  "groupId": "group-example",
  "groupType": "LivenessFace",
  "url": "https://example.com/portrait.jpg",
  "assetType": "Image",
  "name": "Front Portrait",
  "remark": "external-asset-001"
}

Response Fields (200)

Name	Type	Description
success	boolean	Business success flag; check it even for HTTP 200
message	string	Message; empty on success
data	object	Response data on success
data.id	string	Platform resource ID for this operation

Response Example

{
  "success": true,
  "message": "",
  "data": {
    "id": "asset-example"
  }
}

Send JSON fields at the top level without a body wrapper. Success only means the asset has been created. Query Real-Person Asset Detail and wait for status=Active and assetStatus=1 before video generation. Content must meet the relevant verification and upstream review requirements.