Delete Student Question Customer Callback URL
Updated: 2026-05-12 09:48:27
API Description
Delete the "Student Question" customer callback configuration under the current account. After deletion, the system will no longer POST notifications to the original URL when a student question is submitted. The corresponding Redis cache will be cleared upon successful deletion. Deleting the same account multiple times is idempotent (returns success even if no record exists). The API supports the HTTPS protocol.
API URL
https://api.polyv.net/live/v5/chat/redirect/channel/student-question-webhook/delete
Request Method
POST
API Constraints
- The API supports both HTTP and HTTPS; HTTPS is recommended.
roomIdis written into the request body, consistent with other v5 configuration APIs, to verify channel ownership. This aligns with POST and GET (optional query) behavior to avoid environmental differences.
Request Parameter Description
| Parameter | Required | Type | Description |
|---|---|---|---|
| appId | true | String | Account appId [See Get Secret Key] |
| timestamp | true | Long | Current 13-digit millisecond timestamp, valid for 3 minutes |
| sign | true | String | Signature, a 32-character uppercase MD5 value. The appSecret key used to generate the signature is critical for communication data security. It must never be stored or used directly on the client side. All APIs must be called through the customer's own server to relay requests to the POLYV server for response data. [See Signature Generation Rules] |
| roomId | true | String | Channel ID, used to verify whether the channel belongs to the current account |
Example
Request Body JSON:
{
"roomId": "412738"
}
Response Body JSON (Success):
{
"code": 200,
"status": "success",
"message": "删除成功",
"data": ""
}
Response Parameter Description
| Parameter | Type | Description |
|---|---|---|
| code | Integer | 200 indicates completion (including idempotent cases with no record) |
| status | String | success / error |
| message | String | e.g., "Deletion successful" |
| data | String | Usually an empty string on success |
Error Examples
If roomId is not provided, causing channel verification to fail, the response may be:
{
"code": 400,
"status": "fail",
"message": "roomId非法"
}
If x-auth-user-id is not provided:
{
"code": 400,
"status": "fail",
"message": "accountId is required"
}
Server-side error:
{
"code": 500,
"status": "error",
"message": "unknown error"
}
(The specific message depends on the actual situation.)
