Midjourney
High Variation
Strong variation (varyStrong, Vary (Strong)) on a single upscaled image
POST
| Item | Value |
|---|---|
| action | HIGH_VARIATION |
| Billing | midjourney@high_variation[-speed] |
| Required | task_id + index, or task_id + custom_id |
| Optional | speed, metadata |
Parameters
| Field | Description |
|---|---|
task_id | Task ID returned by this platform (typically the Upscale single-image task) |
index | 1–4; Required when custom_id is omitted; button matching does not use index |
custom_id | Button ID for the corresponding action; when set, skips index auto-matching |
speed | relax / fast / turbo |
metadata | Optional custom metadata |
Auto matching
PreferVary (Strong), then fall back to Make Variations.
Request example
Notes
- Typically call
upscaleon the Imagine grid first, then call this endpoint with the newtask_idreturned by Upscale. - In the current implementation, when
custom_idis omitted,indexis still required even though button matching does not useindex. - Version metadata from the source task is inherited automatically. To price by speed, configure
midjourney@high_variation-fast/midjourney@high_variation-turbo.
Response
On success you receive a new localtask_id. Poll GET /v1/tasks/{task_id} for the result.