> ## Documentation Index
> Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

> The CLI config file: location, format, and direct edits.

`jetemail login` writes credentials to a TOML config file. You can also read, write, and clear values directly with `jetemail config`.

## File location

| Platform | Path                                                              |
| -------- | ----------------------------------------------------------------- |
| macOS    | `~/Library/Application Support/com.JetEmail.jetemail/config.toml` |
| Linux    | `~/.config/jetemail/config.toml`                                  |
| Windows  | `%APPDATA%\JetEmail\jetemail\config\config.toml`                  |

Override with the `JETEMAIL_CONFIG` environment variable:

```sh theme={null}
JETEMAIL_CONFIG=/tmp/jet.toml jetemail whoami
```

The file is `chmod 600` on Unix.

## Inspect

```sh theme={null}
jetemail config path        # prints the location
jetemail config show        # dumps the TOML
```

## Read / write / clear

```sh theme={null}
jetemail config get api_key
jetemail config set api_key api_xxxxxxxx
jetemail config set transactional_key transactional_xxxxxxxx
jetemail config unset api_key
```

Valid keys: `api_key`, `transactional_key`.

## Format

```toml theme={null}
current_profile = "default"

[profiles.default]
api_key = "api_xxxxxxxx"
transactional_key = "transactional_xxxxxxxx"
```

Keys are stored under the `default` profile. You can edit the file directly if you prefer.

## Resolution precedence

The CLI picks a key in this order:

1. `--api-key` / `--transactional-key` flag
2. `JETEMAIL_API_KEY` / `JETEMAIL_TRANSACTIONAL_KEY` env var
3. Config file (`profiles.default`)

`jetemail whoami` shows which layer the active key came from.

<Card title="See also: Authentication" icon="key" href="/cli/authentication" arrow="true">
  Full login / whoami / logout flow.
</Card>