Skip to main content

Update Theme Settings

Updates global theme settings for a project. Send only the top-level keys you want to change.
The API performs a shallow merge at the top level. If you send a nested object, that object replaces the existing value for its top-level key. Fetch the current settings first when you need to preserve sibling values.
When stored values change, Weaverse attempts to create a theme snapshot of the merged result before writing it. The attempt is deduplicated against the latest snapshot and is best-effort: snapshot failure is non-fatal, and the settings write continues. Do not assume that every successful update has a restorable snapshot. After a successful stored change, the route uses the same cache-invalidation path as a Studio save. This does not guarantee a specific propagation time; fetch the settings again to verify the stored result.

Request body

The theme object must contain at least one key. Clients that cannot send PATCH may send POST to the same URL with the same body.

Example

Response

theme contains the full stored theme after the merge. updatedKeys is empty for a no-op patch.

Safe update pattern

  1. Get the current theme settings.
  2. Prepare the smallest top-level patch that represents the intended change.
  3. Confirm nested objects contain every sibling value that must be preserved.
  4. Send the update and fetch the settings again to verify the result.

Errors

Get Theme Settings

Read the current values before constructing an update.

Content API overview

Review authentication and common write behavior.