API Reference

Midjourney U1 button upscale

Upscale the first image using the actual U1 button from a successful source task via /submit/action; requires a source channel that supports button actions.

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 U1 button upscale

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_SOURCE_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

Supported scope

  • This new contract covers ordinary U1 upscaling via /mj/submit/action only.
  • It does not restore /submit/change or establish support for other buttons, 2x/4x, Subtle/Creative, or every channel.

Request and channel

  • Do not add model, action or index.
  • Live evidence used /mj; keep account, token mode and source channel compatible.

Acceptance evidence

The November 8, 2026 sample passed submission, SUCCESS retrieval and PNG decoding; deployment acceptance of this branch remains required.

Minimal request example

{
  "taskId": "YOUR_SOURCE_TASK_ID",
  "customId": "COPY_U1_CUSTOM_ID_FROM_SOURCE_TASK"
}

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
taskIdstringYesSuccessful source task ID owned by the same account; retrieve it and require status=SUCCESS. Example: YOUR_SOURCE_TASK_ID
customIdstringYesCopy the complete customId of the U1 button from that source task; never construct it. Example: COPY_U1_CUSTOM_ID_FROM_SOURCE_TASK
statestringNoOptional caller state; does not provide a general idempotency guarantee.

Response fields

FieldTypeDescription / constraints
codeinteger1/21/22 mean accepted or compatible success; still validate result and retrieve the terminal state.
descriptionstringSubmission description or error reason.
resultstringTask ID for subsequent retrieval, not an image URL.

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

{
  "code": 1,
  "description": "Submit success",
  "result": "YOUR_UPSCALE_TASK_ID"
}

Asynchronous workflow

  1. First GET /mj/task/{source_task_id}/fetch and require SUCCESS and a U1 button.
  2. Submit the actual taskId/customId and persist result immediately.
  3. GET /mj/task/{result}/fetch and verify the matching id.
  4. On SUCCESS require action=UPSCALE and a nonempty imageUrl; on FAILURE inspect failReason.
  5. Poll other states with bounded backoff; investigate a timed-out submission before retrying.
  6. The linked guide includes button selection, polling and resumption.

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.