The HTTP 422 Unprocessable Content status code means the server understands the request but cannot process its content. In web scraping, this often happens when payloads or parameters are invalid or incomplete.
Semantic errors in the request fields that the server cannot interpret or act upon
Data validation failures, such as field values not adhering to expected formats or constraints
Conflicts in the current state of the resource against which the request was made, such as version mismatches
Incomplete request settings or parameters that are required by the server to process the request
# Request example curl -X POST https://sandbox.oxylabs.io/ -H 'Accept: */*;q=0.8' -H 'Accept-Encoding: gzip, deflate' -H 'User-Agent: Chrome/91.0.4472.124'
Try Scraper API with 5K results
Verify the requested range: Ensure that the range specified in the request is correct and falls within the valid bounds of the content.
Adjust the range headers: Modify the range specified in the HTTP request headers to match the available data on the server.
Check server configuration: Ensure the server is properly configured to handle range requests and that the feature is enabled.
Update the content: If the content has changed, update the client about the new content length or modifications to ensure correct range requests.
# Response example
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 68
{
"error": "Unprocessable entity",
"message": "Invalid data provided"
}Web Scraper API
Public data delivery from a majority of websites
From
49