Skip to main content

Midjourney Overview

Midjourney-related APIs use a separate set of routes and are not mixed with OpenAI Images or the unified video task structure.
  • Task submission mainly uses /mj/submit/*
  • Task querying mainly uses /mj/task/*
  • Public images can be accessed via /mj/image/{id}
  • Common operations include IMAGINE, BLEND, DESCRIBE, SHORTEN, MODAL, VIDEO, SWAP_FACE

Task Submission

POST /mj/submit/imagine, /blend, /modal, /describe, /shorten, /video, /upload-discord-images, /insight-face/swap

Task Querying

GET /mj/task/{id}/fetch, POST /mj/task/list-by-condition, GET /mj/task/{id}/image-seed

Route List

Common Return Codes

The common response structure for Midjourney submission APIs is:
Common code meanings:
The current gateway converts some upstream 21 and 22 states into success responses back to the client, so in actual use you may see a successful response while the task is still effectively in an “already exists” or “queued” state. The safe approach is still to take the task ID in result and query the task status again.

Common Field Conventions

  1. Midjourney Task Submission
  2. Midjourney Task Querying
  3. Image Series Overview