Bad Request

Status: 400 Type: https://brivo.ltd/docs/identity/api/errors/bad-request

The server could not process the request because it was syntactically invalid. This is distinct from a validation error (422), which means the request was well-formed but its contents failed business rules.

Common causes

• JSON body that cannot be parsed
• Missing a required top-level field that is not subject to schema validation
• Incorrect Content-Type header

Example

{
  "type": "https://brivo.ltd/docs/identity/api/errors/bad-request",
  "title": "Bad Request",
  "status": 400,
  "detail": "Request body must be valid JSON."
}

Resolution

Check that the request body is valid JSON and that the Content-Type header is set to application/json. For field-level validation failures, see Validation Error.