Skip to main content
The TalkValue CLI supports two authentication paths so the same binary works on your laptop and in automation. Profiles let one install hold credentials for multiple workspaces or accounts.

​
Interactive: local desktop

Sign in through the browser:
The CLI prints a one-time code, opens your default browser to the verification page, and waits for you to approve the device. Once you do, it polls for the access token, lists your organizations, and asks which one to use. Pick from the menu and the CLI saves a profile. Skip the org picker by passing the name or ID up front:
The access token is stored in your system keyring (Keychain on macOS, libsecret on Linux, Credential Manager on Windows). The profile record on disk holds the organization ID, organization name, your email, and the auth method, never the token itself.

​
CI and scripting: API token

For non-interactive environments, set TALKVALUE_TOKEN and skip auth login entirely:
An API token in the environment takes precedence over any saved profile, so the same shell can switch between accounts by re-exporting the variable. Generate the token from the dashboard’s Settings area before adding it to your CI secret store.

​
Multi-profile workflow

Each profile stores the organization ID, organization name, your email, and the auth method (oauth or token-based). Profiles let you keep credentials for a staging workspace and a production workspace on the same machine, or work across multiple customer organizations. Target a specific profile for a single command:
Make a profile the default for the shell:

​
Credential precedence

The CLI resolves credentials in this order: The --profile <name> flag and TALKVALUE_PROFILE env var only pick which saved profile is read at priority 2. A TALKVALUE_TOKEN in the environment still wins.

​
Sign out

Removes the active profile and clears its tokens from your system keyring. Pass --profile <name> to remove a specific profile.