- Software and digital services
- HTTP service
422
HTTP 422 Unprocessable Content: valid syntax but instructions cannot be processed
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
HTTP 422 means the server understands the request content type and the content syntax is correct but it cannot process the contained instructions.
Safety first
Stop and check this first
- Do not disable server-side validation or strip required business rules to make a 422 disappear. Correct the instruction or the documented contract.
Safe checks you can perform
- Preserve the structured error response
- Check instructions rather than basic syntax
- Reduce to the smallest valid operation
Leave these tasks to a qualified professional
- Do not attempt this professional task: Align processing rules and machine-readable feedback
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Align processing rules and machine-readable feedback
What they doThe API owner should identify the unprocessable instruction and ensure the response names the relevant rule or field without leaking internal or sensitive data.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Preserve the structured error response
Record the endpoint request identifier timestamp and returned field or rule details. Remove secrets and personal data before sharing the evidence.
Validation responses and request bodies can contain private user or business data.
Evidence: RFC 9110 section 15.5.21 - 422 Unprocessable Content
Check instructions rather than basic syntax
Compare values relationships and requested operation with the endpoint rules. The server has already understood the content type and syntax in the RFC 9110 definition.
Changing Content-Type or JSON punctuation blindly addresses different error classes and can hide the actual rule violation.
Evidence: RFC 9110 section 15.5.21 - 422 Unprocessable Content
Reduce to the smallest valid operation
In a safe environment remove optional instructions and reintroduce them one at a time while preserving required fields and the endpoint contract.
Do not use real customer data or repeat a production write while isolating the rejected instruction.
Evidence: RFC 9110 section 15.5.21 - 422 Unprocessable Content
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- HTTP
- Product type
- HTTP service
Known code variants
- 422 Contenido no procesable
- 422 Contenuto non elaborabile
- 422 Nicht verarbeitbarer Inhalt
- 422 Unprocessable Content
- Bosch 422 bici elettrica
- Bosch 422 bicicleta eléctrica
- Bosch 422 E-Bike
- Bosch 422 eBike
- Bosch 422 vélo électrique
- Bosch eBike code 422
- Bosch eBike error 422
- Bosch eBike Fehler 422
- Bosch eBike Fehlercode 422
- code Bosch eBike 422
- code erreur 422
- codice Bosch eBike 422
- código Bosch eBike 422
- erreur Bosch eBike 422
- error Bosch eBike 422
- errore Bosch eBike 422
- HTTP 422
- HTTP status 422
- status code 422
What it means
The distinction matters: 422 is not unsupported media type and not malformed syntax. Use the response details and the endpoint’s rules to locate the instruction it cannot process.
Warnings and stop conditions
- Higheditorial warning
Do not disable server-side validation or strip required business rules to make a 422 disappear. Correct the instruction or the documented contract.
Evidence: RFC 9110 section 15.5.21 - 422 Unprocessable Content
Symptoms and causes
Probable causes · in order
- The server cannot process otherwise valid content instructionsConfirmed
RFC 9110 defines 422 when the server understands the content type and the syntax is correct but it cannot process the contained instructions.
Evidence: RFC 9110 section 15.5.21 - 422 Unprocessable Content
Virtual technician
Does 422 still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
RFC 9110 section 15.5.21 - 422 Unprocessable Content
Internet Engineering Task Force · 2022 · official_doc
Was this entry useful?