# v1 endpoints

Endpoints that are part of BRIA API version 1.


## Delayer Image

 - [POST /{visual_id}/image_to_psd](https://docs.bria.ai/image-editing-v2/v1-endpoints/image-to-psd.md): 



*



The  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.

## Get Masks

 - [POST /objects/mask_generator](https://docs.bria.ai/image-editing-v2/v1-endpoints/objects-mask-generator.md): 




*

The  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.

## Get Presenter info

 - [GET /{visual_id}/person/info](https://docs.bria.ai/image-editing-v2/v1-endpoints/person-info.md): 




*

The  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.

## Modify Presenter

 - [POST /{visual_id}/create](https://docs.bria.ai/image-editing-v2/v1-endpoints/create.md): 



*

The  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.