Skip to main content
The API uses standard HTTP status codes to indicate the success or failure of an API request.
Important: While the HTTP status code indicates the transport status, the specific business logic result is defined by the code field in the response body.Please always refer to the msg field in the response JSON for the specific error message and details.

​
HTTP Status Codes

These are the general HTTP status codes used by the API to indicate the connection or request status.
HTTP CodeMeaningDescription
200OKRequest successful (includes synchronous results or successful submission of asynchronous tasks).
400Bad RequestInvalid parameters (e.g., missing required fields, JSON format error). Corresponds to business codes 100xxx.
401UnauthorizedAuthentication failed (missing, invalid, or revoked API Key). Corresponds to 401xxx.
402Payment RequiredInsufficient quota, balance exhausted, or plan expired. Corresponds to 402xxx.
403ForbiddenAccess denied (e.g., account frozen, banned App ID, or accessing unauthorized resources).
404Not FoundResource not found (invalid API path). Corresponds to 404xxx.
413Payload Too LargeUploaded file size exceeds the system limit.
429Too Many RequestsRate limit exceeded (QPS limit). Corresponds to 429xxx.
500Internal Server ErrorSystem internal error. Corresponds to 5xxxx.

​
Business Error Codes

The code field in the JSON response represents the specific business error.
CodeMessage
0Success
100001Request parameter binding failed
100002Parameter validation failed (e.g., model not found, size limit exceeded)
130005Request too frequent
400001Invalid path format
400002Invalid version
400003Invalid module name
400005Invalid request parameters (missing auth info or body)
401001Authorization information missing
401002Unauthorized (Invalid API Key/Token)
402000Quota freeze failed
500001Service unavailable
500002Database error
500003Proxy error
500004Task creation failed
530002Server is busy
530003Internal server error