Videos

Video generation is included in the overseas docs structure to match the mature CN navigation, but public endpoint availability must be confirmed from the overseas OpenAPI schema and account configuration.

Request

When video endpoints are enabled, expect an async task model. A create request normally includes a prompt, model, duration, aspect ratio, and optional frame or reference media. All requests use bearer authentication:

Authorization: Bearer YOUR_API_TOKEN

Use only endpoint paths returned by GET /api/openapi.json. Do not copy CN current paths into overseas clients.

Response

Video task responses usually return a task id and status first, then a result video URL after completion. Store the task id and original project id together, because video generation can outlive a browser session.

Billing And Credits

Video tasks can be expensive. Enforce user confirmation for long duration, high resolution, or batch generation. Check Profile before creating batches and pause your queue on insufficient credits.

Errors

Handle invalid prompt, unsupported model, unreachable reference media, insufficient credits, and processing failure. If the schema does not expose video endpoints, show the capability as unavailable instead of attempting hidden routes.