Back to all status codes

422

Unprocessable Entity

Client Error
RFC 4918

The request was well-formed but was unable to be followed due to semantic errors.

Detailed Information

The 422 status code indicates that the request was well-formed but was unable to be followed due to semantic errors.

Common Examples

  • API requests with invalid JSON
  • Form submissions with missing required fields

Common Uses

  • API requests with invalid JSON
  • Form submissions with missing required fields

Best Practices

  • Use when the request is well-formed but contains semantic errors
  • Include a detailed error message
  • Ensure proper request validation and error handling

Quick Actions

Category Information

Client Error

The request contains bad syntax or cannot be fulfilled

Related Status Codes

3 similar
400

Bad Request

The server cannot or will not process the request due to something that is perceived to be a client error.

401

Unauthorized

The request requires user authentication.

402

Payment Required

Reserved for future use.

Available for Freelance

Fullstack developer specializing in React, Next.js, and Node.js. Let's build something amazing together!

Contact me

Stay in the loop

Get notified about new tools and updates

HTTP Status Codes Reference - Complete List with Descriptions