youka login, or provide it through YOUKA_API_KEY in CI and other non-interactive environments.
youka login verifies the key against the API before saving it, then caches the resolved account email in ~/.youka/config.json for diagnostics.
login
Save an API key to ~/.youka/config.json.
The API key copied from the Youka dashboard. If omitted, the CLI prompts for
it on an interactive terminal.
Examples
logout
Remove the saved API key from ~/.youka/config.json.
whoami
Inspect the resolved key source, API URL, and account identity.
Resolution order
When a saved config key is active,
whoami verifies identity with the API and falls back to the cached account email only if the live lookup is unavailable. It does not use cached config identity for YOUKA_API_KEY tokens.
What’s next
- Global options - flags shared by every command
- Projects - create and process karaoke projects
