Callback on room destroyed

Overview

With this callback, you can receive the callback on the room destroyed by the user in real time, and view the information of the room destroyed by the user.

Callback description

Request method: POST.
Note
The callback data format is JSON, and you need to perform UrlDecode decoding on it.
Request URL: The corresponding callback endpoint set in the ZEGOCLOUD Admin Console
Protocol: HTTPS/HTTP. HTTPS is recommended.

Callback parameters

Parameter	Type	Description
appid	String	The unique identifier of the App.
event	String	The callback event. The return value of this callback is `group_create`.
timestamp	Int	The server time in Unix timestamp when the group is created.
nonce	String	A random number, used to calculate the signature.
signature	String	The verification string. For details, see Authenticating server-to-server callbacks.

Parameters	Type	Description
user_ids	Array	The user IDs of all room members when the room is destroyed.
operator_account	String	The user ID of the room destroyer.

Note

We recommend that you convert some parameters to Int for logical processing. The relevant fields include appid and nonce.

Sample code

Untitled

{
    "appid" : "1",
    "event" : "room_destroy",
    "room_id" : "1",
    "nonce": "350176",
    "signature": "signature",
    "user_ids" : ["Tony","Jenny"],
    "operator_account" : "userA",
    "timestamp" : 1499676978
}

Copied!

Return codes

A status code of 2XX (such as 200) indicates success, and other responses indicate failure.

Callback retry policy

If the ZEGOCLOUD server does not receive a response, or the HTTP status code received by the ZEGOCLOUD server is not 2xx (such as 200), it will retry with intervals of 2s, 4s, 8s, 16s, and 32s respectively. If the retry still fails after an interval of 32s, it will no longer retry.