Version: v1.0.0 | Last Updated: 2026-08-13This platform fully supports the MiniMax Video Generation V2 (MiniMax-H3) official API. Requests and responses are transparently proxied, and all parameter semantics remain consistent with the official API.
The model generates a video from multimodal inputs — text, images, video, and audio — with native 2K output. This is an asynchronous endpoint: on success it returns a task_id, which you poll via the Query Task endpoint.
POST https://platform.dataeyes.ai/hailuo/v2/video_generation
Each element of the content array is typed via type (text / image_url / video_url / audio_url) and its purpose is marked via role. Different combinations map to different generation scenarios:
Scenario
content combination
Text-to-video (t2va)
A single text item
Image-to-video, first frame
text + 1 image_url (role=first_frame; with a single image, role may be omitted and defaults to first frame)
Image-to-video, last frame
text + 1 image_url (role=last_frame)
Image-to-video, first + last frame
text + 2 image_url items (role set to first_frame and last_frame respectively)
Multimodal-reference-to-video (r2va)
text + any combination of reference images (role=reference_image), reference videos (role=reference_video), and reference audio (role=reference_audio)
Image-to-video and multimodal reference are mutually exclusive: once any reference_image / reference_video / reference_audio role appears in content, first_frame / last_frame must not appear (and vice versa).
Defaults to adaptive (the most suitable aspect ratio is chosen automatically from the inputs; the actual ratio is available in the query endpoint's ratio field). Allowed values: adaptive, 21:9, 16:9, 4:3, 1:1, 3:4, 9:16.
Scenario
Rule
Text-to-video
Required, and must not be adaptive
Image-to-video
Determined by the input image; always adaptive. Other values are ignored without error
Multimodal reference
Optional; defaults to adaptive, or specify any concrete ratio
When configured, the MiniMax server first sends a verification request containing a challenge field (echo the challenge back within 3 seconds to complete verification). After verification, every task status change is POSTed to the URL; the payload structure matches the Query Task response. Callback status values: queued / running / succeeded / failed / cancelled.
Billed per second on usage.total_seconds (input reference video seconds + output seconds) at the resolution's unit price; the first 5 input images per task are free, additional images are billed per image. An estimated fee is pre-charged at submission and settled against actual usage on completion (difference charged or refunded); failed tasks are fully refunded. See Overview · Billing & Settlement.