Skip to main content
POST
This endpoint only returns an enhanced video prompt. It does not create a video generation task.
H3-Context-IR deeply interprets multimodal context across text, images, audio, and video. It analyzes relationships among the inputs and between those inputs and the intended output, performs complex reasoning, and converts that understanding into a structured representation with richer semantic detail while preserving the user’s original intent as much as possible.
H3-Context-IR is a complex system and its implementation is not open sourced. This API can be used both to validate the official Full 2K-Workflow results and in production workflows.
After creating the task, use Query Task or List Tasks. H3-Context-IR tasks have task_type=h3_context_ir; when the task succeeds, retrieve the enhanced prompt from content.prompt.

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

Request parameters for creating an H3-Context-IR task.

model
enum<string>
required

Model name. Currently available: MiniMax-H3.

Available options:
MiniMax-H3
content
object[]
required

Array of multimodal context describing the intended video and the relationships among the inputs. 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):

duration
enum<integer>
required

Target video duration 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 target video. Defaults to adaptive. 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 Task endpoint.

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

Response

The create endpoint returns a task_id. Use this task_id with the Query Task endpoint to retrieve the task status and result. When the task succeeds, retrieve the enhanced prompt from content.prompt.

Successful Query Task response example

task_id
string

ID of the task, used to query the task status and result later.