Skip to main content

Error codes

View the ParseX API error response format, HTTP status codes, error messages, and their meanings.

When a request fails, the API returns a request ID, an error code, and an error message.

Error response structure

FieldTypeDescription
request_idstringThe request ID, which can be used to locate the failed request.
codestringThe error code.
messagestringThe error message.
Error
{
  "request_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "code": "NotExistBizId",
  "message": "The bizId not exist."
}

Common error codes

codeHTTPmessageDescription
NotExistBizId400The bizId not exist.The biz ID does not exist
ResultNotReady409Retrieve result if job is not completed.The task is not complete; the result is not ready yet

Parameter errors

codeHTTPmessageDescription
FileDownloadFailed400File download failed.File download failed; not retryable
FileDownloadTimeout400File download timed out.File download timed out; retryable
FileFormatNotSupported400Unsupported file formatsUnsupported file format
FileSizeExceeded400File size exceeds limitFile size exceeds the limit
InvalidFileUrl400URL is invalid or inaccessibleThe URL is invalid or inaccessible
ParseResultExpired400The ParseResult has exceeded the 30-day retention period.The parsing result has expired; it is beyond the 30-day retention period
PageCountExceeded400The page count exceeds the limit.The page count exceeds the limit
PageRangeInvalid400The page range is invalid.The page range is invalid

Task errors

codeHTTPmessageDescription
ProcessingFailed500An internal error occurred in the processing engine.Internal error in the processing engine
ProcessingTimeout500The processing timed out.Processing timed out
BatchProcessingFailed500The batch processing failed.Batch processing failed
CustomerOssWriteFailed500Failed to write to the customer OSS.Failed to write to the customer OSS
InternalError500An internal error has occurred, please try again later.Internal error

Extraction errors

codeHTTPmessageDescription
ParseResultNotReusable400The ParseResult is not reusable because the input is audio/video or the type does not match.The parsing result is not reusable
UnsupportedFileType400Extract does not support audio/video input.Extract does not support audio/video input
InvalidSchema400The schema format is invalid.The schema format is invalid

Other errors

codeHTTPmessageDescription
AccountOverdue403Service suspended due to unpaid feesService suspended due to overdue payment
ServiceQuotaExhausted503The service quota is exhausted.Service quota exhausted

Handling suggestions

When you receive ResultNotReady, the task has not completed yet. Continue calling the corresponding result endpoint with the original biz_id.
FileDownloadFailed is marked as non-retryable; fix the file URL or access conditions first. FileDownloadTimeout is marked as retryable.
Check whether the parsing result is still within the 7-day retention period, and whether the input is audio/video or a mismatched type that Extract does not support.
Return to the API overview to review the async calling flow.
Managed Agent API
Flow Agent API
Sandbox API
RAG API
Long-term Memory
ParseX API
Security API
Framework Integration