Error Handling

All API error responses follow a consistent envelope format.

Error Response Format

{
  "detail": {},
  "type": "string",
  "requestUuid": "uuid",
  "message": "Human-readable error message",
  "status": 422
}

Common Status Codes

Status	Meaning
400	Bad Request — Invalid parameters
401	Unauthorized — Missing or invalid token
403	Forbidden — Insufficient permissions
404	Not Found — Resource does not exist
422	Unprocessable Entity — Validation failed
500	Internal Server Error

Handling Errors

Always check the status field and the message for details. The detail field may contain validation errors for specific fields. The requestUuid can be provided to support for debugging.