HTTP 400 Bad Request
The server can't understand the request because it is malformed.
Common causes and fixes
- Check the JSON or form body, headers, and URL encoding.
- Look at the response body: APIs usually say what is wrong.
Example response
HTTP
HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8
{ "error": "Bad Request" }Look up the headers shown here in the HTTP headers reference.
Common questions
- What does HTTP 400 mean?
- Bad Request. The server can't understand the request because it is malformed.
- How do I fix a 400 error?
- Check the JSON or form body, headers, and URL encoding. Look at the response body: APIs usually say what is wrong.
- Is 400 an error?
- Yes. 4xx codes are client errors: The request contains a mistake or can't be fulfilled as sent.
Other 4xx codes
401 Unauthorized402 Payment Required403 Forbidden404 Not Found405 Method Not Allowed406 Not Acceptable407 Proxy Authentication Required408 Request Timeout409 Conflict410 Gone411 Length Required412 Precondition Failed413 Content Too Large414 URI Too Long415 Unsupported Media Type416 Range Not Satisfiable417 Expectation Failed418 I'm a teapot421 Misdirected Request422 Unprocessable Content423 Locked424 Failed Dependency425 Too Early426 Upgrade Required428 Precondition Required429 Too Many Requests431 Request Header Fields Too Large451 Unavailable For Legal Reasons