tencent cloud

Stream Pushing Callback Notification
Download PDF
Last updated: 2025-09-08 17:27:01
Stream Pushing Callback Notification
Last updated: 2025-09-08 17:27:01
Download PDF
The stream pushing callback informs you whether stream pushing is successful or interrupted. After enabling the Callback Configuration in StreamLive's Input Setting, you need to fill in the Callback URL for receiving callback messages. Once you start pushing the live stream to StreamLive, the backend will send the callback to the server you set.
Note:
Currently, the stream pushing callback is only applicable to rtmp input protocol. Other protocols are not supported.

Stream Pushing Event Parameters

Event type

Event Type
Value
Successful push
event_type = 329
Push interrupted
event_type = 330

Common callback parameters

Parameter
Type
Description
t
int64
Expiration time, which is the Unix timestamp when the event notification signature expires.
The default validity period of a callback notification from Tencent Cloud is 10 minutes. If the time specified by the t value in a notification has elapsed, then this notification is considered invalid. This prevents network replay attacks.
The value of t is a decimal Unix timestamp, that is, the number of seconds that have elapsed since 00:00:00 (UTC/GMT time), January 1, 1970.
sign
string
Security signature. sign = MD5(key + t).
Note: Tencent Cloud splices the encryption key and t, generates the MD5 hash of the spliced string, and embeds it in callback messages. Your backend server can perform the same calculation when it receives a callback message. If the signature matches, it indicates the message is from Tencent Cloud. This callback key is used for authentication. We recommend you set this field to ensure data security.

Callback parameters

Parameter
Type
Description
appid
int
User APPID
channel_id
string
StreamLive Channel ID
event_type
int
Successful push：event_type = 329
Push interrupted：event_type = 330
input_id
string
StreamLive Channel Input ID
pipeline
int
StreamLive Channel Input Pipeline

Sample callback

Push Callback Message Example

{
            "data": {
                "appid": *********,
                "channel_id": "63F5C728000061D706B6",
                "event_type": 329,
                "input_id": "6583B18B000017CCCBDA",
                "interface": "general_callback",
                "pipelie": 0,
                "sign": "fb94d1628c7ab6b3ba23fcd777ac5112",
                "stream_id": "",
                "t": 1757066192
            },
            "header": {
                "Connection": "keep-alive",
                "Content-Length": "222",
                "Content-Type": "application/json",
                "User-Agent": "*********"
            },
            "receive_time": 1757065592
        }

Interruption Callback Message Example

{
            "data": {
                "appid": *********,
                "channel_id": "63F5C728000061D706B6",
                "event_type": 330,
                "input_id": "6583B18B000017CCCBDA",
                "interface": "general_callback",
                "pipelie": 1,
                "sign": "fb94d1628c7ab6b3ba23fcd777ac5112",
                "stream_id": "",
                "t": 1757066239
            },
            "header": {
                "Connection": "keep-alive",
                "Content-Length": "222",
                "Content-Type": "application/json",
                "User-Agent": "*********"
            },
            "receive_time": 1757065639
        }

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback