HTTP 400 Bad Request
The server cannot process the request because of a client-side error. The request has malformed syntax, invalid parameters, or is otherwise unreadable by the server.
What does HTTP 400 mean?
The server cannot process the request because of a client-side error. The request has malformed syntax, invalid parameters, or is otherwise unreadable by the server.
Common causes
- 1
Malformed JSON or XML in the request body — missing commas, unclosed brackets, or invalid encoding.
- 2
Invalid or missing required query parameters, headers, or form fields that the server expects.
- 3
URL contains invalid characters, is too long, or has a malformed query string.
How to fix it
- 1
Inspect the request in browser dev tools (Network tab). Check the request body, headers, and URL for formatting errors.
- 2
Validate your JSON payload with a linter before sending. Ensure Content-Type matches the body format (application/json for JSON, etc.).
- 3
Read the response body — most APIs include a detailed error message explaining which field or parameter is invalid.
Monitor for HTTP 400 errors
If your endpoint starts returning 400 errors to valid requests, it often means a deployment broke input parsing. Uptrack detects the status code change and alerts you before users file bug reports.
Catch HTTP errors before your users do
Start free, or choose a plan, for 30-second monitoring and alert confirmation.
from $3/mo · 30-day money-back guarantee
Other HTTP status codes
- HTTP 401 Unauthorized
- HTTP 403 Forbidden
- HTTP 404 Not Found
- HTTP 405 Method Not Allowed
- HTTP 408 Request Timeout
- HTTP 409 Conflict
- HTTP 410 Gone
- HTTP 413 Payload Too Large
- HTTP 415 Unsupported Media Type
- HTTP 422 Unprocessable Entity
- HTTP 429 Too Many Requests
- HTTP 451 Unavailable For Legal Reasons
- HTTP 304 Not Modified
- HTTP 302 Found
- HTTP 301 Moved Permanently
- HTTP 500 Internal Server Error
- HTTP 502 Bad Gateway
- HTTP 503 Service Unavailable
- HTTP 504 Gateway Timeout
- HTTP 520 Web Server Returns Unknown Error
- HTTP 522 Connection Timed Out
- HTTP 204 No Content
- HTTP 201 Created
- HTTP 200 OK