Error Format

Client API error responses share a common JSON body.

Generic error

{
  "statusCode": 400,
  "message": "Chat is too old. Please start a new chat.",
  "error": "Bad Request"
}

message may be an array:

{
  "statusCode": 400,
  "message": [
    "type must be a valid enum value",
    "chatId must be a UUID"
  ],
  "error": "Bad Request"
}

Code	Meaning
`400`	Invalid request / business rule violation
`401`	Missing or invalid access token
`404`	Resource not found (chat, template)