Introduction

Purchase Guide

Billing Overview

Overdue Payments and Service Suspension

Console Guide

Input Management

Channel Management

Asset Management

Plan Management

Feature Guide

Implementing Live Streaming

Stream Real-Time Monitoring

Digital Rights Management (DRM)

Forensic Watermark

Input Failover

Input Switch

Stream Pushing Callback Notification

Playlist

Scheduled Recording

Highlights

Time shifting

Delayed Playback

Adaptive Bitrate Streaming

Caption

Relay

Frame Capture

SCTE-35

PDT (HLS)

Archiving (Recording)

Dolby Audio

Output To YouTube

Ad Insertion

StreamLive Tag

API Documentation

History

Introduction

API Category

Making API Requests

Input Management APIs

Input Security Group Management APIs

Channel Management APIs

Plan APIs

Watermark Management APIs

Statistics APIs

Data Types

Error Codes

StreamLive Policy

Data Processing and Security Agreement

Related Agreement

Service Level Agreement

Stream Pushing Callback Notification

PDF

Focus Mode

Font Size

Last updated: 2025-09-08 17:27:01

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
        }
﻿

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

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

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.

tencent cloud

StreamLive

Stream Pushing Callback Notification

Stream Pushing Event Parameters

Event type

Common callback parameters

Callback parameters

Sample callback

Push Callback Message Example

Interruption Callback Message Example

Help and Support