happyhorse-1.1-i2v is the first-frame image-to-video model in HappyHorse 1.1. It uses one image to define the starting point of the shot, then uses text to describe subject actions, environmental changes, and camera movement. It is suitable for turning product images, character design images, and scene illustrations into dynamic short videos, supports 3–15-second creation, includes native audio capabilities, and is especially suited to tasks with an established composition that need to further develop visual motion.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
api.acedata.cloudhappyhorse-1.1-i2vInput parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
Native resolutions also include 480P; this platform entry provides 720P and 1080P, and first-frame tasks determine the aspect ratio based on the input image.
The first-frame image directly serves as the starting point of the video, providing a clear basis for product placement, character appearance, and scene composition. Compared with building a shot entirely from text, this approach is better suited to creations with existing visual assets; prompts can focus on changes such as looking up, turning around, wind moving clothing, or a slow push-in, reducing repeated descriptions of the initial image.
This model is designed for first-frame animation and can create short videos around subject actions, environmental dynamics, and camera movement. In practice, it is recommended to first define one primary action, then add lighting, background, and camera-motion requirements, allowing a few seconds of footage to serve a clear purpose rather than cramming a complete story, multiple transitions, and complex interactions into one clip.
Submit the first frame and creation description through POST /happyhorse/videos, explicitly selecting image_to_video and happyhorse-1.1-i2v. When background processing is needed, you can use async to obtain a task ID and query its status, or use callback_url to receive completion results, making it suitable for integration with asset production tools and batch creation workflows.
Input a clearly composed product photo, describe a subtle camera push-in, changes in background lighting and shadows, or movement in the surrounding environment, and generate a short clip for marketing previews. When packaging and brand text need to be highlighted, use restrained motion to preserve visual focus, and check labels, small text, and outlines before delivery to avoid dynamic changes affecting product information.
Use a character design image as the first frame, combined with action descriptions such as looking up, looking back, and clothing movement, to obtain a dynamic storyboard draft. The deliverable can be used to discuss performance direction and shot pacing; if the task becomes one where multiple character images jointly constrain a new scene, choose a reference-image-to-video model instead of continuing to add first-frame inputs.
Start with a landscape image or scene illustration, describe the movement of water, leaves, clouds, and the camera, and create a short atmospheric shot. When producing vertical content, first prepare a vertically composed image so the aspect ratio continues from the first frame; after completion, obtain the video URL, download the assets, and enter the editing workflow to combine them into longer content.
If you already have an image that needs to serve as the opening frame, choose happyhorse-1.1-i2v; if you only have a text script, choose happyhorse-1.1-t2v; if multiple images are needed to constrain characters, props, or style, choose happyhorse-1.1-r2v. The difference is whether the image must become the first frame, rather than merely serving as creative reference. Modifying an existing video belongs to a video-edit task.
The native duration, frame rate, and file format of the 1.1 and 1.0 first-frame models are the same; 1.1 adds a native 480P option. At this entry point, both use 720P or 1080P, so do not assume speed or image-quality improvements based on the version number alone. For new first-frame tasks, 1.1 is available; if you must specify the ending frame or connect long shots, choose a model that explicitly supports first-and-last-frame control.
Prepare a single first-frame image_url, and use a prompt to describe the action; keep the aspect ratio aligned with the input image whenever possible, with no need to pass ratio.
Set model=happyhorse-1.1-i2v and action=image_to_video for /happyhorse/videos. Choose an integer duration of 3–15 seconds and 720P or 1080P, using the input image to determine the starting composition.
Use async or callback_url to integrate background tasks, save the task_id and query /happyhorse/tasks; wait for succeeded before reading video_url, then check the characters, actions, and audio.
Use a portrait photo as the first frame, with the person gently turning their head toward the camera while the background remains stable and their hair and clothing move naturally in a light breeze.
Set an integer duration of 3–15 seconds, and check the face, head, and audio; the platform only provides 720P/1080P, so do not claim that the platform also offers 480P just because it appears in the native table.
Use image_url to submit a publicly accessible image, and set action to image_to_video and model to happyhorse-1.1-i2v. The image will serve as the first video frame; prompt is used to supplement subsequent actions, environmental changes, and camera movement, so there is no need to redescribe all static details.
The output aspect ratio for first-frame tasks should follow the image as closely as possible, with no need to pass ratio separately. To create vertical or square content, prepare a first frame with the corresponding composition first; it is best to leave safe space around product labels, people's heads, and other important elements, then check the actual final video frame.
This model starts generation from a single first-frame image and is not a multi-image reference mode. If you need to combine references for characters, clothing, or props, choose happyhorse-1.1-r2v; if the main goal is to make an existing image start moving without reorganizing the scene, i2v better matches the task structure.
This endpoint offers 720P or 1080P, with durations of whole numbers from 3–15 seconds; native video specifications are 24 fps, MP4, with audio support. Audio generation and precise dubbing control are different capabilities; retaining the original video audio or using reference audio input cannot be used with this model.
You can set async=true, save the returned task_id, and then query through /happyhorse/tasks; you can also provide callback_url to wait for a completion notification. Result statuses include pending, succeeded, and error, and successful results include video_url; do not assume the video has been generated just because you have obtained a task ID.
Choose a development approach or application suited to this model and follow its setup guide.
↗Python SDK Integration Guide
SDK installation, authentication and examples↗TypeScript SDK Integration Guide
SDK installation, authentication and examples
↗This is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs