Home > Error > 400
Bad Request
Your browser sent a request that this server could not understand.
This is usually caused by a malformed URL, missing or invalid parameters, or a payload that does not conform to the expected format. The request was rejected before any application logic ran — no records were created or modified.
Possible causes
- Request URL contains invalid characters or malformed query string
- Required header is missing (e.g. Content-Type, Host, Authorization)
- Request body is not valid JSON / XML / form-encoded data
- A required field is missing from the request body
- A field value violates a constraint (length, type, range, enum)
- Multipart form is incorrectly delimited or has corrupt boundaries
- Cookie header contains invalid characters
Example of a malformed payload
// expected schema requires: email (string), age (number), role (enum)
{
"email": "not-an@email", // invalid email format
"age": "thirty", // expected number, got string
"role": "super-admin"// value not in enum [user, admin]
}
Correct vs incorrect
✗ Bad
{
"email": "user@",
"age": "30",
"role": "X"
}
✓ Good
{
"email": "u@a.io",
"age": 30,
"role": "admin"
}
Common validation rules
| Field | Rule | Example |
| email | RFC 5322 | user@example.com |
| age | integer 0-150 | 34 |
| role | enum | user / admin |
| created_at | ISO 8601 | 2026-05-19T14:18Z |
| tags | array max 8 | ["a","b"] |
Request information
Status:400 Bad Request
Method:POST
Request URI:/api/v2/users
Content-Type:application/json
Content-Length:148
Request ID:req_8a92-bb04-cc01
Schema:users.v2.json
Time:Tue, 19 May 2026 14:18:02 GMT
How to fix this
- Verify each field against the API documentation
- Use a JSON validator to check payload syntax
- Check that the Content-Type header matches the body format
- Try again after correcting the errors
- Contact support with the request ID if the issue persists
Tip: If you are a developer, the API reference documents the expected format for each endpoint, including the full JSON Schema for every payload.
nginx — server — running on Linux — IPv4/IPv6