400 Bad Request

http

HTTP/1.1 400 Bad Request

Explanation

Use 400 when the request cannot be understood or parsed as sent.

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Same sheet · prioritizing Client and server errors

Missing or invalid authentication credentials.

Open In sheethttpsame section

Authenticated but not allowed to perform the action.

Open In sheethttpsame section

The resource does not exist.

Open In sheethttpsame section

Request conflicts with current resource state.

Open In sheethttpsame section

Optimistic concurrency guard failed.

Open In sheethttpsame section

Well-formed request but semantic validation failed.

Open In sheethttpsame section