What a 422 Unprocessable Entity means
The request's format is fine, but the server can't process what's inside it. This is almost always a validation failure on the payload (the data you sent in the request body): a field is missing, a value is the wrong type, or a value breaks a business rule. In short, a 422 status code means the request was well-formed but failed validation.
Why scrapers see 422
You'll hit a 422 when you send data to an API or submit a form and one of the fields is invalid — a malformed JSON value, a bad date, or a required parameter you left out. It's about meaning, not formatting, so fixing it like a 400 'bad request' won't help: the body parsed fine, the values just didn't pass validation.
How to fix a 422 error
Start by reading the response body — most APIs return JSON that lists exactly which fields failed and why. Then fix your payload to match what the server expects: correct the data types, include every required field, and stay within allowed ranges. A reliable trick is to copy a real, working submission captured in your browser's DevTools (the built-in developer tools, opened with F12), including any hidden form fields and tokens. Because a 422 is a problem with the data in your request, changing IPs or headers won't fix it.