# Register Image A new visual can be registered to Bria without being uploaded to the database using the . This route returns a visual identification to the user. This is the recommended method to onboard images to Bria, when needed. It's the first step for consuming the Bria API for new visuals (instead of using the /upload route). The visual id in the response of the must be kept by the user in order to query image info, modify the image and use the search routes. The in the response of the /upload route will be used for all other routes. Store the visual_id in your database and map it to your image identification method for easy reference Files should not be larger than 12MB. The status code 413 will be returned if the file exceeds its maximum size. 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. Endpoint: POST /register ## Header parameters: - `api_token` (string, required) ## Request fields (application/json): - `org_image_key` (string) The internal image id in your API, of the image you would like to register to Bria. If accessing your images requires authentication, you will be able to register them using org_image_key only after giving Bria the API authentication information. It is also possible to register images using an org_image_key, without any authentication data. - `image_url` (string) The URL of the image you would like to register to Bria. The URL should lead to an image publicly available online. Either an org_image_key or an image_url should be provided. If both are provided, then the route will use image_url and org_image_key will be saved but not used. Images can only be registered using an image_url if they do not require authentication. - `is_private` (string) The image can be included in the Bria public gallery (is_private=false) or only in the Bria gallery of your organization (is_private=true). This parameter is optional and the default value is true. ## Response 200 fields (application/json): - `visual_id` (string) Unique visual identification ## Response 208 fields (application/json): - `visual_id` (string) Unique visual identification