Recommended: use public URLs directly
The asset library is not a required step for most video requests. Keep your existing URL-based flow:
- Include publicly accessible asset URLs directly in the video request.
- The platform automatically handles any asset review required for that request.
- The request is passed through in the native protocol without pre-creating a group or obtaining an asset ID.
Open the Seedance video integration guide →
When the Assets API is useful
Use it only when your workflow explicitly depends on asset IDs, for example:
- The same asset is reused at scale or over a long period and needs a stable ID.
- Your existing system already uses the Volcano Assets API and you want a low-change migration.
- You need API-based lifecycle management for groups and assets, including list, update, and delete operations.
Use the official Volcano API definition
Except for authentication and the request address, Actions, versions, request parameters, response fields, and statuses follow the official Assets API. This site provides a compatible passthrough endpoint and does not redefine the API.
BytePlus ModelArk: Assets API reference ↗
BytePlus ModelArk: private real-person assets guide ↗
Authentication on this site
Replace the official Volcano request address with this site's /ark/ endpoint and authenticate with this site's API key using Bearer Authentication.
POST https://zerofa.ai/ark/?Action=<Action>&Version=2024-01-01
Authorization: Bearer sk-zerofa-xxx
Content-Type: application/jsonCurrent scope
The compatible API covers regular assets and private real-person assets. Identity verification and asset parameters continue to follow the official BytePlus definitions.