Error codes and handling
Update:
Check HTTP status and errorCode first, then interpret each endpoint’s code/result. Error responses may omit task and moderation fields.
Video moderation service errors
HTTP
errorCode
Scenario and handling
400
2001
Invalid parameter: unsupported language, out-of-range sampling, invalid Base64. Correct the request before retrying.
400
2002
Request binding, format, or protocol error; HTTP status can instead be 404/405, etc. Check method, path, headers, and JSON.
400
1103
Project or strategy missing. Check X-AppId/strategyId and provisioning.
429
1104
Request, queue, or concurrency limit. Back off; avoid tight polling or repeated submissions.
400
2109
Missing task record, such as a cleaned-up VOD task. Live queries can instead return HTTP 200 with code=3.
400
2110
RTC recording startup error. Check provider, room, and joining credentials.
400
2111
Task ID exceeds its validation window. Use a newly submitted task ID; retrying an old ID cannot restore results.
400
2112
Invalid ID timestamp, e.g. later than service time. Do not modify IDs returned by the service.
500
1001
Service error. Record time, project, and task ID; avoid unbounded retries.
{
"errorCode": 2001,
"errorMessage": "Invalid Parameter"
}
Download, decoding, or downstream failures in asynchronous tasks may appear as errorCode=0, code=1 in queries/callbacks. Do not expect a universal HTTP 200 / errorCode=1200. Error messages are diagnostic text, not stable business identifiers.
Public gateway and authentication errors
The public entry point can also return routing, length, authentication, or token errors, such as 1002/1003/1004/1007, 1102/1106/1107/1108/1110, and 2000. These belong to the entry layer and may use different HTTP statuses. Continue to follow the request signature specification; authentication is required even when a gateway error is not exhaustively listed here.
Check HTTP status and errorCode first, then interpret each endpoint’s code/result. Error responses may omit task and moderation fields.
Video moderation service errors
| HTTP | errorCode | Scenario and handling |
|---|---|---|
| 400 | 2001 | Invalid parameter: unsupported language, out-of-range sampling, invalid Base64. Correct the request before retrying. |
| 400 | 2002 | Request binding, format, or protocol error; HTTP status can instead be 404/405, etc. Check method, path, headers, and JSON. |
| 400 | 1103 | Project or strategy missing. Check X-AppId/strategyId and provisioning. |
| 429 | 1104 | Request, queue, or concurrency limit. Back off; avoid tight polling or repeated submissions. |
| 400 | 2109 | Missing task record, such as a cleaned-up VOD task. Live queries can instead return HTTP 200 with code=3. |
| 400 | 2110 | RTC recording startup error. Check provider, room, and joining credentials. |
| 400 | 2111 | Task ID exceeds its validation window. Use a newly submitted task ID; retrying an old ID cannot restore results. |
| 400 | 2112 | Invalid ID timestamp, e.g. later than service time. Do not modify IDs returned by the service. |
| 500 | 1001 | Service error. Record time, project, and task ID; avoid unbounded retries. |
{
"errorCode": 2001,
"errorMessage": "Invalid Parameter"
}
Download, decoding, or downstream failures in asynchronous tasks may appear as errorCode=0, code=1 in queries/callbacks. Do not expect a universal HTTP 200 / errorCode=1200. Error messages are diagnostic text, not stable business identifiers.
Public gateway and authentication errors
The public entry point can also return routing, length, authentication, or token errors, such as 1002/1003/1004/1007, 1102/1106/1107/1108/1110, and 2000. These belong to the entry layer and may use different HTTP statuses. Continue to follow the request signature specification; authentication is required even when a gateway error is not exhaustively listed here.