> ## Documentation Index > Fetch the complete documentation index at: https://help.decodo.com/llms.txt > Use this file to discover all available pages before exploring further. # Status Codes > Web Data API Response Code Explaination ## API Response Codes API response codes and codes that can be found in the response body as `status_code` parameter. | Code | Status | Description | | - | - | - | | `200` | Ok | The request was successfully fulfilled. | | `202` | Accepted | The request has been accepted for processing. | | `204` | No content | The job you requested is still in progress and has not yet been completed. | | `400` | Multiple error messages | The request structure is invalid. This may be due to a misspelled parameter or an incorrect value. More details, will be provided in the response body. | | `401` | Authorization header not provided Invalid authorization header Client not found | The request is missing the required Authorization header, or the provided credentials are invalid. | | `403` | Forbidden | You do not have the necessary permissions to access this resource. | | `404` | Not Found | The requested task ID cannot be found or is no longer available. | | `422` | Unprocessable Entity | There is an issue with the payload you submitted. Please ensure it is properly formatted and contains a valid JSON object. | | `429` | Too many requests | You exceeded the rate limit of your current subscription or requests to a domain are limited due to a low success rate. | | `500` | Internal Server Error | We're currently experiencing some technical difficulties on our end. Please try your request again shortly. | | `524` | Timeout | Service unavailable. | | `612` | Undefined Internal Error | An unexpected error occurred, and we were unable to process the job you submitted. Please try your request again shortly. | | `613` | Faulted After Too Many Retries | An unexpected error occurred, and we were unable to process the job you submitted. Please try your request again shortly. | | `999` | Generic error triggered by server-side restrictions or anti-bot mechanisms | Please try your request again without JS Rendering (`headless: "html"`) parameter. | ## Parser Status Codes Parser status code can be found in the response as `parse_status_code` parameter. | Code | Status | Description | | - | - | - | | `12000` | Success | The returned parsed content is complete. | | `12002` | Failure | We were unable to fully parse the page, possibly due to changes in the target website's HTML structure. | | `12003` | Not Supported | The web page you requested cannot be parsed because it is not supported by our system. | | `12004` | Partial Success | Most of the page was successfully parsed; however, some fields could not be retrieved. | | `12005` | Partial Success | Most of the page was successfully parsed; however, some fields were assigned default values because they could not be located in the HTML source. | | `12006` | Failure | An unexpected error occurred. Please notify us that you received this response, and we will investigate the issue to determine what went wrong. | | `12007` | Unknown | The status of the parsed data is currently undefined, and the result may range from complete failure to full success depending on the circumstances. | | `12008` | Failure | The parsed content could not be retrieved due to missing or invalid data in the target. | | `12009` | Failure | The requested product could not be found. Please verify the URL you submitted, as it may be incorrect, and try again. | Need help or just want to say hello? Our support is available 24/7. \ You can also reach us anytime via email at [support@decodo.com](mailto:support@decodo.com). Can't find what you're looking for? Request an article! \ Have feedback? Share your thoughts on how we can improve. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.