API method

Midjourney variations via API

Updated November 4, 2026

Button → method

Each of them also takes prompt, but it only matters when the account is in Remix mode.

Request

Base URL is https://api.userapi.ai. Every request needs two headers, api-key and Content-Type: application/json.

{
  "hash": "6794f6ef-866a-4bc3-b0bc-7b28ec010d1b",
  "choice": 1,
  "prompt": "new prompt if in remix mode",
  "webhook_url": "https://example.com/variation/webhook-url",
  "webhook_type": "result"
}

Parameters

What comes back

The response is just the task hash, e.g. {"hash": "ed162774-9244-4038-bdf1-801b033809ec"}. The finished task is what you later get from GET /midjourney/v2/status?hash=… or in the webhook:

{
  "account_hash": "a7d44910-88a6-4673-acc8-d60ffc3479a6",
  "hash": "c688a245-3964-4286-9572-d6c7e22f589a",
  "choice": 3,
  "type": "variation",
  "progress": 100,
  "status": "done",
  "result": {
    "url": "https://cdn.discordapp.com/...515a41ad678f.png",
    "proxy_url": "https://media.discordapp.net/...515a41ad678f.png",
    "filename": "...-515a41ad678f.png",
    "content_type": "image/png",
    "width": 2048,
    "height": 2048,
    "size": 7003237
  },
  "status_reason": null,
  "created_at": "2006-01-02T15:04:05+00:00"
}

No account_hash here: variations are made by the same Discord account that generated the original.

Example with cURL

1. Grid

curl -X POST https://api.userapi.ai/midjourney/v2/imagine \
  -H "Content-Type: application/json" \
  -H "api-key: $USERAPI_KEY" \
  -d '{"prompt": "a robot barista making latte art"}'

2. V3

curl "https://api.userapi.ai/midjourney/v2/status?hash=IMAGINE_HASH" \
  -H "api-key: $USERAPI_KEY"

curl -X POST https://api.userapi.ai/midjourney/v2/variation \
  -H "Content-Type: application/json" \
  -H "api-key: $USERAPI_KEY" \
  -d '{"hash": "IMAGINE_HASH", "choice": 3}'

3. Or 🔄 for the whole grid

curl -X POST https://api.userapi.ai/midjourney/v2/reroll \
  -H "Content-Type: application/json" \
  -H "api-key: $USERAPI_KEY" \
  -d '{"hash": "IMAGINE_HASH"}'

4. Vary (Subtle) on an upscaled picture

curl -X POST https://api.userapi.ai/midjourney/v2/upscale \
  -H "Content-Type: application/json" \
  -H "api-key: $USERAPI_KEY" \
  -d '{"hash": "IMAGINE_HASH", "choice": 3}'

curl -X POST https://api.userapi.ai/midjourney/v2/vary-subtle \
  -H "Content-Type: application/json" \
  -H "api-key: $USERAPI_KEY" \
  -d '{"hash": "UPSCALE_HASH"}'

Wrappers for Python, Node.js and PHP are on separate pages. If you'd rather not write code, the same methods are available in n8n and Make. This method in the documentation.

Vary (Subtle) and Vary (Strong)

{
  "hash": "6794f6ef-856a-4bc3-b0bc-7b28ec010d1b",
  "prompt": "new prompt if in remix mode",
  "webhook_url": "https://example.com/vary-subtle/webhook-url",
  "webhook_type": "result"
}

Both work on an upscale, not on a grid. Subtle changes small details, Strong changes the picture noticeably more.

Reroll

The 🔄 button: the same prompt is generated again. Send the task hash, and in Remix mode also a new prompt.

Remix

When Remix is on, variation, vary-subtle, vary-strong, reroll and pan use the prompt you send. This is how you keep the composition and change the details. Remix is set per Discord account, with the prefer method:

{
  "account_hash": "6794f6ef-866a-4bc3-b0bc-7b28ec010d1b",
  "choice": "remix",
  "is_async": false
}

prefer toggles the mode, and the new state comes back in result ("on" or "off"). With is_async: false the response waits until the switch is done. The current state is in the is_remix field of GET /discord/info?account_hash=….

Other methods