preset, settings.style, and settingsOverride field map.
client.projects.getSettings(projectId, options?)
Fetch a project’s active settings.
client.projects.updateSettings(projectId, body, options?)
Patch the active project settings. You can apply a preset, pass raw settings, or both (the preset is applied first, then settings overrides are merged on top).
Fields
Apply a reusable preset. Omit it to leave the current preset unchanged.
Patch applied on top of the preset. Use
style for preset-shaped overrides,
plus project-local fields such as displayLanguages, chordSettings, and
duetSingerFilter.Discovering valid fields
Convert the update schema to JSON Schema at runtime to discover every valid field:Common patterns
- Trim
- Background color
- Display languages
- Apply preset
Project settings vs presets
| Question | Use |
|---|---|
| Same look across many projects? | Presets |
| One-off trim or color tweak on a single project? | Project settings |
| Base look + small project-specific overrides? | Preset + project settings |
What’s next
- Render settings reference — all shared field paths and enum values
- Presets — reusable configurations
- Media — upload backgrounds and logos
- API project settings — the same flow over raw HTTP
- CLI projects — the same flow from the terminal
- Exports — use
settingsOverridefor export-only tweaks
