Every project has active settings — trim, background, subtitle style, layout — that control how exports are rendered. Use project settings when you want project-local overrides that aren’t worth sharing as a preset. See Render settings reference for the sharedDocumentation Index
Fetch the complete documentation index at: https://docs.youka.io/llms.txt
Use this file to discover all available pages before exploring further.
preset, settings.style, and settingsOverride field map.
Endpoints
| Method | Path | Purpose |
|---|---|---|
GET | /projects/{projectId}/settings | Fetch the active project settings. |
PATCH | /projects/{projectId}/settings | Apply a preset, patch settings, or both. |
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:| Layer | Scope | When to use |
|---|---|---|
| Preset | Account-wide | The same look across many projects. |
| Project settings | One project | Project-specific trim, background, or color. |
Export settingsOverride | One export only | Tweak a single render without touching the project. |
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
