This topic describes the syntax of the HTTP and HTTPS POST requests sent to call the Content Moderation API.

Request methods

The Content Moderation API supports both HTTP and HTTPS POST requests. The JSON-formatted request parameters are sent to the server in an HTTP request body. The common query parameter clientInfo is available in the URL query parameters.

The following code provides an example of an unencoded request for synchronous image moderation:
http://green.cn-shanghai.aliyuncs.com/green/image/scan?clientInfo={"ip":"127.0.0.2","userId":"120234234","userNick":"Mike","userType":"others"}
Parameters:
  • http: the protocol used to send the request.
  • green.cn-shanghai.aliyuncs.com: the endpoint of the Content Moderation API.
  • green/image/scan: a specific operation. In the example, green/image/scan indicates the synchronous image moderation operation.
  • clientInfo={"ip":"127.0.0.2","userId":"120234234","userNick":"Mike","userType":"others"}: the common query parameters.

Communication protocols

You can send requests over HTTP or HTTPS. For a higher level of security, we recommend that you send requests over HTTPS, especially when sensitive data is involved.

Request parameters

In each request, you must specify common request parameters and operation-specific service request parameters. Service request parameters are passed through in the request body. For more information about the body structure, see the description of each operation.

Encoding

Requests and responses are both encoded in UTF-8.