Last Frame to Video Generation
Video generation V2 API. Input via multimodal content array (text / image / video / audio). Supports text-to-video, image-to-video (first/last frame), and multimodal reference-to-video with 2K output.
Authorizations
Pass Authorization: Bearer <token> in the request header.
Headers
Media type of the request body. Set to application/json.
application/json Body
Model name. Currently available: MiniMax-H3.
MiniMax-H3 Multimodal input content array describing the information used to generate the video. Each element is distinguished by type (text / image_url / video_url / audio_url) and can be annotated with a role.
Each request must contain a non-empty text item (prompt is required); omission will return a parameter error. Supported input combinations (corresponding to different generation scenarios):
Image-to-video (first frame): text + 1 image_url (role=first_frame or omitted). Image-to-video (last frame): text + 1 image_url (role=last_frame). Image-to-video (first-last frame): text + 2 image_url (roles first_frame and last_frame respectively). Image-to-video and multimodal reference-to-video are mutually exclusive: if any of reference_image / reference_video / reference_audio roles appear in content, first_frame / last_frame must not appear (and vice versa); they cannot be mixed.
Input media limits (total request body size ≤ 64 MB; use public URLs for large files, do not use Base64)
Image image_url:
Video resolution. Currently available: 768P, 2K.
768P, 2K Video duration in seconds. Required, integer. Available: 4~15.
4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 Output video aspect ratio, default adaptive (automatically selects the most suitable aspect ratio based on input; the actual ratio can be retrieved from the ratio field in the query API).
Text-to-video (t2va, content contains only text): ratio is required and cannot be adaptive; available values: 21:9, 16:9, 4:3, 1:1, 3:4, 9:16.
21:9, 16:9, 4:3, 1:1, 3:4, 9:16 Callback notification URL for task status changes. After configuration, the MiniMax server will first send a verification request containing a challenge field (must return the challenge value unchanged within 3 seconds to complete verification). Once verified, whenever the task status changes, a POST push will be sent to this URL, with the push body structure matching the query task API response.
Callback status values: queued, running, succeeded, failed, cancelled.
Whether to add an AIGC watermark to the generated video. Default false.
Response
Returns task_id upon successful creation. Use this task_id to call the query task API to retrieve task status and results.
Query task success response example
Task ID, used to query task status and results.