Theme settings
Update theme settings
Shallow-merges theme over the project's own theme settings. Send only the top-level keys you want to change; theme must contain at least one key.
Nested objects are replaced wholesale. Fetch the current settings first when you need to preserve sibling values inside a nested object.
- Writes the project's own config only; a parent project's theme is never changed through a child project.
- updatedKeys lists the top-level keys whose stored value actually changed. It is empty for a no-op patch, in which case no cache invalidation happens.
- When values change, a theme version snapshot (restorable from Studio) is attempted before the write. Snapshots are deduplicated and best-effort, so do not assume every update has one.
- After a change, caches are invalidated like a Studio save so the edit goes live through api.weaverse.io. Propagation time is not guaranteed; read the settings again to verify.
- Clients or proxies that strip PATCH bodies may send POST to the same URL.
Concurrency: pass the revision from your GET as expectedRevision. If the settings changed since, the request returns 409 STALE_PROJECT and writes nothing; re-read and reapply. Delegated (MCP OAuth) tokens must send it (428 PRECONDITION_REQUIRED otherwise); it is optional for API keys.
Required scope: content:write
patch/projects/{projectId}/theme-settings
Request
- Base URLhttps://studio.weaverse.io/api/v1/content
- AuthHTTP bearer
Path parameters
projectIdstring required
Request body
Response
Merge result with the full stored theme
Changes
No recorded changes to this operation across all 1 revision of this API.