Skip to main content
This document introduces the integration and usage of the MiniMax H3 Task Query API. This API is used to query, batch list, or delete asynchronous tasks created by the MiniMax H3 Video Generation API.

Application Process

To use the MiniMax H3 Task Query API, first go to the Ace Data Cloud Console to obtain your API Token and keep it for later use. If you have not logged in or registered yet, you will be automatically redirected to the login page and invited to register and log in. After completion, you will automatically return to the current page. One API Token can call all platform services, with no need to apply separately for each service. Your first application will include free credits for a free trial; when credits are insufficient, you can recharge your general balance in the Console.
📘 Full documentation: MiniMax H3 Task Query API →
When querying a task, you should use the same Token that created the task. It is recommended to save the Token as an environment variable and not write it into source code or commit it to a version repository:

API Overview

  • Base URL: https://api.acedata.cloud
  • Endpoint: POST /minimax/tasks
  • Authentication Method: Include authorization: Bearer {token} in the HTTP Header
  • Request Headers:
    • accept: application/json
    • content-type: application/json
  • Query a Single Task: action=retrieve, pass in id
  • Batch Query Tasks: action=retrieve_batch, can filter by task ID, time range, and pagination conditions
  • Delete a Task: action=delete, pass in id
  • Billing Notes: Task queries are free and will not result in repeated charges
You must save the task_id after creating a video. It is recommended to query approximately every 10 seconds until the task enters a terminal state.

Request Parameters

The purposes of the three actions are as follows:

Query a Single Task

Below is the response from a real successful task:
Open the real video result of this task

Task Status

succeeded, failed, and cancelled are all terminal states. Do not continue polling after entering a terminal state.

task Response Fields

Complete Python Polling Example

The following code reads the Token from an environment variable, creates a task, and queries it every 10 seconds:
Production environments should set an overall timeout for polling and use exponential backoff for 429 and temporary 5xx responses. A network timeout does not mean generation has failed; you can continue querying using the same task_id.

Batch Querying

Specify multiple task IDs:
List tasks by time range with pagination:
The items in the batch response use the same task fields as a single-task query, and total is the total number of tasks matching the filter criteria:
The task query window covers the most recent 7 days. A task_id beyond this window may return an invalid task; business systems should save the ID when creating a task and promptly persist the result URL after success.

Cancel or Delete a Task

The action depends on the task’s current status: Example of a successful deletion:
Deleting a task record does not reverse charges that have already been incurred, nor does it guarantee that saved video copies will be deleted at the same time.

Failure Responses and Troubleshooting

Failed tasks still return a task object with HTTP 200, and the reason is provided in task.error:
When the API itself returns 400, check the action and condition parameters. 401 indicates an invalid Token, 429 indicates that queries are too frequent, and 500 indicates that the service is temporarily unavailable. Failed generation tasks are not billed; successful tasks are charged based on the final usage record.