Skip to main content
POST
/
api
/
v1
/
mj
/
generateVary
Vary
curl --request POST \
  --url https://api.midapi.ai/api/v1/mj/generateVary \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "taskId": "96a5****67tr",
  "imageIndex": 1,
  "waterMark": "my_watermark",
  "callBackUrl": "https://example.com/callback"
}'
{
  "code": 200,
  "msg": "success",
  "data": {
    "taskId": "2182668588ae82da0bc553c07c48ca38"
  }
}

Usage Guide

  • This endpoint is used to create variations of Midjourney generated images
  • Requires providing the taskId from generation task and the image index to vary
  • Supports adding watermarks and callback notifications
  • Enhances image clarity and provides style simulation

Developer Notes

  • imageIndex range is 1-4, corresponding to the 4 generated images
  • Varied images have enhanced clarity and style simulation
  • Recommended to use callback URL in production environments for result notifications

Authorizations

Authorization
string
header
required

All APIs require authentication via Bearer Token.

Get API Key:

  1. Visit API Key Management Page to get your API Key

Usage: Add to request header: Authorization: Bearer YOUR_API_KEY

Note:

  • Keep your API Key secure and do not share it with others
  • If you suspect your API Key has been compromised, reset it immediately in the management page

Body

application/json
taskId
string
required

Task ID returned from MJ generation task

Example:

"96a5****67tr"

imageIndex
integer
required

Image index, range (0, 1, 2, 3) for the 4 generated images

Required range: 0 <= x <= 3
Example:

0

waterMark
string

Watermark identifier (optional)

Example:

"my_watermark"

callBackUrl
string<uri>

Callback URL to receive task completion updates (optional)

📖 Detailed Callback Mechanism: See Midjourney Image Generation Callbacks for callback format, status codes, best practices, and troubleshooting.

Example:

"https://example.com/callback"

Response

Request successful

code
enum<integer>

Response status code

  • 200: Success - Request has been processed successfully
  • 400: Bad Request - Invalid request parameters
  • 401: Unauthorized - Authentication credentials are missing or invalid
  • 402: Insufficient Credits - Account does not have enough credits to perform the operation
  • 404: Not Found - The requested resource or endpoint does not exist
  • 422: Validation Error - The request parameters failed validation checks
  • 429: Rate Limited - Request limit has been exceeded for this resource
  • 455: Service Unavailable - System is currently undergoing maintenance
  • 500: Server Error - An unexpected error occurred while processing the request
  • 501: Generation Failed - Image generation task failed
  • 505: Feature Disabled - The requested feature is currently disabled
Available options:
200,
400,
401,
402,
404,
422,
429,
455,
500,
501,
505
msg
string

Response message

Example:

"success"

data
object