chat-themes

Update Chat Theme

Update a chat theme (partial update — only sent fields change).

NOTE: Sending is_default: true via PUT DOES cascade here (it unsets other defaults for the account before applying the update); the dedicated POST /{theme_id}/set-default endpoint is the explicit way to do the same.

The configuration blob is normalized + validated on write ONLY when it is present in the payload (full-replace of the blob — senders must ship a complete v2 configuration). A PUT that omits configuration updates the other fields without touching/validating the blob. A legacy-shaped or invalid-token configuration yields a 400 (RFC 9457) naming the offending key (the same normalize-on-write funnel used by MCP).

put/api/v1/chat-themes/{theme_id}

Request

  • Base URL: https://api.gnosari.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.gnosari.com/api/v1/chat-themes/{theme_id}
  • Auth: one of:
    • HTTP bearer
    • API key in header X-AUTH-TOKEN

Path parameters

theme_idinteger required

Request body

namestring nullable
descriptionstring nullable
identifierstring nullable
configurationobject nullable
is_defaultboolean nullable

Response

Successful Response

namestring required

Theme name

descriptionstring nullable

Theme description

identifierstring nullable

URL-safe unique identifier

configurationobject

Canonical v2 chat-theme configuration (camelCase blob): {version: 2, branding: {...}, defaults: {...}}. Legacy pre-v2 shapes (top-level ui/content/features/appearance keys) are rejected with a 400.

is_defaultboolean

Whether this is the account's default theme

idinteger required
created_atstring date-time required
updated_atstring date-time nullable

Changes

No recorded changes to this operation across all 1 revision of this API.