Skip to content

HTTP status codesUpdated 2 Nov 2026

422 Error Code: Data Was Read but Not Accepted

Quick answer A 422 means the server understood the format of what you sent but a value broke a rule. Correct the form fields or the request data and send it again.

HTTP status422
Impact
Medium impact
Typical fix time
Minutes
Who fixes it
You or the developer

The 422 error code, named Unprocessable Content (older texts say Unprocessable Entity), means the server could read your request and its format was valid, but it still could not act on it. Something in the content failed a rule: a missing required field, an email that is not in the right shape, a date in the past, a name that already exists.

Everyday visitors meet it as a form that refuses to submit or an app that shows "422" under a field. Developers meet it when an API checks the body and finds it invalid. The steps below help both groups, starting with the simple check of what you typed.

Common causes

  • 1A required field is empty

    How to tellError appears right after pressing Submit, a field may be marked

    What fixes itFill every field marked required and submit again

  • 2A value is in the wrong format

    How to tellEmail, phone, date or number does not match the expected pattern

    What fixes itRetype it in the shown format, without spaces or symbols

  • 3Value breaks a business rule

    How to tellMessage says already taken, too short, out of range

    What fixes itPick a different username, a longer password or a valid date

  • 4File type or size not allowed

    How to tellError occurs only when you attach a file

    What fixes itUse the allowed type and a smaller size

  • 5Token or form expired

    How to tellYou left the page open for long before submitting

    What fixes itReload the page, fill it again and submit quickly

  • 6Wrong data sent by a script

    How to tellDeveloper gets 422 with a list of invalid fields

    What fixes itRead the error details and correct those fields

How to fix it, step by step

  1. Read the message near each field

    Most forms mark the problem field in red or add a short line beneath it. Work from the top of the form to the bottom and fix each one before pressing Submit again.

  2. Check the format of emails, phones and dates

    Remove extra spaces, remember the at sign and domain in an email, and enter a phone number without brackets. Use the date style the form shows, for example day first or month first.

  3. Make the password meet the rules

    Sites often need a minimum length with letters and numbers. Read the hint beside the box and avoid copying a password that carries a hidden space at the end.

  4. Try a different username or email

    If the error says the value is taken, someone already used it. Add a number or choose another one. If it is your own email, use Login or Forgot password instead.

  5. Reload the page and start fresh

    Forms hold a hidden security token that expires. Reload with F5, refill the form and submit within a few minutes.

  6. Shrink or change the attached file

    Photos from a phone can be large. Use a smaller image or a common type such as JPG or PDF, as the form asks.

  7. Update the app or contact support

    If the app shows only "422" with no explanation, update it and retry. Then send support a screenshot of the screen and what you typed, leaving out passwords and one time codes.

What the 422 error code means

Compare two failures. In a 400, the server cannot even parse your message. In a 422, it parses it perfectly and then says the meaning does not pass its checks. The grammar is right but the facts are wrong. The code comes from a web publishing standard and is now defined in the main HTTP rules as Unprocessable Content.

You register for a course and the page shows 422 Unprocessable Content: email has already been taken. The form was valid. The address is simply already on file, so use Login.

422 compared with 400 and 409

Three ways a server can reject what you send
CodeProblemExample
400Request is malformedBroken JSON or link
422Readable, but values invalidAge field holds text
409Clashes with the current stateEditing an item someone else changed

See 400 Bad Request and 409 Conflict, plus the overview on HTTP status codes.

How developers fix an HTTP 422 error code

  • Read the response body. Frameworks usually return a list of fields with reasons.
  • Match the field names, types and nesting to the API documentation.
  • Check required values, string length, allowed lists and uniqueness.
  • Look for text where a number is expected, and for dates in the wrong format.
  • Validate on the client side too, so users see the message before the call.

A good 422 response names the field and the reason. Avoid sending back only the number, since readers cannot act on it.

Why a 422 should not be ignored in apps

Because the server did not accept the data, nothing was saved. A registration, an order or a profile update that ended in 422 has not happened, so repeat it after fixing the values. If a payment screen showed the error, check your bank app before paying a second time.

Frequently asked questions

What does error code 422 mean?

It means the server understood the request but could not process the content because a value was invalid or broke a rule. Nothing was saved.

How to resolve a 422 error code in a form?

Read the field messages, fix empty or wrongly formatted values, use a unique email or username, then reload and submit again.

How is a 422 different from a 400?

A 400 means the request could not be read properly. A 422 means it was read fine, yet the values failed validation.

Is 422 a problem with my internet?

No. A reply came back, so the line was working. What needs fixing is the data you submitted.

Why do I see 422 in an app and no explanation?

Some apps hide the field details. Update the app, check the data you entered and contact the app's support if it continues.