DashScope (Alibaba Bailian) video models use the native Bailian protocol, transparently forwarded: the {model, input, parameters} body, task envelope and status values match the official API. Available models (e.g. wan2.6-t2v, happyhorse-1.0) come from List Models (protocols contains dashscope).
Authorizations
AuthorizationstringRequired
Bearer Token authentication; no Alibaba Cloud AK needed.
Authorization: Bearer YOUR_API_KEYSubmit a task
Two submission endpoints (per model, matching Bailian):
POST /api/v1/services/aigc/video-generation/video-synthesis # text-to-videoPOST /api/v1/services/aigc/image2video/video-synthesis # image-to-videoRequest headers
| Header | Required | Description |
|---|---|---|
Authorization |
Yes | Bearer YOUR_API_KEY |
Content-Type |
Yes | application/json |
X-DashScope-Async |
Yes | Must be enable. Official Bailian semantics: HTTP calls are async-only; omitting it returns current user api does not support synchronous calls |
Native Bailian body:
model(required)input:prompt,img_url(first frame for image-to-video), etc., per modelparameters:size/duration/seedetc., per the official Bailian docs
Poll a task
GET /api/v1/tasks/{task_id}output.task_status: PENDING / RUNNING / SUCCEEDED / FAILED / CANCELED. On success the result (e.g. video_url) is in output; URL lifetime per Bailian — download promptly. Query / cancel endpoints only require the Authorization header.
Cancel a task
POST /api/v1/tasks/{task_id}/cancelOnly PENDING tasks can be cancelled (Bailian semantics).
Notes
- Query / cancel with the same API Key used for submission; 7-day query window, then 404
task_not_found - Poll every 5–10 seconds until a terminal state
- Service/action combinations outside the whitelist return 404
unsupported_endpoint input/parametersfields follow the official Bailian docs; no field rewriting