API Reference
Submit a Midjourney imagine task
Create an image task through the gateway compatibility endpoint.
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
Updated · Reviewed
Endpoint and authentication
POST https://api.tu-zi.com/mj/submit/imagine
Transport: json
Use an inference API key. Examples contain placeholders; read credentials from environment variables.
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Minimal request example
{
"prompt": "A white ceramic cup"
}
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.
Body parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| prompt | string | Yes | Prompt. |
| base64Array | string[] | No | Optional reference image data URLs. |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| code | integer | Business result code. |
| result | string | Public task ID. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"code": 1,
"description": "Submit success",
"result": "task_example"
}
Asynchronous workflow
Save result; GET /mj/task/{task_id}/fetch with the same key. SUCCESS and FAILURE are terminal; read imageUrl on success or failReason on failure. Retain the same fast/relax/turbo prefix when applicable.
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.
兔子API