Skip to main content

Overview

HappyHorse is an Alibaba video model for text-to-video, image-to-video, reference-guided video generation, and video editing. Use this page when you are ready to call the API after trying the model in the APIXO playground. HappyHorse outputs video with audio by default. The public API does not expose a switch to fully disable generated audio. For video-edit, use audio_setting to choose automatic audio behavior or preserve the original input audio.

Endpoint and authentication

Base URL:
All requests require your APIXO API key:
Submit requests also require:

Copy-paste async quickstart

This minimal request submits a text-to-video task and returns a taskId.
Successful response:
Save the taskId; you need it to poll for the final video.

Poll for result

Processing response:
Success response:
Failed response:
Parse resultJson after state becomes success:

Request body

Text-to-video

Image-to-video

Reference-to-video

Video edit

Parameters

string
default:"async"
required
Result delivery mode. Use async for polling with statusTask, or callback for webhook delivery.
string
Required when request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.
object
required
HappyHorse input parameters.

Response format

Submit task response

POST /generateTask/happyHorse returns a task ID when the task is accepted:
integer
API status code. 200 means the task was accepted.
string
Human-readable status message.
string
Unique task identifier used with the status endpoint.

Status response fields

string
Unique task identifier.
string
Current task state: processing, success, or failed.
string
JSON string containing generated video URLs in resultUrls. Present when state is success.
string
Machine-readable failure code. Present when state is failed.
string
Human-readable failure message. Present when state is failed.
integer
Task creation timestamp in Unix milliseconds.
integer
Task completion timestamp in Unix milliseconds. Present after completion.
integer
Processing duration in milliseconds. Present after successful completion when available.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
See Webhooks for delivery requirements and retry behavior.

Billing

HappyHorse is billed per second. The selected resolution determines the unit price. Billing formulas: For video-edit, the backend probes the input video duration and does not send a public duration parameter to the provider. Billing uses the input video seconds plus the generated output video seconds; APIXO caps the billable input side at 15 seconds, and the generated output side is billed at the same capped duration. For current route and market comparison pricing, see Pricing.

Latency and polling

HappyHorse tasks are asynchronous. The backend does not enforce a fixed public latency SLA; actual time varies by mode, resolution, duration, prompt complexity, media fetch speed, and provider queue load.
For production workloads, use callback mode to avoid frequent polling for long-running video jobs.
Rate limits and concurrency can vary by account, API key, and route. If you receive 429, slow down requests and retry with backoff. For account-level details, see System APIs.

Errors and troubleshooting

HTTP errors

Task failure codes

Troubleshooting tips

  • Use public, direct, fetchable URLs for image_urls and video_urls.
  • For image-to-video, send exactly one image URL.
  • For reference-to-video, send 1-9 image URLs and include a non-empty prompt.
  • For video-edit, send exactly one video URL. Optional reference images are limited to 5.
  • Use ratio only with text-to-video and reference-to-video.
  • Use duration only with text-to-video, image-to-video, and reference-to-video; video-edit duration is determined from the input video and billed as input video seconds plus output video seconds.
  • Store result URLs promptly if your application needs long-term access.
See Error Codes for the full error reference.