Error Codes
When an error occurs, the Parse API returns a structured error response with the following fields:
Custom Error Codes
We provide custom error codes to make it easier for your system to know what happened in case of a failure. There will also be a retryable=true|false field in the response body, but you can also find a breakdown below. Most errors are not retryable and are client errors related to the file provided for parsing.
HTTP error codes
Corresponding http error codes for different types of failures. We generally recommend relying on our custom error codes for programmatic handling.
400 Bad Request
Returned when:
- Required fields are missing (e.g.,
file) urlis not provided in the file object- The provided
urlis invalid - The
configcontains invalid values (e.g., unsupported target format or chunking strategy) - The file type is not supported
- The file size is too large
401 Unauthorized
Returned when:
- The API token is missing
- The API token is invalid
403 Forbidden
Returned when:
- The authenticated workspace doesn’t have permission to use the parse functionality
- The API token doesn’t have sufficient permissions
422 Unprocessable Entity
Returned when:
- The file is corrupt and cannot be parsed
- The file is password protected
- The file could not be converted to PDF
- The system failed to generate the target format
500 Internal Server Error
Returned when:
- An OCR error occurs
- A chunking error occurs
- Any other unexpected error occurs during parsing
Handling Errors
Here are examples of how to handle errors from the Parse API:

