Extracting Invisible Image Watermarks from Images (Image Addresses)
Function
This API is used to extract invisible image watermarks from images whose storage address is specified (only a Huawei Cloudcloud service OBS path is supported).DSC returns the watermark images in a specified storeage location (an OBS path). The supported image format is .jpg, .jpeg, .jpe, .png, .bmp, .dib, .rle, .tiff, .tif, .ppm, .webp, .tga, .tpic, and .gif.
URI
POST /v1/{project_id}/image-address/watermark/extract-image
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        project_id  | 
      
        Yes  | 
      
        String  | 
      
        Project ID  | 
     
Request Parameters
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        X-Auth-Token  | 
      
        Yes  | 
      
        String  | 
      
        User token It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is a token.  | 
     
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        region_id  | 
      
        Yes  | 
      
        String  | 
      
        ID of the region where the project is located, for example, xx-xx-1.  | 
     
| 
        src_file  | 
      
        Yes  | 
      
        String  | 
      
        Address of the image from which the image watermark is to be extracted. Currently, only Huawei Cloudcloud service OBS objects are supported. The format is obs://bucket/object, where bucket indicates the name of the OBS bucket in the same region as the current project, and object indicates the full path name of the object. For example, obs://hwbucket/hwinfo/hw.png.  | 
     
| 
        image_watermark  | 
      
        Yes  | 
      
        String  | 
      
        Storage address of the extracted image watermark. The format requirements are the same as those of src_file.  | 
     
Response Parameters
Status code: 200
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        region_id  | 
      
        String  | 
      
        ID of the region where the current project is located, for example, xx-xx-1.  | 
     
| 
        image_watermark  | 
      
        String  | 
      
        Storage address of the extracted image watermark. Currently, only Huawei Cloudcloud service OBS objects are supported. The format is obs://bucket/object, where bucket indicates the name of the OBS bucket in the same region as the current project, and object indicates the full path name of the object. For example, obs://hwbucket/hwinfo/hw.png.  | 
     
Status code: 400
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        error_code  | 
      
        String  | 
      
        Error Code  | 
     
| 
        error_msg  | 
      
        String  | 
      
        Error Message  | 
     
Example Requests
Extract the invisible watermark from the image at obs://hwbucket/hwinfo/hw.png and store the extracted watermark image at obs://hwbucket/watermarkfile/mark.png.
POST /v1/{project_id}/obs-image/image-watermark/extract HTTP/1.1
{
  "region_id" : "xx-xx-1",
  "src_file" : "obs://hwbucket/hwinfo/hw.png",
  "image_watermark" : "obs://hwbucket/watermarkfile/mark.png"
}
 Example Responses
Status code: 200
Request succeeded.
{
  "region_id" : "xx-xx-1",
  "image_watermark" : "obs://hwbucket/watermarkfile/mark.png"
}
  Status code: 400
Invalid request
{
  "error_code" : "DSC.00000007 ",
  "error_msg" : "File format error"
}
 Status Codes
| 
        Status Code  | 
      
        Description  | 
     
|---|---|
| 
        200  | 
      
        Request succeeded.  | 
     
| 
        400  | 
      
        Invalid request  | 
     
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.