Skip to main content
POST

Authorizations

Authorization
string
header
required

HTTP: Bearer Auth

  • Security Scheme Type: http
  • HTTP Authorization Scheme: Bearer API_key, used to verify account information, can be found in Account Management>API Keys.

Headers

Content-Type
enum<string>
default:application/json
required

Media type of the request body. Set it to application/json.

Available options:
application/json

Body

application/json
model
enum<string>
required

Model name. Currently available: MiniMax-H3.

Available options:
MiniMax-H3
content
object[]
required

Array of multimodal input describing the information used to generate the video. Each element is distinguished by type (text / image_url / video_url / audio_url) and can be labeled with a role.

Every request must include one non-empty text item (the prompt is required); otherwise a parameter error is returned.

Supported input combinations (corresponding to different generation scenarios):

  • Text-to-video: a single text element only.
  • 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 items with role set to first_frame and last_frame respectively.
  • Reference-to-video: text + any combination of reference images (role=reference_image), reference videos (role=reference_video), and reference audio (role=reference_audio); audio alone is not allowed, at least one reference video or image is required.

Image-to-video and reference-to-video are mutually exclusive: if any reference_image / reference_video / reference_audio role appears in content, then first_frame / last_frame must not appear (and vice versa); the two cannot be mixed.


Input media limits (total request body ≤ 64 MB; use public URLs for large files, avoid Base64)

Image image_url:

Video video_url (reference scenario only):

Audio audio_url (reference scenario only):

resolution
enum<string>
required

Video resolution. Currently available: 2K.

Available options:
2K
duration
enum<integer>
required

Duration of the generated video in seconds. Required, integer. Available values: 4-15.

Available options:
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
14,
15
ratio
enum<string>

Aspect ratio of the generated video. Defaults to adaptive (the most suitable ratio is chosen automatically based on the input; the actual ratio can be read from the ratio field of the query endpoint). Available values: adaptive, 21:9, 16:9, 4:3, 1:1, 3:4, 9:16.

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.

Image-to-video (i2va, content contains a first_frame / last_frame image): the aspect ratio is determined by the input image and ratio is always adaptive; passing another valid value does not error but is ignored and treated as adaptive.

Reference-to-video (r2va, content contains reference_image / reference_video / reference_audio): ratio is optional and defaults to adaptive; you may also explicitly specify any of the concrete ratios above.

Available options:
adaptive,
21:9,
16:9,
4:3,
1:1,
3:4,
9:16
callback_url
string

Callback URL for task status changes. Once configured, the MiniMax server first sends a verification request containing a challenge field (you must return the challenge unchanged within 3 seconds to complete verification); after verification succeeds, it POSTs an update to this URL whenever the task status changes. The push body has the same structure as the response of the Query video generation task endpoint.

Callback status values: queued, running, succeeded, failed, expired.

aigc_watermark
boolean

Whether to add an AIGC watermark to the generated video. Defaults to false.

Response

task_id
string

ID of the video generation task, used to query the task status later.