Application Process
To use the API, you first need to apply for the corresponding service on the Midjourney Edits API page. After entering the page, click the “Acquire” button, as shown in the image below:
If you are not logged in or registered, you will be automatically redirected to the login page inviting you to register and log in. After logging in or registering, you will be automatically returned to the current page.
Upon your first application, there will be a free quota available for you to use the API at no cost.
Basic Usage
First, understand the basic usage method, which involves inputting the promptprompt, the action action, and the reference image image_url to obtain the processed result. You first need to simply pass a field action with the value generate, as detailed below:

accept: the format of the response result you want to receive, filled in asapplication/json, which means JSON format.authorization: the key to call the API, which can be selected directly after application.
mask: can specify the mask position of the image area for editing and regeneration.split_images: splits the generated image into multiple images, returned through the sub_image_urls field. By default, it is false.action: the behavior of this image editing generation task, defaulting togenerate.image_url: the link to the image that needs to be edited.prompt: the prompt.mode: generation mode, optionalfast/relax/turbo.callback_url: the URL to receive the callback result.

success: the status of the image editing generation task.task_id: the ID of the image editing generation task.image_id: the image ID of this image editing task.sub_image_urls: multiple image results of the image generation task.image_url: the link to the generated image result.image_width: the width of the generated image result.image_height: the height of the generated image result.progress: the progress field of the image editing generation task.
image_url.
Additionally, if you want to generate the corresponding integration code, you can directly copy the generated code, for example, the CURL code is as follows:
Asynchronous Callback
Since the time taken by the Midjourney Edits API to generate is relatively long, approximately 1-2 minutes, if the API does not respond for a long time, the HTTP request will keep the connection open, leading to additional system resource consumption. Therefore, this API also provides support for asynchronous callbacks. The overall process is: when the client initiates a request, an additionalcallback_url field is specified. After the client initiates the API request, the API will immediately return a result containing a task_id field, representing the current task ID. When the task is completed, the generated video result will be sent to the client-specified callback_url in the form of a POST JSON, which also includes the task_id field, allowing the task result to be associated by ID.
Let’s understand how to operate specifically through an example.
First, the Webhook callback is a service that can receive HTTP requests, and developers should replace it with the URL of their own HTTP server. For demonstration purposes, we will use a public Webhook sample site https://webhook.site/, where you can open the site to get a Webhook URL, as shown in the image below:
Copy this URL, and it can be used as a Webhook. The sample here is https://webhook.site/556e6971-b41f-4fa8-9151-6e91acd0399f.
Next, we can set the callback_url field to the above Webhook URL while filling in the corresponding parameters, as shown in the image below:

https://webhook.site/556e6971-b41f-4fa8-9151-6e91acd0399f, as shown in the image below:

task_id field, and other fields are similar to the above text. This field can be used to achieve task association.
Error Handling
When calling the API, if an error occurs, the API will return the corresponding error code and message. For example:400 token_mismatched: Bad request, possibly due to missing or invalid parameters.400 api_not_implemented: Bad request, possibly due to missing or invalid parameters.401 invalid_token: Unauthorized, invalid or missing authorization token.429 too_many_requests: Too many requests, you have exceeded the rate limit.500 api_error: Internal server error, something went wrong on the server.

