--- title: "HTTP 400 Bad Request — What It Means & How to Fix It" description: "HTTP 400 Bad Request: The server cannot process the request because of a client-side error. Common causes, fixes and how to monitor it." url: https://uptrack.app/http/400 ---

# 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. 1 Malformed JSON or XML in the request body — missing commas, unclosed brackets, or invalid encoding. 2. 2 Invalid or missing required query parameters, headers, or form fields that the server expects. 3. 3 URL contains invalid characters, is too long, or has a malformed query string. ## How to fix it 1. 1 Inspect the request in browser dev tools (Network tab). Check the request body, headers, and URL for formatting errors. 2. 2 Validate your JSON payload with a linter before sending. Ensure Content-Type matches the body format (application/json for JSON, etc.). 3. 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. [See plans](https://uptrack.app/pricing) from $3/mo · 30-day money-back guarantee ## Other HTTP status codes - [HTTP 401 Unauthorized](https://uptrack.app/http/401) - [HTTP 403 Forbidden](https://uptrack.app/http/403) - [HTTP 404 Not Found](https://uptrack.app/http/404) - [HTTP 405 Method Not Allowed](https://uptrack.app/http/405) - [HTTP 408 Request Timeout](https://uptrack.app/http/408) - [HTTP 409 Conflict](https://uptrack.app/http/409) - [HTTP 410 Gone](https://uptrack.app/http/410) - [HTTP 413 Payload Too Large](https://uptrack.app/http/413) - [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415) - [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422) - [HTTP 429 Too Many Requests](https://uptrack.app/http/429) - [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451) - [HTTP 304 Not Modified](https://uptrack.app/http/304) - [HTTP 302 Found](https://uptrack.app/http/302) - [HTTP 301 Moved Permanently](https://uptrack.app/http/301) - [HTTP 500 Internal Server Error](https://uptrack.app/http/500) - [HTTP 502 Bad Gateway](https://uptrack.app/http/502) - [HTTP 503 Service Unavailable](https://uptrack.app/http/503) - [HTTP 504 Gateway Timeout](https://uptrack.app/http/504) - [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520) - [HTTP 522 Connection Timed Out](https://uptrack.app/http/522) - [HTTP 204 No Content](https://uptrack.app/http/204) - [HTTP 201 Created](https://uptrack.app/http/201) - [HTTP 200 OK](https://uptrack.app/http/200)