---
title: "Run MiniMax H3 Max Camera Controls (minimax-h3-max-camera-controls)"
method: POST
path: "/models/minimax-h3-max-camera-controls"
tags: ["Run a model"]
---

# Run MiniMax H3 Max Camera Controls (minimax-h3-max-camera-controls)

`POST /models/minimax-h3-max-camera-controls`

## Request

- Base URL: `https://api.hedra.com/v3`
- URL: `https://api.hedra.com/v3/models/minimax-h3-max-camera-controls`
- Auth: one of:
  - API key in header `Authorization`
  - HTTP bearer

Orbit, tilt, and dolly a camera through a single image along a path you key-frame in 3D.

Submits an asynchronous job and returns `202` with a job id. Fetch the result at `GET /v3/jobs/{job_id}` — each item in its `outputs[]` follows the `OutputItem` schema — or track progress via `GET /v3/jobs/{job_id}/status` / the SSE stream at `GET /v3/jobs/{job_id}/stream`.

## Headers

- `Idempotency-Key` string

## Request body

- SubmitBodyMinimaxH3MaxCameraControls
  - `input` InputMinimaxH3MaxCameraControls, required: Model-specific inputs for `minimax-h3-max-camera-controls`.
    - `num_outputs` 1: Number of outputs generated per job. Only 1 is supported.
    - `prompt` string, required: Generation prompt. From 1 to 50000 characters.
    - `resolution` '480p' | '768p', required: Output resolution.
    - `duration_ms` 5000 | 6000 | 7000 | 8000 | 9000 | 10000 | 11000 | 12000 | 13000 | 14000 | 15000, required: Duration in ms.
    - `start_image` union, required: Start frame. From 256px to 5760px on each side, with an aspect ratio from 0.4 to 2.5, and at most 30 MB.
      - object: A file uploaded via POST /v3/files, referenced by the returned url.
        - `source` 'url', required
        - `url` string, uri, required: A URL returned by POST /v3/files.
      - object: An existing asset you own, referenced by its id.
        - `source` 'asset', required
        - `asset_id` string, required: The asset's id (`asset_<uuid>`), as issued by the server — a completed generation publishes one per output as `outputs[].asset_id`. Do not construct one or derive it from any other id.
    - `camera_trajectory` object[], required: Camera path through the scene, as poses ordered by strictly increasing `time`. The first pose holds until its `time` and the last holds to the end of the clip; the camera interpolates between them. `time` runs 0 (start) to 1 (end), `azimuth` is the horizontal angle around the subject in degrees, `elevation` the vertical angle in degrees from -90 to 90, and `distance` the distance from the subject in scene units (above 0; 1 is where the input frame sits). Consecutive azimuths may travel at most 32 full turns in total. 2 to 12 items.
      - `time` number, required: When this pose applies, from 0 at the start to 1 at the end.
      - `azimuth` number, required: Horizontal camera angle around the subject, in degrees.
      - `elevation` number, required: Vertical camera angle around the subject, in degrees.
      - `distance` number, required: Camera distance from the subject, in normalized scene units.
  - `webhook` string, uri, nullable: URL to receive a signed completion webhook.

## Response `202`

Accepted. The job runs asynchronously; poll `status_url` / `result_url` from the ack.

- SubmitResponse
  - `job_id` string, required: This job's id — server-issued, and opaque.
  - `model` string, required: The resolved model id this job runs on.
  - `status` 'IN_QUEUE' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED', required: The four states a job can be in.
  - `status_url` string, required: Path of this job's status monitor: poll GET /v3/jobs/{job_id}/status for status, progress, and the estimated completion time.
  - `result_url` string, required: Path of the job resource itself: GET /v3/jobs/{job_id} returns the result envelope, including the outputs once it completes. Also the value of this response's `Location` header.
  - `estimated_completion_at` string, date-time, nullable: ISO-8601 instant this job is estimated to finish, as of this response. Null when no estimate is available yet, and when the job has already finished. The estimate can change while the job runs: poll `GET /v3/jobs/{job_id}/status` for the current one.

## Other responses

- `400`: Invalid or failed-validation request.
- `401`: Authentication failed: missing, malformed, or invalid credentials.
- `402`: The API wallet cannot cover this request. `error.billing` carries the balance, the price, and where to add funds.
- `403`: Insufficient scope or plan.
- `404`: Resource not found.
- `422`: Moderation refused the request's content.
- `429`: Rate limit exceeded.
- `500`: Internal error.

## Changes

- **2026-10-16** `06692d16e78a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/hedra-labs/apis/hedra-api/changes/models/minimax-h3-max-camera-controls/post.md)

---

[API](https://skmtc.dev/hedra-labs/apis/hedra-api.md) - [All operations](https://skmtc.dev/hedra-labs/apis/hedra-api/llms.txt) - [OpenAPI document](https://skmtc.dev/hedra-labs/apis/hedra-api/revisions/6ef35a11cefe?raw)