ParseLiveStreamProcessNotification

Last updated: 2026-08-14 16:33:20Download PDF

1. API Description

Domain name for API request: mps.intl.tencentcloudapi.com.

After receiving the message from CMQ, parse out the content of the MPS live stream processing event notification from the msgBody field of the message.
This API is not used to trigger network calls, but to help generate SDKs for each language platform. You can refer to the parsing implementation in the SDK to parse event notifications.

A maximum of 20 requests can be initiated per second for this API.

We recommend you to use API Explorer

Try it

API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name	Required	Type	Description
Action	Yes	String	Common Params. The value used for this API: ParseLiveStreamProcessNotification.
Version	Yes	String	Common Params. The value used for this API: 2019-06-12.
Region	No	String	Common Params. This parameter is not required for this API.
Content	Yes	String	Event notification content for live streams obtained from CMQ.

3. Output Parameters

Parameter Name	Type	Description
NotificationType	String	Live stream processing result type, including: AiReviewResult: content moderation result; AiRecognitionResult: content recognition result; LiveRecordResult: live streaming result; AiQualityControlResult: media quality inspection result. AiAnalysisResult: content analysis result. AiSmartSubtitleResult: smart subtitle result; ProcessEof: end of live stream processing.
TaskId	String	Task ID for video processing.
ProcessEofInfo	LiveStreamProcessErrorInfo
AiReviewResultInfo	LiveStreamAiReviewResultInfo
AiRecognitionResultInfo	LiveStreamAiRecognitionResultInfo
AiAnalysisResultInfo	LiveStreamAiAnalysisResultInfo
AiQualityControlResultInfo	LiveStreamAiQualityControlResultInfo
LiveRecordResultInfo	LiveStreamRecordResultInfo
AiSmartSubtitleResultInfo	LiveStreamAiSmartSubtitleResultInfo	Smart subtitle result, valid when NotificationType is AiSmartSubtitleResult.
SessionId	String	An identifier for deduplication. If there has been a request with the same identifier within the past seven days, an error will be returned for the current request. The maximum length is 50 characters. Leaving it blank or using a null string indicates no deduplication is required.
SessionContext	String	Source context, which is used to pass through user request information. The callback for task flow status changes will return the value of this field. The maximum length is 1,000 characters.
Timestamp	Integer	-Expiration time, the UNIX timestamp for event notification signature expiration. Notifications from Media Processing Service (MPS) have a default expiration time of 10 minutes. If the time specified by the Timestamp value in a notification has expired, the notification can be deemed invalid, which helps prevent network replay attacks. The Timestamp format is a decimal UNIX timestamp, representing the seconds elapsed since midnight on January 1, 1970 (UTC/GMT).
Sign	String	Event notification security signature. Sign = MD5 (Timestamp + NotifyKey). Note: Media Processing Service concatenates Timestamp and NotifyKey from TaskNotifyConfig as a string and calculates the Sign value through MD5. This value is included in the notification message. Your backend server can verify whether the Sign is correct using the same algorithm, to confirm whether the message is indeed from the Media Processing Service backend.
RequestId	String	The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

4. Example

Example1 Parsing Live Stream Event Notification Content

Callback body description

Input Example

https://mps.intl.tencentcloudapi.com/?Action=ParseLiveStreamProcessNotification
&Content={"NotificationType":"AiReviewResult",XXX
&<Common request parameters>

Output Example

{
    "Response": {
        "NotificationType": "AiReviewResult",
        "TaskId": "2459149217-procedure-live-xxx51da009t0",
        "ProcessEofInfo": null,
        "AiReviewResultInfo": {
            "ResultSet": [
                {
                    "Type": "VoicePorn",
                    "ImagePornResultSet": [],
                    "ImageTerrorismResultSet": [],
                    "ImagePoliticalResultSet": [],
                    "VoicePornResultSet": [
                        {
                            "StartPtsTime": 0.266,
                            "EndPtsTime": 4.146,
                            "Confidence": 98,
                            "Suggestion": "block",
                            "Label": "sexual_moan"
                        }
                    ]
                }
            ]
        },
        "AiRecognitionResultInfo": null,
        "AiAnalysisResultInfo": null,
        "AiQualityControlResultInfo": null,
        "SessionId": "",
        "SessionContext": "",
        "RequestId": "335bdaa3-db0e-46ce-9946-51941d9cb0f5"
    }
}

5. Developer Resources

SDK

TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

Command Line Interface

Tencent Cloud CLI 3.0

6. Error Code

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

Error Code	Description
FailedOperation.InvalidMpsUser	Operation failed: unauthorized MPS user.
InvalidParameterValue.InvalidContent	The value of Content is invalid.