- Server-Side Access Overview
- Server-Side Callbacks
- Server-Side Stream Mixing APIs
- Server-Side Recording APIs
- Server-Side Room Signaling APIs
- Server-Side Audio Audit APIs
- Server-Side Streaming Control APIs
- API Documents
- API Documents
- Function overview
Server-Side Access Overview
This version of the Server APIs will no longer be updated.
For a better experience, we recommend you use Server APIs v2 in your project. For the detailed specifications of the APIs, see Server API v2.
The following concisely explains the logic to be implemented for business server access:
1、The business server generates the user information,
streamID, etc, required by the client to publish the stream, and all of those information needs to be globally unique, and before the client publishing the stream, the business server need to send that information to the client.
2、After the client pushes the stream successfully, the business server can receive the stream creation callback of the ZEGO server, which is used to increase the live broadcast list (The live broadcast list can be maintained).
- Stream create callback inside the
pic_urlcan be used to yellow, the default is 20 a cached image.
pic_urlcan only be used during a push stream and is not valid after the push stream has ended.
3、After the client stops publishing the stream, the business server can receive the callback for stream closed from the ZEGO sever, which is used to delete the live stream list(The live broadcast list can be maintained).
4、After the client ends the real-time broadcast, the business server can receive a recording file generation callback from the ZEGO server, which is used as an on-demand file.
5、If you need to configure callback information, please log in to the ZEGO Admin console to configure independently.