Authentication

The first time you launch the interactive TUI (buzz with no arguments), you’ll be prompted to authenticate with Beeminder. You can also authenticate explicitly at any time with buzz auth login — which is what the other subcommands (buzz today, buzz next, etc.) point you to if no credentials are found.

Either way, the steps are the same:

1. Visit https://www.beeminder.com/api/v1/auth_token.json to get your credentials.

2. Copy the JSON output. It has this format:

   {"username":"your_username","auth_token":"your_token"}

3. Paste it in when prompted.

4. Press Enter to save.

Your token stays private

Credentials are read interactively (not as command-line arguments), so your auth token stays out of your shell history. They’re stored in ~/.buzzrc with read/write permissions for your user only.

Re-authenticating

The interactive TUI auto-prompts for credentials on first run, so you typically only need buzz auth login to re-authenticate or when a subcommand reports that no configuration was found.

Piped input is also supported for scripting:

buzz auth login < creds.json

See buzz auth login in the command reference for details.