Bria's Image Editing API equips builders with a comprehensive suite of tools for manipulating and enhancing images.
The API provides advanced capabilities including background operations (removal, replacement, blur), content manipulation (eraser, generative fill), image transformation (expansion, resolution increase), automatic cropping, person modification and automatic mask generation.
Advanced Customization and Access: As part of Bria’s Source Code & Weights product, developers seeking deeper customization can access Bria’s source-available GenAI models via Hugging Face. This allows full control over fine-tuning, pipeline creation, and integration into proprietary workflows—empowering AI teams to develop and optimize their own generative AI solutions.
The Eraser Route enables the removal of elements or specific areas from a given image.
You can define the area to be removed by providing a mask that outlines the region to be erased. There are two main ways recommended to generate these masks:
Masks can be created by allowing users to draw directly on the image with a brush, for example. To access the SDK that demonstrates how to implement a brush feature in your interface, please refer to the following link.
By using the /objects/mask_generator route, which will generate all the possible masks for an image.
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the modified output would contain inappropriate content.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp.
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp.
mask_urlstring
The URL of the binary mask image that represents the area that will be cleaned. If both mask_url and mask_file are provided, mask_url will be used. Accepted formats - jpeg, jpg, png, webp. The area to be removed should have the value 255 (white), while the rest of the image should have the value 0 (black). Note: The input image and mask must have the same aspect ratio.
mask_filestring
The file of the binary mask image that represents the area that will be cleaned, in base64 format. This parameter is used if mask_url is not provided. Accepted formats - jpeg, jpg, png, webp. The area to be removed should have the value 255 (white), while the rest of the image should have the value 0 (black). Note: The input image and mask must have the same aspect ratio.
mask_typestring
You can use this parameter to specify the type of the input mask from the list. 'manual' opttion should be used in cases in which the mask had been generated by a user (e.g. with a brush tool), and 'automatic' mask type should be used when mask had been generated by an algorithm like 'SAM'.
Default "manual"
Enum"manual""automatic"
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output images:
If the modified image fails moderation, returns a 422 error
URL that represents the updated visual created in the request. It is a temporary URL that will expire
Example: "URL"
Response
application/json
{
"result_url": "URL"
}
Generative Fill
Request
Description
The GenFill Route enables the generation of objects by prompt in a specific region of an image.
You can define the area for object generation by using a mask that outlines the region where the object will be created. Our model is optimized to work seamlessly with blob-shaped masks.
Masks can be created by allowing users to draw directly on the image with a brush, for example. To access the SDK that demonstrates how to implement a brush feature in your interface, please refer to the following link.
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content and filters out unsafe generated images - the first blocked input image will fail the entire request.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp.
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp.
mask_urlstring
The URL of the binary mask image that represents the area in which the object will be generated. If both mask_url and mask_file are provided, mask_url will be used. Accepted formats are jpeg, jpg, png, webp. The area in which the object will be generated should have the value 255 (white), while the rest of the image should have the value 0 (black). Note: The input image and mask must have the same aspect ratio.
mask_filestring
The file of the binary mask image that represents the area in which the object will be generated, in base64 format. This parameter is used if mask_url is not provided. Accepted formats are jpeg, jpg, png, webp. The area in which the object will be generated should have the value 255 (white), while the rest of the image should have the value 0 (black). Note: The input image and mask must have the same aspect ratio.
mask_typestring
You can use this parameter to specify the type of the input mask from the list. 'manual' opttion should be used in cases in which the mask had been generated by a user (e.g. with a brush tool), and 'automatic' mask type should be used when mask had been generated by an algorithm like 'SAM'.
Default "manual"
Enum"manual""automatic"
promptstring
The prompt you would like to use to generate the object within the masked region.
negative_promptstring
The prompt you would like to use to specify details or attributes to avoid in the object generated within the masked region.
num_resultsinteger[ 1 .. 4 ]
The number of images you would like to generate.
Default 4
syncboolean
Determines the response mode. When true, responses are synchronous. With false, responses are asynchronous, immediately providing URLs for images that are generated in the background. It is recommended to use sync=false for optimal performance. When generating more than 1 result, you should use the value false.
Default false
seedinteger
You can choose whether you want your generated results to be random or predictable. You can recreate the same result in the future by using the seed value of a result from the response. You can exclude this parameter if you are not interested in recreating your results. This parameter is optional.
content_moderationboolean
When enabled, applies content moderation to both input visuals and generated outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For synchronous requests (sync=true):
If some images pass and others fail, returns a 200 response with URLs array containing successful generations and "422_image_blocked_due_to_content_moderation" for failed ones examples: send using url: value: image_url: 'URL' mask_url: 'URL' prompt: 'object description' send using base64 string: value: file: 'base64_encoded_string_for_image' mask_file: 'base64_encoded_string_for_image' prompt: 'object description'
An array of URLs representing the updated visuals generated by the request. These URLs are temporary and will eventually expire.
When content_moderation is true:
For synchronous requests (sync=true): Array will contain URLs for successful generations and "422_image_blocked_due_to_content_moderation" for images that failed moderation
For asynchronous requests (sync=false): Failed images will be replaced with zero-byte files at their placeholder URLs
seedArray of integers or null
An array of integers representing the seeds used to generate each result. These seeds ensure reproducibility and are compatible with the results URL structure. When content moderation blocks an image, its corresponding seed will be null.
The Remove BG Route can be used to remove the background of an image. This route leverages Bria's newest model, RMBG 2.0. For more details and to explore the model, check out the Hugging Face demo.
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the modified output would contain inappropriate content.
Constraints
The Bria API currently supports only JPEG and PNG files in RGB, RGBA, or CMYK color modes. When the file is of a different type or color mode, the status code 415 will be returned.
Remove the background from an image using the image file
In our documentation request example, we demonstrate how to remove the background from an image using the image URL.
If you want to use an image from a file, follow the example below:
The image file you would like to remove the background from.
image_urlstring
The URL of the image file you would like to remove the background from. The URL should lead to an image publicly available online. Either a file or an image_url should be provided. If both are provided, then the route will use image_url.
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output images:
If the modified image fails moderation, returns a 422 error
URL that represents the updated visual created in the request. It is a temporary URL that will expire.
Response
application/json
{
"result_url": "string"
}
Generate Background
Request
Description
The Replace BG Route is used to replace the background of any image. We offer a fast version of this feature, powered by Bria 2.3 Fast LoRA (model card on Hugging Face), which provides an optimal balance between speed and quality. This endpoint also supports solid colors - you can take a color code and use it in the prompt. Here are some examples:
original image:
bg_prompt: in a parking lot
num_results: 3
results:
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content, and filters out unsafe modified images - the first blocked input image will fail the entire request.
Headers
api_tokenstringrequired
API token associated with the organization.
Bodyapplication/json
syncboolean
Determines the response mode. When true, responses are synchronous. With false, responses are asynchronous, immediately providing URLs for images that are generated in the background. It is recommended to use sync=false for optimal performance. When generating more than 1 result, you should use the value false.
Default false
fastboolean
Determines the generation mode. When true, the generation will utilize the fast mode which provides the best balance between speed and quality. When false, the regular mode will be utilized.
Default true
image_urlstring
The URL of the image to which a new background should be generated. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
filestring
The product of the image to which a new background should be generated, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
ref_image_urlstring
The URL of the reference image to be used for generating the new background. Either ref_image_url or bg_prompt has to be provided but not both. If both ref_image_url and ref_image_file are provided, ref_image_url will be used. Accepted formats are jpeg, jpg, png, webp.
ref_image_filestring
The reference image file to be used for generating the new background. If both ref_image_url and ref_image_file are provided, ref_image_url will be used. Accepted formats are jpeg, jpg, png, webp.
bg_promptstring
Text description of the new scene or background for the provided image. Either ref_image_url or bg_prompt has to be provided but not both. Bria currently supports prompts in English only, excluding special characters.
refine_promptboolean
When true, an additional logic takes the bg_prompt that was included and adjusts it to achieve optimal results. Built with Meta Llama 3.
Default true
enhance_ref_imageboolean
When set to true, additional logic processes the included reference image to make adjustments for optimal results.
Default true
original_qualityboolean
When true, the output image retains the original input image's size; otherwise, the image is scaled to 1 megapixel (1MP) while preserving its aspect ratio.
Default false
num_resultsinteger
The number of results you would like to generate.
Default 4
force_rmbgboolean
Forces background removal, even if the original image already contains an alpha channel. Useful for refining existing foreground/background separation or ignoring unnecessary alpha channels.
Default false
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops at the first image that fails moderation
Returns a 422 error with details about which parameter failed
For synchronous requests (sync=true):
If all modified images fail moderation, returns a 422 error
If some images pass and others fail, returns a 200 response with successful outputs and "blocked" objects for failed ones
For asynchronous requests (sync=false):
Failed images are replaced with zero-byte files at their placeholder URLs
Successful images are stored at their original placeholder URLs
Default false
negative_promptstring
Elements or features that should be excluded from the generated scene. This parameter is optional and is available only when fast=false. Bria currently supports descriptions in English only.
seedinteger
You can choose whether you want your generated results to be random or predictable. You can recreate the same result in the future by using the seed value of a result from the response. You can exclude this parameter if you are not interested in recreating your results. This parameter is optional.
curl -i -X POST \ https://engine.prod.bria-api.com/v1/background/replace \ -H 'Content-Type: application/json' \ -H 'api_token: string' \ -d '{ "bg_prompt": "in a living room interior, on a kitchen counter", "num_results": 2, "sync": true, "image_url": "URL" }'
Responses
Successful operation
Bodyapplication/json
resultArray of strings
The array contains the results created in the request. In each result, the first value represents the URL of the result, the second value represents the seed, and the third value represents the session id of the result. It will take a few seconds for the image to become available via the URL if sync=false. You can recreate the same result in the future by using the seed as part of the request.
When content_moderation is true:
For synchronous requests (sync=true): Results array will contain both successful generations and "blocked" objects for images that failed moderation
For asynchronous requests (sync=false): Failed images will be replaced with zero-byte files at their placeholder URLs
This route is used to erase the foreground from a provided image, while generating the area behind it. This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the modified output would contain inappropriate content.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
Example: "URL"
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output images:
If the modified image fails moderation, returns a 422 error
URL that represents the updated visual created in the request. It is a temporary URL that will expire
Example: "URL"
Response
application/json
{
"result_url": "URL"
}
Blur Background
Request
Description
The background/blur Route is used to create a blur effect on the background of an image. This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the modified output would contain inappropriate content.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
Example: "URL"
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
scaleinteger[ 1 .. 5 ]
A scale for determining how blurry the background of the image should be. The options are 1, 2, 3, 4, 5. This parameter is optional.
Default 5
force_rmbgboolean
Forces background removal, even if the original image already contains an alpha channel. Useful for refining existing foreground/background separation or ignoring unnecessary alpha channels.
Default false
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output images:
If the modified image fails moderation, returns a 422 error
URL that represents the updated visual created in the request. It is a temporary URL that will expire
Example: "URL"
Response
application/json
{
"result_url": "URL"
}
Expand Image
Request
Description
The Image Expension Route can be used to expand an image, by utilizing generative AI.
You can decide on the image size of the final result as well as the position and size of the original image compared to the final result.
In this way, you can create unique variations of your original image instead of cropping it into different aspect ratios and losing important details.
Optimal input range
Input Image Area: Ensure that the ratio of the input image foreground or main subject to the canvas area is greater than 15% to achieve optimal results.
Canvas Size: The canvas size should be up to an area of 5000x5000 pixels. Here are some examples:
original image (Generated by Bria):
results:
original image (Stock Image):
results:
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the expanded output would contain inappropriate content.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
Example: "URL"
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
canvas_sizeArray of integers
The desired size of the final image, after the expansion. should have an area of less than 5000x5000 pixels.
Default [1000,1000]
Example: [1200,674]
original_image_sizeArray of integers
The desired size of the original image, inside the full canvas. Ensure that the ratio of input image foreground or main subject to the canvas area is greater than 15% to achieve optimal results.
Example: [610,855]
original_image_locationArray of integers
The desired location of the original image, inside the full canvas. Provide the location of the upper left corner of the original image. The location can also be outside the canvas (the original image will be cropped).
Example: [301,-66]
promptstring
Text on which you wish to base the image expansion. This parameter is optional. Bria currently supports prompts in English only, excluding special characters.
seedinteger
You can choose whether you want your generated expension to be random or predictable. You can recreate the same result in the future by using the seed value of a result from the response. You can exclude this parameter if you are not interested in recreating your results. This parameter is optional.
negative_promptstring
This parameter is optional. Bria currently supports prompts in English only.
content_moderationboolean
When enabled, applies content moderation to both input visuals and expanded output.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output image:
If the expanded image fails moderation, returns a 422 error
A message that describes the request status. The options are Finished sucessfully, Content might not be safe for work.
Example: "Finished sucessfully"
promptstring
The prompt used to generate the expansion. If you want to recreate the result again, you should use in the request the prompt and the seed of the response.
Example: "a man in a shirt sitting down in front of a brick wall looking off to the side"
result_urlstring
URL that represents the updated visual created in the request. It is a temporary URL that will expire
Example: "URL"
seedinteger
If you want to recreate the result again, you should use in the request the prompt and the seed of the response.
Example: 1525972691
statusstring
The request status. The options are SUCCESS, NSFW.
Example: "SUCCESS"
Response
application/json
{
"code": 200,
"description": "SUCCESS",
"message": "Finished sucessfully",
"prompt": "a man in a shirt sitting down in front of a brick wall looking off to the side",
"result_url": "URL",
"seed": 1525972691,
"status": "SUCCESS"
}
Increase Resolution
Request
Description
The Increase Resolution Route is used to upscale the resolution of any image.
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the modified output would contain inappropriate content.
Constraints
The Bria API currently supports only JPEG and PNG files in RGB, RGBA, or CMYK color modes. When the file is of a different type or color mode, the status code 415 will be returned.
It's possible to increase the resolution of an image up to a total area of 8192x8192 pixels.
Increase the Resolution of an image using the image file
In our documentation request example, we demonstrate how to Increase the Resolution of an image using the image URL.
If you want to use an image from a file, follow the example below:
The resolution multiplier. The possible value are 2,4. It's possible to increase the resolution of an image up to a total area of 8,192x8,192 pixels.
Example: desired_increase=2
Headers
api_tokenstringrequired
Bodymultipart/form-datarequired
filestring(binary)
The image file you would like to increase the resolution for. Minimum resolution supported for width and/or height is 216 pixels.
image_urlstring
The URL of the image file you would like to increase the resolution for. The URL should lead to an image publicly available online. Either a file or an image_url should be provided. If both are provided, then the route will use image_url. Minimum resolution supported for width and/or height is 216 pixels.
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output images:
If the modified image fails moderation, returns a 422 error
Note: This API route requires the image to be registered via the /register route.It will be replaced soon with isolated version, that doesn't require image registration.
The Image to PSD Route is used to create a layered PSD file from any image.
The image is divided into different layers (depending on the image): a background layer with all identified objects removed, a foreground layer without the background, and a layer for each object.
You can also use this route on a modified image by providing the sid from the response of the previously used route.
Path
visual_idstringrequired
visual id of the image, for which the user would like to create a layered PSD file
Example: 8487fb411f3c6716
Query
sidstring
This session id was obtained from the response of a route that had been applied to this visual id. If you have used another route on the provided visual before, and you would like the current route to apply on the result of that route, please provide this information. This parameter is optional.
Example: sid=Remove this parameter if the image has not been modified using Bria.
The Crop Route is used to remove the background from an image and crop tightly around the foreground or remaining region of interest. It supports both images with and without a background. This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content or if the modified output would contain inappropriate content.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
paddinginteger
Cropping the object with padding around it. Currently, padding is applied to all four borders of the remaining region. This parameter is optional.
Default 0
force_rmbgboolean
Forces background removal, even if the original image already contains an alpha channel. Useful for refining existing foreground/background separation or ignoring unnecessary alpha channels.
Default false
content_moderationboolean
When enabled, applies content moderation to both input visuals and modified outputs.
For input images:
Processing stops if the image fails moderation
Returns a 422 error with details about which parameter failed
For output images:
If the modified image fails moderation, returns a 422 error
URL that represents the updated visual created in the request. It is a temporary URL that will expire
Example: "URL"
Response
application/json
{
"result_url": "URL"
}
Get Masks
Request
Description
Note: This API route requires the image to be registered via the /register route.
The Objects/Mask Generator Route is used to generate all possible masks for an image, creating a full segmentation of the image.
The response contains a zip file named as the visual_id of the provided image.
There are k mask files in the zip, each named with the visual_id and mask_id.
The zip file contains an additional file whose name ends with "panoptic". It's not an image, it's a panoptic map. It can be transformed into a regular matrix.
Each point in the image (x,y) is mapped to the mask that applies to that point. In the panoptic map, each pixel's grayscale value includes the mask_id.
You can display those masks to the user, let them pick one or more masks, and use objects/remove route to remove the masked area.
In order to use the objects/remove route on the mask the user selected, you should provide the mask_id, and use the parameter mask_source=generated.
You can see below an example of the content of the zip:
92bf8ce17584de82_panoptic.png
92bf8ce17584de82_1.png
92bf8ce17584de82_2.png
92bf8ce17584de82_3.png
...
92bf8ce17584de82_86.png
You can access the SDK that demonstrates how to use this endpoint in a UI in the following link. This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content - the first blocked input image will fail the entire request.
Headers
api_tokenstringrequired
Bodyapplication/json
image_urlstring
The URL of the input image. If both image_url and image_file are provided, image_url will be used. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
filestring
The file of the input image, in base64 format. Used if image_url is not provided. Accepted formats are jpeg, jpg, png, webp. Maximum file size 12MB.
content_moderationboolean
When enabled, applies content moderation to input visuals.
For input images:
Processing stops at the first image that fails moderation
Returns a 422 error with details about which parameter failed
Note: This API route requires the image to be registered via the /register route.
The Person/Info Route is used to retrieve useful information on the people in a specific visual that was previously uploaded to the database.
Additionally, it provides a description of each person within the scene along with its available changes, which are supported by the Bria API.
This route should be used instead of the main /info route when you are only interested in information and available actions for the people in the image. With this route, you will save time by only obtaining information that is relevant to your needs.
Path
visual_idstringrequired
visual id of the image, received after using the /upload or register route.
curl -i -X GET \ https://engine.prod.bria-api.com/v1/f49943971e3039c7/person/info \ -H 'api_token: string'
Responses
Successful operation.
Bodyapplication/jsonArray [
actionsobject
The available API actions for this specific person.
idstring
The id of the person
labelsArray of arrays
The known information about the person, such as age range and gender
oracleobject
The predicted quality of the available actions for this specific person
rectobject
The location of the face inside the image. x and y represent the upper left corner of the face, and by using the w (width) and h (height) you can create a rectangle around the face.
Note: This API route requires the image to be registered via the /register route.
The Create Route is used to create a new visual, based on the changes requested by the user for a previously uploaded visual.
You can also use this route on a modified image by providing the sid from the response of the previously used route.
This route returns both the URL and the sid associated with the updated image.
Before making any modifications, please call the /info or person/info route to obtain information on the available presenters in the image, the available modifications, and their oracle values.
You should always include all the required changes in the request if you want to use multiple changes on a single person. It is not supported to make one request on a person with one change, take the SId from the result, and then use it in another request with a different change.
When you want to make changes on multiple people, you can make one request with all the desired changes on all the relevant people or make one request with all the desired changes on one person and then use the sid from the response in the request on the other person.
Path
visual_idstringrequired
visual id of the image the user wants to create a new visual from.
Example: 8487fb411f3c6716
Headers
api_tokenstringrequired
Bodyapplication/json
sidstring
This session id was obtained from the response of a route that had been applied to this visual id. If you have used another route on the provided visual before, and you would like the current route to modify the result of that route, please provide this information. This parameter is optional.
desired_resolutionstring
The desired resolution of the updated image. This parameter is optional.
Id of the selected object in the image, to which the user would like to make changes.
changes[].​actionsobject
The changes the user wishes to perform for this object in the image. Each action the user chooses to use must be included in the info route response for this object and image. This is essential for the /create request to be successful.
changes[].​actions.​agestring
Changing the age of a selected person. It is possible to use one of the enum values or to provide a value between -10 and 10. Decimal values are acceptable.
Enum"mid-20""mid-40""mid-60"
changes[].​actions.​diversitystring
Changing the diversity of a selected person. It is possible to use one of the enum values or to provide in addition to the enum a value between 0 and 1.
Changing the expression of a selected person. It is possible to use one of the enum values or to provide in addition to the enum a value between 0 and 1.5.
Changing the glasses of a selected person. It is possible to use one of the enum values or to provide a value between 0 and 6. Only integer values are acceptable.
Enum"light""heavy""none"
changes[].​actions.​haircolorstring
Changing the hair color of a selected person. It is possible to use one of the enum values or to provide a value between 0 and 4. Only integer values are acceptable.
Enum"black""brown""red""blond""gray"
changes[].​actions.​genderstring
Changing the gender of a selected person. It is possible to use one of the enum values or to provide a value between -10 and 10. Decimal values are acceptable.
Enum"femininity""masculinity"
changes[].​actions.​makeupstring
Changing the makeup of a selected person. It is possible to use one of the enum values or to provide a value between -10 and 10. Decimal values are acceptable.
Enum"light""heavy""none"
changes[].​actions.​hair_linestring
Changing the hair line of a selected person. It is possible to use one of the enum values or to provide a value between -20 and 20. Decimal values are acceptable.
Enum"high""low"
changes[].​actions.​Beardstring
Changing the facial hair of a selected person. It is possible to use one of the enum values or to provide a value between -2 and 2. Decimal values are acceptable.
This session id represents the result of the current route request. If you wish to use this result in other routes, please provide this sid in their input.
This API endpoint supports content moderation via an optional parameter that can prevent processing if input images contain inappropriate content, and filters out unsafe modified images - the first blocked input image will fail the entire request.
