Errors

The API uses conventional HTTP status codes. Route handlers return a structured error envelope:

{
  "error": {
    "code": "invalid_content",
    "message": "content.text is required for text content",
    "details": { }
  }
}

The code field is a stable, machine-readable identifier — branch on it rather than the human-readable message.

Status codes

Status	Meaning
400	Malformed request.
401	Missing or invalid API key.
403	Authenticated but not allowed (plan/permission gate).
404	Resource not found.
409	Conflicting state (chat closed, channel not active, idempotency reuse).
422	Validation failed.
501	Endpoint is defined but not implemented yet.

Authentication failures (401/403) use a flatter shape: { "error", "message", "status" }.