preset, settings.style, and settingsOverride field map.
Endpoints
Full request and response schemas are in API reference.
Fetch the current settings
Patch the settings
PATCH accepts any subset of presetId and settings. When both are passed, the preset is applied first and then settings is merged on top.
- Apply a preset
- Inline settings
- Preset + overrides
Discover valid fields
The SDK exports the schema that validates project settings updates. Convert it to JSON Schema at runtime:Project settings vs presets vs export overrides
Youka has three layers where render settings can live:
Each layer is merged in that order at export time.
What’s next
- Render settings reference — all shared field paths and enum values
- Presets — reusable configurations
- Media — referenced from settings
- CLI projects — the same flow from the terminal
- SDK project settings — the same endpoints in TypeScript
Choose a version
GET /projects/{projectId}/versions lists the project’s versions. Add ?versionId=ver_example to the settings GET request, or include versionId in the PATCH body, to choose a version. Settings responses include versionId. Omitting it preserves primary-version behavior.
Export requests also accept versionId. Alignment selection belongs to the project and is shared across versions. See Automate lyric videos for timing revisions and export snapshots.