Text 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-Max.
- MiniMax-H3: supports text-to-video, image-to-video (first / last frame), and multimodal reference-to-video; resolution 768P / 2K, duration 4 ~ 15 seconds.
- MiniMax-H3-Max: fast generation version. Supports text-to-video and image-to-video (first / last frame) only; multimodal references (reference image / reference video / reference audio) are not supported; resolution 480P / 768P, 2K is not supported; duration 5 ~ 15 seconds.
MiniMax-H3, MiniMax-H3-Max 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):
Text-to-video: a single text element only.
Video resolution. Available values: 480P, 768P, 2K.
- MiniMax-H3: supports 768P and 2K.
- MiniMax-H3-Max: supports 480P and 768P (default 768P, 2K is not supported).
480P, 768P, 2K Video duration in seconds. Required, integer.
- MiniMax-H3: 4 ~ 15 seconds.
- MiniMax-H3-Max: 5 ~ 15 seconds (4 seconds is not supported).
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.
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.