API Reference

Midjourney pan

Use the mj_pan action through this gateway; no model field is required.

POST https://api.tu-zi.com/mj/submit/action
Preview guide

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

Preview guide

Midjourney pan

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/mj/submit/action

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.
  • 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

Action parameters

  • Request fields reuse the marketplace action definition.
  • Replace sample assets, taskId and customId; copy customId from source-task buttons.

Modes and channels

  • /mj defaults to fast; /fast/mj, /relax/mj and /turbo/mj select modes (swap uses its fixed path), subject to token-fixed mode.
  • Keep account, mode and source channel aligned.

Action limitations

  • Video extension uses action=extend, taskId and index 0–3; change uses index 1–4.
  • Actions such as shorten/edits require channel support.

Minimal request example

{
  "taskId": "YOUR_TASK_ID",
  "customId": "COPY_CUSTOM_ID_FROM_SOURCE_TASK_BUTTONS"
}

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.

  1. Poll only when submission returns code 1, 21 or 22 and a result task ID.
  2. Code 21 means an existing task and 22 means queued; poll the returned ID without resubmitting.
  3. At SUCCESS verify imageUrl and the image; stop on FAILURE and inspect failReason.

Body parameters

FieldTypeRequiredDescription / constraints
taskIdstringYesExisting task ID owned by this account; copy it from task retrieval. Form initial value (not an upstream default): "" Example: YOUR_TASK_ID
customIdstringYesCopy the exact customId from the source task buttons; never invent it. Form initial value (not an upstream default): "" Example: COPY_CUSTOM_ID_FROM_SOURCE_TASK_BUTTONS
statestringNoOptional caller-defined state string.

Response fields

FieldTypeDescription / constraints
codeintegerBusiness result code.
resultstringPublic 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

  1. Submission code 1/21/22 indicates acceptance/compatible success; result is a task ID.
  2. Poll GET /mj/task/{task_id}/fetch with the same mode prefix.
  3. Consume imageUrl/videoUrl only on SUCCESS; inspect failReason on FAILURE.
  4. Use bounded backoff.
  5. result is not an image URL.

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.