Skip to main content
POST
/
mj
/
submit
/
blend
cURL
curl https://api.deerapi.com/mj/submit/blend \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DEERAPI_KEY" \
  -d '{
    "botType": "MID_JOURNEY",
    "base64Array": [
      "data:image/png;base64,xxx1",
      "data:image/png;base64,xxx2"
    ]
  }'
{
  "code": 123,
  "description": "<string>",
  "properties": {},
  "result": 123
}

​
Overview

Use this endpoint to call the Midjourney Submit Blend workflow through DeerAPI. The API reference on this page shows the request schema, response schema, authentication requirements, and runnable examples for the configured endpoint.

​
Before you start

Use the DeerAPI base URL and pass your API Key in the Authorization header: 
https://api.deerapi.com

Authorization: Bearer $DEERAPI_KEY

​
Model selection

Choose a current model ID from the live pricing page. Model availability changes over time, so avoid copying a model ID from an old project without checking the live list first.

​
Implementation notes

  • Use the OpenAPI playground for the exact request fields accepted by this endpoint.
  • Keep API Keys on the server side when you build production applications.
  • Log the request ID from failed calls so support can investigate the request.
  • Retry 429, 500, and 503 responses with exponential backoff.

Authorizations

​
Authorization
string
header
required

Use a DeerAPI API Key as a Bearer token.

Body

application/json
​
base64Array
string[]
required

Two or more base64-encoded images to blend. Each item should be a data URI such as data:image/png;base64,xxx.

​
dimensions
enum<string>

Output aspect ratio.

Available options:
PORTRAIT,
SQUARE,
LANDSCAPE
​
notifyHook
string

Webhook URL to receive task status updates. Falls back to your account-level webhook if omitted.

​
state
string

Custom state string. Returned as-is in the task result and webhook callback for your own tracking.

​
botType
enum<string>

Bot type to use. MID_JOURNEY for Midjourney (default), NIJI_JOURNEY for Niji.

Available options:
MID_JOURNEY,
NIJI_JOURNEY

Response

200 - application/json

Success

​
code
integer
required

Status code

​
description
string
required

Human-readable description message corresponding to the status code

​
properties
object
required

Additional properties or metadata

​
result
integer
required

Returned task ID