Skip to main content
POST
Create a HappyHorse video from text, reference images, or an opening frame. The API returns a task ID immediately. Store the returned id to poll the task and download the completed video. POST /v1/videos uses multipart/form-data. Send controls as form fields and reference images as input_reference fields, with one HTTPS URL or uploaded image file per field.

Choose an input mode

Reference images guide the subjects and visual details in the video. Send 1–9 publicly accessible HTTPS image URLs or 1–9 image files, repeating input_reference once per image in image order. Use only URLs or only files within this field. Send each URL separately rather than joining URLs with commas. For input_reference, each reference image must be at or below 10 MB with happyhorse-1.0. With happyhorse-1.1, each reference image must be at or below 20 MB. These model limits apply to both image URLs and uploaded files. Use JPEG, JPG, PNG, or WEBP images with a shortest side of at least 400 px. The input_reference upload limit is 20 MiB (20 × 1024 × 1024 bytes) per file. Uploaded images must also meet the model-specific limit above. The request samples at the top of this page show multiple image URLs for HappyHorse 1.1 and multiple file uploads for both models. To set the opening frame, send first_frame once with one publicly accessible HTTPS image URL or one image file. Use this field in a separate request from input_reference.

Set duration and size

Choose an exact WxH value for size from the table below. For first-frame requests, the image determines the framing and aspect ratio, while size selects the output resolution tier.

Task flow

1

Create the task

Send the multipart form request and store the returned id.
2

Poll the task

Call Retrieve a HappyHorse video until status is completed, failed, or error.
3

Download the result

When the task is completed, call Retrieve HappyHorse video content to download the MP4 file.

Authorizations

Authorization
string
header
required

Bearer authentication. Use your CometAPI API key.

Body

multipart/form-data
model
enum<string>
required

HappyHorse model ID for this endpoint.

Available options:
happyhorse-1.0,
happyhorse-1.1
Example:

"happyhorse-1.1"

prompt
string
required

Text prompt that describes the video to generate. For image inputs, describe the motion and visual details to preserve.

Example:

"Use the uploaded reference image as the visual guide. Create a short cinematic shot with gentle natural motion."

seconds
integer
default:5

Requested clip duration in whole seconds. Send an integer from 3 through 15 as a form field. The default is 5.

Required range: 3 <= x <= 15
Example:

3

size
string

Output size as an exact WxH value. Use one of the documented size values for the selected HappyHorse model. For first-frame requests, size selects the resolution tier; the image determines the framing and aspect ratio.

Example:

"1920x1080"

input_reference

Reference images for reference-to-video. Send 1–9 publicly accessible HTTPS image URLs or 1–9 uploaded image files by repeating input_reference once per image. Use only URLs or only files within this field; do not join URLs with commas. Reference images guide subjects and visual details. CometAPI preserves image order. Use JPEG, JPG, PNG, or WEBP images with a shortest side of at least 400 px. Each reference image must be at or below 10 MB for happyhorse-1.0 or 20 MB for happyhorse-1.1. These model limits apply to both image URLs and uploaded files. The input_reference file upload limit is 20 MiB (20 x 1024 x 1024 bytes) per file. Keep uploads within the model limit as well. Keep this field separate from first_frame.

Pattern: ^https://
first_frame

Opening-frame image as one publicly accessible HTTPS URL or one image file. Send this field once, using either a URL or a file. Use JPEG, JPG, PNG, or WEBP images up to 20 MB. Do not combine first_frame with input_reference.

Pattern: ^https://

Response

Task created. Store the returned id and poll GET /v1/videos/{task_id}.

id
string
required

Task ID. Use this value with retrieve and content endpoints.

Example:

"task_example"

object
string
required

Object type. Video tasks return video.

Example:

"video"

model
string
required

Model ID used for the task.

Example:

"happyhorse-1.1"

status
enum<string>
required

Task lifecycle status. Poll until the value is completed, failed, or error.

Available options:
queued,
in_progress,
completed,
failed,
error
Example:

"queued"

progress
integer
required

Task progress as a coarse percentage.

Required range: 0 <= x <= 100
Example:

0

created_at
integer
required

Task creation time as a Unix timestamp in seconds.

Example:

1779938152

task_id
string

Compatibility alias for id when present.

Example:

"task_example"

completed_at
integer

Task completion time as a Unix timestamp in seconds. This field appears on completed tasks.

Example:

1779938219

video_url
string

Temporary video delivery URL. This field appears on completed tasks.

Example:

"<temporary-video-url>"

error
object

Failure details. This field appears when the task fails.

Last modified on September 9, 2026