Stop live moderation

Update:

Stop moderation for a URL or RTC live task. Success means the stop request was processed; media finalization, result persistence, and cleanup may still be in progress.

POSThttps://vsafe.ilivedata.com/api/v1/livevideo/check/stop

Request format

Send a UTF-8 encoded JSON body.

Request header Required Description
Content-Type Yes application/json; charset=UTF-8
Accept Recommended application/json

For authentication headers and signing rules, see Request signature in the Help Center. Use the submitting project when querying or stopping a task.

Request body

Parameter Type Required Description
taskId String Yes The result.taskId from the successful submission response.

The ID below illustrates the format only. Replace it with the ID returned by your own submission under the same project; do not reuse this fixed example.

{
  "taskId": "cn_00000000-0000-0000-0000-000000000001_1791763200000"
}

Response format

The response body is JSON, with the response header Content-Type: application/json.

Field Type Description
errorCode Integer 0 means the stop request was processed successfully.
errorMessage String Error message; normally omitted on success.
result.taskId String Task ID targeted by this operation.
result.result Integer 0: stop accepted or task already ended; 2: task missing. Not a moderation verdict. 
{
  "errorCode": 0,
  "result": {
    "taskId": "cn_00000000-0000-0000-0000-000000000001_1791763200000",
    "result": 0
  }
}

Retry the same stop request if its response is lost. Once records expire, later stops can report a missing task or expired ID. Stopping does not retract delivered/in-flight callbacks; keep the receiver idempotent. Wait for finalization and cleanup before resubmitting changed settings; a stop response does not guarantee all results have been persisted.

Disconnection, retries, and explicit stopping

Errors

See Error codes and handling; handle HTTP status, errorCode, task/result status code, and moderation verdict result separately.