API Reference

Retrieve a Midjourney task

Retrieve a Midjourney task. The following is this gateway’s public contract.

GET https://api.tu-zi.com/mj/task/{task_id}/fetch

Preview guide

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

# Retrieve a Midjourney task

Retrieve a Midjourney task. The following is this gateway’s public contract.

## Endpoint and authentication

`GET https://api.tu-zi.com/mj/task/{task_id}/fetch`

Transport: json

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

```http
Authorization: Bearer YOUR_API_KEY
```

## Path parameters

| Field | Type | Required | Description / constraints |
| --- | --- | --- | --- |
| task_id | string | Yes | Public task ID returned by this gateway. Example: YOUR_TASK_ID |

## Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

## Code examples

### curl

```bash
curl --request GET 'https://api.tu-zi.com/mj/task/YOUR_TASK_ID/fetch' \
  --header 'Authorization: Bearer YOUR_API_KEY'
```

### python

```python
import json
import os
import requests

url = "https://api.tu-zi.com/mj/task/YOUR_TASK_ID/fetch"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.
```

### javascript

```javascript
// Node.js 20+
const url = "https://api.tu-zi.com/mj/task/YOUR_TASK_ID/fetch";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.
```

## Response fields

| Field | Type | Description / constraints |
| --- | --- | --- |
| id | string | Task ID. |
| status | string | SUCCESS and FAILURE are terminal. |
| progress | string | Progress. |
| imageUrl | string | Image URL on success. |
| failReason | string | Failure reason. |
| buttons[] | object | Follow-up action buttons; copy actual customId values, never invent them. |

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

```json
{
  "id": "task_example",
  "status": "IN_PROGRESS",
  "progress": "50%"
}
```

## Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.

## Constraints

Preserve /fast/mj, /relax/mj or /turbo/mj when used for submission; a pinned token mode takes precedence. This returns a task object, not the submission {code,result} envelope.

## Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-relay-midjourney-fetch

This export contains documentation and examples only, without real credentials, account data or user requests.

Updated 2026-11-02 · Reviewed 2026-11-02

Endpoint and authentication

GET https://api.tu-zi.com/mj/task/{task_id}/fetch

Transport: json

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

Authorization: Bearer YOUR_API_KEY

Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

Constraints

Preserve /fast/mj, /relax/mj or /turbo/mj when used for submission; a pinned token mode takes precedence. This returns a task object, not the submission {code,result} envelope.

Path parameters

Field	Type	Required	Description / constraints
task_id	string	Yes	Public task ID returned by this gateway. Example: YOUR_TASK_ID

Response fields

Field	Type	Description / constraints
id	string	Task ID.
status	string	SUCCESS and FAILURE are terminal.
progress	string	Progress.
imageUrl	string	Image URL on success.
failReason	string	Failure reason.
buttons[]	object	Follow-up action buttons; copy actual customId values, never invent them.

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

{
  "id": "task_example",
  "status": "IN_PROGRESS",
  "progress": "50%"
}

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.

Document information and sources

Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-relay-midjourney-fetch

This export contains documentation and examples only, without real credentials, account data or user requests.

Request examples

curl --request GET 'https://api.tu-zi.com/mj/task/YOUR_TASK_ID/fetch' \
  --header 'Authorization: Bearer YOUR_API_KEY'

import json
import os
import requests

url = "https://api.tu-zi.com/mj/task/YOUR_TASK_ID/fetch"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.

// Node.js 20+
const url = "https://api.tu-zi.com/mj/task/YOUR_TASK_ID/fetch";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.