Skip to main content
PATCH
Update theme settings

Authorizations

Authorization
string
header
required

Bearer token: a shop API key (WEAVERSE_API_KEY), a scoped API key or a delegated MCP OAuth token; translation-unit routes also accept a project-bound translation agent token. Each operation lists the scope it requires; the scope table is in the API description.

Path Parameters

projectId
string
required

Body

application/json
theme
object
required

Top-level theme settings keys to merge. Must be a non-empty object.

expectedRevision
string<date-time> | null

Optimistic-concurrency token: the revision value from the GET read this patch was based on (null when GET returned null for a project whose revision was never set; compared null-safely). Required for delegated (MCP OAuth) tokens — omitted → 428 PRECONDITION_REQUIRED; optional for API keys. When the settings changed since (e.g. a concurrent studio save), the request is rejected with 409 STALE_PROJECT before anything is written. Re-read and reapply instead of retrying the same patch.

Response

Merge result with the full stored theme

object
enum<string>
Available options:
theme_settings_update
projectId
string
updatedKeys
string[]

Top-level keys whose stored value actually changed. Empty when the merge was a no-op (no cache invalidation happens in that case).

theme
object

The full merged theme now stored on the project's own config.