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

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

FieldRuleExample
emailRFC 5322user@example.com
ageinteger 0-15034
roleenumuser / admin
created_atISO 86012026-05-19T14:18Z
tagsarray 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

  1. Verify each field against the API documentation
  2. Use a JSON validator to check payload syntax
  3. Check that the Content-Type header matches the body format
  4. Try again after correcting the errors
  5. 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