Information Submission Interface Specification

1. Parameter specification

  • Request URL:

  • Interface description:

Submit the information related to live video streaming to the interface. After the submission, screenshots of the video will be detected, and the detection results need to be obtained by calling the Result Obtaining Interface.

  • Supported formats:

Streaming protocols supported by the detection interface are as follows: rtp, srtp, rtmp, rtmps, mmsh, mmst, hls, http-m3u8, http-flv, tcp, etc.

  • HTTP Request Header:
Header Value Description
Content-Type application/json;charset=UTF-8 Request body type
Accept application/json;charset=UTF-8 Accepted return type
X-AppId The only identifier of the project or application
X-TimeStamp The UTC timestamp of the request. Timestamps need to be formatted according to W3C standards, for example: 2010-01-31T23:59:59Z. (
Authorization Signature value
  • Request method:POST

  • Request body JSON object:

Parameter Essential Type Description
lang Essential String language:zh-CN;Support more languages in the future
audio Essential Srting URI of live audio
userId Optional Srting Unique end user ID. The user ID should be no more than 32 characters.
userIP Optional Srting User IP address
did Optional Srting User device ID
dtype Optional Srting User device type:1:iPhone 2:android 3: ipad 4:wphone 5: pc 6:web 7:wap
callbackRegion Optional String callback region:default use cn server to do callback,supports : cn,us,eu
callbackUrl Optional String callback url:http
callbackSecretKey Optional String callback secret key, customizable. but is necessary be consistent in your callback signature
  • Example of request body:

    JSON Response
     "userId": "testUser"
  • Request signature:

When the user requests Video Submit API, the request can be signed with the appId and secretKey (obtained from the Console - Service Configuration). When the API receives the request with the signature information, it will verify the signature using the same algorithm, and if the signature is found to be inconsistent, the API will return 401 error to the user.

If the API validation signature is consistent and the user corresponding to the appId has permission to operate the requested resource, the request succeeds, otherwise the API returns 401 error.

  • Send signatures by HTTP Request Headers

Method: Add a header named Authorization in the request, whose value is the signature value. For example:

 Authorization: Njl86M/jY6zZaZoGhZdGO+GI/8+yGFECusGH1yQHUFE=
  • Signature calculation method
  1. Canonicalized Query String

Convert the request body JSON string to a hexadecimal string (not Base64) by doing sha256 encoding with UTF-8 character encoding.

CanonicalizedQueryString = hex(sha256(jsonBody))

  1. Constructs the signed string StringToSign ("\n" stands for ASCII newline character):

    StringToSign = HTTPMethod + “\n” + HostHeaderInLowercase + “\n” + HTTPRequestURI + “\n” + CanonicalizedQueryString + “\n” + “X-AppId:” + SAME_APPID_IN_HEADER + “\n” + “X-TimeStamp:” + SAME_TIMESTAMP_IN_HEADER

The HTTPRequestURI is the absolute path to the request URI, without the request string. If the HTTPRequestURI is empty, also keep a forward slash (/)

The hash-based message authentication code (HMAC) is created using the HMAC-SHA256 protocol and the signature is calculated.

  1. StringToSign as the signature string, secretKey as the secret key and SHA256 as the hash algorithm.

    For more information about HMAC, see:。
  2. Converting the results of the previous step to a BASE64 string

  3. Put the BASE64 string into the Authorization of HTTP request Header

  • Example of signature

Below is an example of appId & secretKey & audio


Below is an example of request type.

 "userId": "testUser"

Generate CanonicalizedQueryString


Generate StringToSign


Signatures from HMAC calculations