API Reference

Retrieve Midjourney tasks in a batch

Retrieve Midjourney tasks in a batch; the contract below follows this gateway implementation.

POST https://api.tu-zi.com/mj/task/list-by-condition
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Retrieve Midjourney tasks in a batch

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/mj/task/list-by-condition

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Before calling

  • Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
  • Replace resource placeholders YOUR_TASK_ID: obtain task/request IDs from the same account's real responses and use provider versions/buttons documented by the linked protocol. Do not send placeholders.
  • Resource IDs such as 123 are examples. Read real IDs from your own list endpoint before retrieving or modifying them; batch operations also require owned IDs.
  • Use an inference key created on this site's token page. Set the API_KEY environment variable or replace YOUR_API_KEY, as shown in the selected example.

Constraints

  • Only matching tasks owned by the account are returned.
  • Not every input ID or input ordering is guaranteed; correlate by id.

Minimal request example

{
  "ids": [
    "YOUR_TASK_ID"
  ]
}

Confirming success

Check HTTP status, the business status in the body and the required result fields. Do not rely only on HTTP 200 or the script exit code.

Body parameters

FieldTypeRequiredDescription / constraints
idsarrayYesTask IDs owned by the current gateway account.

Response fields

FieldTypeDescription / constraints
[]arrayDirect task array, not wrapped in data; no matches yields [].
[].idstringTask ID.
[].statusstringSUCCESS / FAILURE are terminal.
[].imageUrl / [].videoUrlstringResult URLs after success.
[].failReasonstringFailure reason.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

[
  {
    "id": "YOUR_TASK_ID",
    "status": "IN_PROGRESS",
    "progress": "50%"
  }
]

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols.

  • 401/403: check credentials and permissions.
  • 429: classify temporary throttling, exhausted quota, or service capacity failure; only transient failures merit bounded backoff.
  • 5xx: inspect the gateway, upstream, and model/channel configuration.

Error bodies may contain error/message/code depending on the protocol.

  • Use bounded exponential backoff for reads encountering transient errors; fix parameter, authentication, quota, or configuration failures first.
  • Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.