Skip to main content
POST
Reference-to-Video: create a video task with up to 9 reference images to preserve the subject
You can debug directly in the Playground on the right: fill in Authorization with Bearer sk-your-api-key, set model / input.media / parameters, then send the request. A successful submission returns a task_id; see below for polling and downloading.
This page covers the create endpoint for happyhorse-1.1-r2v (Reference-to-Video): provide reference images, and the model preserves the subjects and scene features in them. HappyHorse-r2v supports up to 9 reference images, giving stronger subject consistency in multi-reference scenarios. For the complete async flow, see the HappyHorse Overview.
  • happyhorse-1.1-r2v supports up to 9 reference_image entries (more than Wan2.7-r2v’s combined ≤5).
  • input.media is required, and the media url must be a public https link that can be fetched directly via GET.
  • The create request goes to /wan/api/v1/... with X-DashScope-Async: enable; do not use /v1/videos.

Code Examples

Parameter and Media Quick Reference

media[] Values

Response Format

After submission, poll GET /v1/tasks/{task_id} until completed, then download the mp4 from result_url (without the Authorization header, expires in 24 hours). See the full polling loop in HappyHorse Overview · Async Call Flow.

Authorizations

Authorization
string
header
required

The API Key obtained from the APIYI Console

Headers

X-DashScope-Async
enum<string>
default:enable
required

Async processing switch, must be set to enable

Available options:
enable

Body

application/json
model
enum<string>
default:happyhorse-1.1-r2v
required

Model ID, fixed to happyhorse-1.1-r2v for Reference-to-Video

Available options:
happyhorse-1.1-r2v
input
object
required
parameters
object

Response

Task submitted, returns task_id and PENDING status

output
object
request_id
string

Unique request identifier

Example:

"..."