DeleteCDNTransferRule
https://rtc-api.zego.im/
Call this API to stop relaying streams to CDN. If the specified stream is being relayed to the CDN live service, the relay task will be stopped. Developers must ensure that the relay address is consistent (parameters may differ) to correctly stop the corresponding relay task.
After developers start relaying streams to CDN to relay RTC streams to the specified CDN live address, if it is no longer necessary to relay the stream to the CDN, please refer to this documentation to stop the relaying.
In the test environment (see the IsTest common parameter description for details), the Stream ID must be prefixed with "zegotest-AppId-". For example, if the Stream ID is "test" and the AppId is "123456789" in the test environment, the Stream ID should be "zegotest-123456789-test".
Request
Query Parameters
Possible values: [DeleteCDNTransferRule]
API prototype parameters
https://rtc-api.zego.im?Action=DeleteCDNTransferRule
💡Public parameter. Application ID, assigned by ZEGOCLOUD. Get it from the ZEGOCLOUD Admin Console.
💡Common parameter. A 16-character hexadecimal random string (hex-encoded 8-byte random number). For the generation algorithm, refer to the signature example.
💡Common parameter. Current Unix timestamp in seconds. For the generation algorithm, refer to the signature example. A maximum deviation of 10 minutes is allowed.
💡Common parameter. Signature used to verify the legitimacy of the request. Please refer to the signature mechanism to generate it.
Possible values: [2.0]
Default value: 2.0
💡Public parameter. Signature version number.
Stream ID.
The CDN address for relaying, must be in RTMP format.
When used, URL encoding (UrlEncode) must be performed on its content.
Request sequence number.
Note
For the same StreamId, within 10 consecutive seconds, the request sequence number issued for this StreamId must be strictly increasing; this avoids inconsistent operation order caused by inconsistent request timing received by the server.
If there is no concurrent scenario, using a timestamp (millisecond level) is recommended.
Responses
- 200
- application/json