Skip to main content

​
Get Your API Key

  1. Log in to the Bolna Dashboard
  2. Go to Developers
  3. Create a new API key or copy an existing one

​
Authentication Methods

The CLI resolves authentication using this priority order:

​
Environment Variable

Best for CI/CD jobs, containers, or scripts. Define it once per session and every command uses it — no keychain lookup happens at all.

​
Stored Login

Best for local, day-to-day use. bolna login validates your key live, then stores it in your OS’s native credential store — never in a plaintext file.
Remove it with bolna logout.
Multiple accounts? Every auth command accepts --profile <name> (see Global Flags), so you can keep separate credentials for separate Bolna accounts side by side — bolna login --profile client-acme, then bolna agents list --profile client-acme. Omitting --profile uses a default profile.

​
Never a Dead End

Any command that needs auth — including bare bolna opening the dashboard — checks for credentials first. If none are configured and you’re on a real terminal, it offers to log you in right there instead of erroring out:
It logs in, then falls straight through into the command you originally ran. In a non-interactive context (a script, a pipe, CI), this prompt never appears — it fails fast with a clear error instead, since there’s no one there to answer it.

​
Security Best Practices

  • Do not commit API keys in scripts, repositories, or configuration files.
  • Prefer environment variables in CI/CD, since the keychain isn’t available in most containers.
  • Rotate API keys regularly and scope keys to the minimum access required.

​
Commands

bolna login

bolna logout

bolna whoami