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/jsoncontent-type: application/json
- Query a Single Task:
action=retrieve, pass inid - Batch Query Tasks:
action=retrieve_batch, can filter by task ID, time range, and pagination conditions - Delete a Task:
action=delete, pass inid - Billing Notes: Task queries are free and will not result in repeated charges
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
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: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: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:
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
Example of a successful deletion:
Failure Responses and Troubleshooting
Failed tasks still return a task object with HTTP 200, and the reason is provided intask.error:
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.
