Status Callback
The Cloud Player Service provides status callbacks to synchronize relevant data and states to your application server address configured in the Console.
Callback Method
POST: <your-receiving-server-url>
Data Format: application/json
The callback URL <your-receiving-server-url>
is the receiving address you configured in the Console for the current App Key and service. Ensure this address is accessible. If your network has IP restrictions, configure the IP allowlist to receive server callbacks properly.
To verify data integrity and authenticate the caller as RC Server, each request includes a signature. For callback signature rules, see Server Callback.
Callback Body Parameters
The HTTP request body of this callback service uses application/json
format and contains a JSON object with the following structure:
Field Name | Type | Description |
---|---|---|
timestamp | Number | Timestamp in milliseconds |
type | Number | Callback type. 1 : Stream pull success. 2 : Stream pull ended. 3 : Initial stream pull failure. 4 : Stream pull interrupted (RTMP reconnection). 5 : RTC publishing status callback (for manual cloud recording, call start recording only after status 5 ). |
app_key | String | App Key assigned in the developer platform |
room_id | String | Room ID |
rtmp_url | String | Public URL of the streaming resource |
user_id | String | User ID of the stream |
code | Number | Status code. See code descriptions below. |
video_resolution | String | Video resolution (e.g., 1920X1080). |
-
code
Descriptions:Status Code Description 10000 Normal 61000 Unsupported HTTP request 61101 Failed to pull stream from the given RTMP URL 61102 RTMP stream pull error (reconnecting) 61103 RTMP reconnection failed after 3 attempts 61010 Invalid HTTP request header 61011 Invalid HTTP request body 61012 Field value validation failed 61013 Internal error (signal server timeout) 61014 Internal error (media server timeout) 61015 Internal error (abnormal room exit) 61017 RTC publishing success.