Common Error Codes

Scope

This page describes common error codes used by HTTP moderation APIs, including text, image, audio, video, and web moderation. Not every API returns every code listed here. API-specific errors, parameter requirements, and limits remain documented on each API page.

Use the HTTP status and errorCode together to identify an error. For example, 2000 with HTTP 400 indicates a missing business parameter, while 2000 with HTTP 401 indicates a missing authentication parameter.

A successful API call does not necessarily mean that content passed moderation. Check the moderation result or task status separately.

Common Error Codes

HTTP Status Error Code Message Description
200 0 — The request succeeded; the error message is usually omitted.
400 1002 API Not Found API path not found. Check the request URL.
400 1003 Bad Request The request could not be parsed. Check its format and the API parameter requirements.
405 1004 Method Not Allowed The request method or headers do not meet the API requirements. Check the HTTP method and Content-Type.
411 1007 Not Content Length Content-Length is missing or invalid.
401 1102 Unauthorized Client X-AppId is invalid. Check the project ID.
401 1106 Missing Access Token The Authorization signature is missing.
401 1107 Invalid Token The Authorization signature is invalid. Check the signing parameters, secret key, and the actual request body.
401 1108 Expired Token X-TimeStamp has expired. Check the request timestamp and the client clock.
401 1110 Invalid Client The client identifier is invalid or missing. The exact condition depends on the API; some APIs use this code when X-AppId is missing.
400 2000 Missing Parameter A required business parameter is missing, such as content, taskId, or url. See the API-specific supplement.
400 2001 Invalid Parameter A business parameter has an invalid format or value. See the API documentation for specific conditions.
401 2000 Missing Parameter An authentication parameter is missing, such as X-TimeStamp.
401 2001 Invalid Parameter An authentication parameter has an invalid format, such as an incorrectly formatted X-TimeStamp.
429 1104 Out of Rate Limit The request rate limit was exceeded. Limits and counting rules depend on the product, API, and project configuration.
429 1105 Bandwidth limit exceeded The bandwidth limit was exceeded. Limits depend on the product or project configuration.

For authentication errors, see Request Signature. Use the HTTP method and Content-Type required by the specific API.