400 Bad Request

HTTP 400 Bad Request indicates the server could not understand the request due to invalid syntax, malformed JSON, missing required fields, or invalid query parameters. The client should not retry without modification.

Invalid input validation failures, malformed JSON bodies, missing required headers, or schema violations.

• Malformed JSON in request body
• Invalid query string parameters
• Missing required fields
• Schema validation failure
• Invalid Content-Type header

• Inspect the response body for validation error details
• Verify Content-Type matches the body format
• Validate JSON with a linter before sending
• Check API documentation for required fields

HTTP/1.1 400 Bad Request
Content-Type: application/json

{"error":"Invalid email format"}